PEGACPSA88V1 Certified Pega System Architect (V8.8) Questions and Answers

When the goal interval lapses and the assignment urgency is adjusted to 100, the urgency value continues to increment as configured for the deadline and passed deadline intervals. The urgency value determines how quickly an assignment needs attention and affects how assignments are prioritized in worklists and work queues. References: https://community.pega.com/knowledgebase/articles/case-management/86/configuring-service-levels

The project delivery leader is responsible for managing the project plan, scope, budget, and timeline, as well as communicating with stakeholders and resolving issues. The project delivery leader should be contacted to verify the project plan and manage expectations for the release schedule when the scope of the project exceeds the original estimates. References: https://academy.pega.com/library/82/pega-project-delivery-methodology

This option follows best practices for naming a ruleset in Pega Platform. A ruleset name consists of two parts separated by a colon (:). The first part is an application-specific identifier, such as Credit Check, that is unique within your organization. The second part is a version number that consists of three numeric segments separated by hyphens (-), such as 03-01-02. References: https://community.pega.com/sites/default/files/help_v88/procomhelpmain.htm#rule-/rule-ruleset-/rule-ruleset-name/main.htm

Graphical user interface, text, application Description automatically generated

A bug is a work item that describes an error or defect in the application that prevents it from functioning as expected. A bug should be created in Agile Workbench to address the issue of the Send case status email step not sending an email. References: https://community.pega.com/knowledgebase/articles/pega-platform-capabilities/86/creating-bugs-agile-workbench

To populate a test page with valid data before testing the rule, you can run a data transform to create the test page or copy data from an existing clipboard page. A data transform is a rule that defines how to convert data that is in one format and class (the source) into data of another format and class (the target). The clipboard is a temporary memory area on the server that stores property values for your application. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/data-transforms https://community.pega.com/knowledgebase/articles/application-development/86/clipboard-tool

These two statements are true about insights. Insights are rules that Pega Platform uses to transform data queries into tables or visualizations that you can then share between users and embed in landing pages of your applications. Insights can include multiple data items that you can filter, sort, and group according to your business requirements. You can search for and select the fields that you want to include in an insight from the data objects that are available in your application. References: https://docs-previous.pega.com/reporting/87/visualizing-data-insights

This statement about configuring application access is true. An access group is a rule that defines the roles and permissions that users have in an application. An access group can list more than one role, but the system uses the most restrictive setting when there is a conflict between roles. For example, if one role allows creating a case and another role denies creating a case, the system denies creating a case for users who belong to both roles. References: https://community.pega.com/knowledgebase/articles/security/86/access-groups

 The context section of a data transform rule defines the scope and applicability of the rule. It specifies the application layer, such as framework or implementation, the class that the rule applies to, and the ruleset version that contains the rule. References: https://community.pega.com/sites/default/files/help_v88/procomhelpmain.htm#rule-/rule-obj-/rule-obj-property/context.htm

To configure the account information page, you can select Copy from a data page on the page property. This option copies the data from the data page to the clipboard page when the case is created and does not update it when the case is further processed. A data page is a rule that defines how and when to load data into memory for use by an application. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/data-pages

These two field types are specialized versions of the Query field type. A Query field type allows users to select a value from a list that is populated by running a report definition rule or by referencing another field value rule. A Case reference field type allows users to select an existing case from a list that is populated by running a report definition rule on the Work- class or one of its subclasses. A Data reference field type allows users to select an existing data object from a list that is populated by running a report definition rule on a specific data class. References: https://community.pega.com/knowledgebase/articles/user-experience/86/configuring-field-types

To enforce these restrictions when requesting an instant loan, you can use a single Validate rule with two conditions one for income and one for credit card debt. A Validate rule is a rule that tests property values for errors or omissions during case processing. You can define multiple conditions in a Validate rule to check whether the property values meet your business requirements. References: https://community.pega.com/knowledgebase/articles/case-management/86/validating-case-data

The Constellation design system is a set of UI/UX templates, patterns, and components that enable faster and easier development of Pega applications. It improves context switching or multitasking by allowing users to work on multiple tasks in parallel using dynamic containers and tabs. It also uses a modular design that enables reuse and customization of UI elements across applications. References: https://community.pega.com/knowledgebase/articles/user-experience/88/introducing-pega-constellation-design-system