Pegasystems PEGACPSA88V1 Certified Pega System Architect 8.8 Exam Practice Test

These two statements about Configuration sets are true. Configuration sets are a unified configuration framework that allows for truly upgradeable and dynamic applications. Configuration sets enable the business to control application behavior by providing low-code options for customizing parameters for application features or specific case types. Configuration sets are used to organize Configuration settings with a common element, such as an application feature or specific case type. References: https://academy.pega.com/topic/configuration-sets/v1

To implement this requirement, you can configure a data page to store the make, model, and year vehicle data and configure a connection to an external system of record that contains the make, model, and year vehicle data. A data page is a rule that defines how and when to load data into memory for use by an application. You can configure a data page to source its data from an external system by using connectors or integrations. This way, you can access up-to-date vehicle data from an external database or web service without storing it locally in your application. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/data-pages https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/sourcing-data-page-data-external-systems

To fulfill these requirements, you can add a report widget to the Manager portal dashboard and then click Publish. A report widget is a UI element that displays data from a report definition rule in various formats, such as charts, tables, or maps. You can add report widgets to dashboards or landing pages to provide users with quick access to relevant information. By clicking Publish, you make the changes available to all users who have access to the portal. References: https://community.pega.com/knowledgebase/articles/reporting/86/adding-report-widgets-dashboards

Optional actions are actions that users can perform at any time during a stage in the case workflow. They are not required to advance the case to the next stage or step. Optional actions can be used to allow customers to update any of the user profile pages individually during the order placement stage. References: https://community.pega.com/knowledgebase/articles/case-management/88/configuring-optional-actions

These two statements about data records are true. Data records are values for the fields that are associated with a specific data object, such as a customer or a product. Data records need unique user-generated IDs to identify each record in the data object. Data records define permissible values for data fields, which limit the input values to valid options, reduce errors, and allow for automation. References: https://academy.pega.com/topic/data-records/v4

To display the Select flight insurance check box only when the itinerary includes a flight, you can apply a visibility condition (When rule) to the check box. A visibility condition is a rule that determines whether a UI element is visible or hidden based on a logical expression or a reference to another rule. A When rule is a rule that defines a true-false test based on property values, constants, or other factors. References: https://community.pega.com/knowledgebase/articles/user-experience/86/configuring-visibility-conditions

The basic condition for the Search duplicate cases step is to compare the issue type of the current case with the issue type of existing cases. This way, only cases that have the same issue type are considered as potential duplicates. References: https://community.pega.com/knowledgebase/articles/case-management/88/searching-duplicate-cases

You should consider using a field value when the list of allowed values is mostly static or shared across all case types. A field value is a rule that defines a single value for a field that is used in multiple places in an application. Field values are useful when the list of values does not change frequently or when the same values are used in different case types. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/field-values

Diagram Description automatically generated

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

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 localize correspondence into a language that is unavailable in the Pega language pack, you can create the Translation rule manually and include the rule in the application ruleset. A Translation rule is a rule that defines how to translate text from one language to another. You can create a Translation rule manually by using the Create menu in Dev Studio and selecting Rule > Integration-Resources > Translation. You can then specify the source and target languages, the text to be translated, and the translated text. You can also use a decision table or a connector to provide the translated text. You must include the Translation rule in the application ruleset so that it can be used by the application. References: https://community.pega.com/knowledgebase/articles/integration/86/translation-rules

To satisfy this security requirement, you can create a new SysAdmin persona with the required access. A persona is a rule that defines the access rights and privileges for a group of users who perform similar tasks in an application. You can create a new persona by copying an existing one and modifying it to suit your needs. In this case, you can copy the Admin persona and add some of the reporting features from the Author persona to create the SysAdmin persona. References: https://community.pega.com/knowledgebase/articles/security/86/personas

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