PEGACPSA88V1 Sample Questions Answers

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

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

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

Diagram Description automatically generated

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

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

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 meet the requirement, you can add an Identify service animal process within the Travel booking case life cycle and apply a condition to determine when to run the process. The condition can be based on a property that indicates whether the passenger is traveling with a service animal or not. References: https://community.pega.com/knowledgebase/articles/case-management/88/adding-processes-case-life-cycle

To achieve the requested behavior, you can use a checkbox and a decision shape to branch the case flow based on whether the customer wants catering or not. You can also use a visibility condition to show or hide the menu preferences and appointment date fields depending on the checkbox value. References: https://community.pega.com/knowledgebase/articles/case-management/88/branching-case-flow-based-decision

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

The data page is reloaded at 06:42. A data page is a rule that defines how and when to load data into memory for use by an application. The Reload if older than field specifies the maximum age of the data page before it is reloaded from its source. In this case, the data page’s Reload if older than field is set to 15 minutes, which means that the data page will be reloaded if it is older than 15 minutes when it is requested. The data page is created at 06:12, so it will expire at 06:27. At 06:20, the user requests product information, but the data page is not reloaded because it is not expired yet. At 06:42, the user requests product information again, but this time the data page is reloaded because it is older than 15 minutes. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/data-pages

 These two requirements ensure that valid data is used in a case. The data fits the business logic means that the data values are consistent with the rules and conditions that define the case behavior and outcome. The data is the correct field type means that the data values match the expected format and structure of the field properties, such as text, number, date, or email. References: https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/data-types https://community.pega.com/knowledgebase/articles/data-management-and-integration/86/field-values

 To create a visualization that allows managers in the Customer Service division to track the number and status of Customer Support Request cases submitted over the last 30 days, you can open the Explore data landing page, and then create a new insight. An insight is a visualization of data that you can use to monitor key performance indicators, identify trends, and discover opportunities for improvement. You can create insights from the Explore data landing page in App Studio. References: https://community.pega.com/knowledgebase/articles/reporting/86/creating-insights

To achieve the requested behavior, you can use a checkbox and a decision shape to branch the case flow based on whether the customer wants catering or not. You can also use a visibility condition to show or hide the menu preferences and appointment date fields depending on the checkbox value. References: https://community.pega.com/knowledgebase/articles/case-management/88/branching-case-flow-based-decision