PEGACPSA88V1 Practice Exam Questions with Answers Certified Pega System Architect (V8.8) Certification

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

This statement about channel interfaces is true. A channel interface is a user interface that allows users to interact with an application through various channels, such as web, mobile, email, chatbot, or voice. A channel interface allows you to adjust your application to your specific business needs by creating tailored and interactive user interfaces. Channels are created from templates that include predefined layouts and navigation for use in your application. References: https://academy.pega.com/topic/channel-interfaces/v1

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

When adding an external data source to a data object, a data transform is automatically generated to map the application data model to the connector. 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). A connector is a rule that defines how your application exchanges information with an external system. References: https://academy.pega.com/topic/data-records/v4 https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/connectors

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

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

To configure a solution that requires approvals from the requestor’s manager, division VP, and possibly an accountant based on the total amount, you can use cascading approval using the reporting manager. This model uses a reporting structure to determine who approves a case based on their position in an organizational chart. You can also use a condition to include an accountant in the approval chain if the total amount exceeds a certain threshold. References: https://academy.pega.com/topic/cascading-approval/v1

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

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

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 meet this requirement, you need to set the deadline in the service level to 3 days. The deadline defines when to take action because a step or case is past due. The deadline interval is measured from when an assignment is ready for a user. References: https://academy.pega.com/topic/deadline-interval/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

The status of a case is set to the value configured in the Status field of an assignment shape when that assignment starts. Therefore, if the Review claim step is configured to set the status to Pending-Investigation, the status of the case is set to Pending-Investigation when the Review claim step starts. References: https://community.pega.com/knowledgebase/articles/case-management/88/updating-case-status