Pegasystems PEGACPSA88V1 Certified Pega System Architect (V8.8) Exam Practice Test

 This option requires you to configure distinct mobile app channels because it involves customizing the look and feel of the mobile app for different user groups. A mobile app channel is a configuration layer that defines how users interact with your application on mobile devices. You can create multiple mobile app channels for different user groups or personas and apply different branding, security, or functionality settings to each channel. References: https://community.pega.com/knowledgebase/articles/mobile/86/configuring-mobile-app-channels

To implement this requirement, you can implement the Repair phase as a child case. A child case is a case that is created and processed as part of another case, called the parent case. A child case can run independently of the parent case and can have its own life cycle, data, and service levels. By using a child case for the Repair phase, you can allow the parent case to continue independently of the child case processes. References: https://community.pega.com/knowledgebase/articles/case-management/88/creating-child-cases

 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 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 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

To implement this requirement, you can add an Approve /Reject step and enable approval from email and mobile. This way, sales managers can approve sales quote proposals by clicking a link in an email or by using their mobile devices. References: https://community.pega.com/knowledgebase/articles/case-management/88/configuring-approval-email-and-mobile

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

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 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 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 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

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

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 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