PEGACPSA88V1 Certified Pega System Architect (V8.8) Questions and Answers

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

Graphical user interface, text, application, email Description automatically generated

These two requirements can be supported by configuring a mobile channel in App Studio. A mobile channel allows you to define various settings and features for your mobile app, such as security, branding, navigation, gestures, push notifications, offline support, and so on. References: https://community.pega.com/knowledgebase/articles/mobile/86/configuring-mobile-app-channels

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

In these two situations, it is appropriate to use a decision table because they involve deriving values that have one of a few possible outcomes based on multiple variables. For example, the dance studio can use a decision table to recommend different membership types based on different combinations of number and type of dance classes. The hair care company can use a decision table to suggest different product lines based on different combinations of hair characteristics. References: https://academy.pega.com/topic/decision-tables/v1

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

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

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

This statement about responsive breakpoints is true. Responsive breakpoints are points at which the layout of a UI element changes based on the screen size or orientation of the device. By default, tables have two responsive breakpoints: one for tablet devices and one for phone devices. You can configure custom responsive breakpoints for other UI elements in App Studio. References: https://community.pega.com/knowledgebase/articles/user-experience/88/configuring-responsive-breakpoints

 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