Pegasystems PEGACPSA88V1 - Certified Pega System Architect (V8.8)

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

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

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

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

To meet this requirement, you can design a case with a step that routes to the manager. A step is an action that users or systems perform to advance a case toward resolution. You can configure a step to route to a specific user or group of users based on their role, skill, availability, or reporting structure. References: https://community.pega.com/knowledgebase/articles/case-management/88/adding-steps-case-life-cycle

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 ensure the email includes the case ID for the survey, you can use the Insert Property feature of a Send Email step to add the case ID when composing the custom message. This way, you can dynamically insert the value of any property in your email message. References: https://community.pega.com/knowledgebase/articles/case-management/88/sending-emails