PEGACPSA23V1 Practice Questions

When configuring the "Search duplicate cases" step in a Pega application, especially for IT ticketing

systems, the primary aim is to identify multiple tickets raised for the same underlying issue. The

most straightforward and effective criterion for identifying duplicates in this context is the issue type,

such as "the office Wi-Fi is down."

B . Issue type is same: This option targets the core reason behind the creation of a ticket. Since

multiple individuals can report the same issue from various departments or locations, filtering by the

issue type ensures that all reports concerning a single problem (e.g., Wi-Fi outage) are identified as

duplicates. This approach helps in consolidating the efforts to address and resolve the issue

efficiently, avoiding redundant work.

Filtering by the name of the submitter, department, or office location (Options A, C, and D) might

miss duplicates reported by different users or from different areas, making "Issue type is same" the

most logical and effective criterion for identifying duplicates in IT ticketing scenarios.

Reference: Pega's official documentation on case management and the "Search duplicate cases" step

provides guidance on setting up duplicate search criteria based on the specific needs of the

application, emphasizing the importance of choosing criteria that accurately reflect the nature of the

duplicates being targeted.

Conditional processing within a case type in Pega is used to determine the flow of cases based on

specific criteria:

A . A scholarship eligibility application requires students to enter standardized test scores, Students

with qualifying test scores can schedule an interview. Students without qualifying test scores receive

a rejection email. This scenario clearly requires conditional processing to route students based on

their test scores, either towards scheduling an interview or receiving a rejection.

D . A shopping application requires a guest to fill out payment information. A user who enters a

membership number skips the payment information step. This use case also demonstrates the need

for conditional processing, where the presence of a membership number changes the steps a user

must complete.

In Pega, when referencing a property within a page group, the correct syntax involves specifying the

page group name followed by the index in parentheses, and then the property name. In this case,

.Address(Home).State correctly specifies that the "State" property should be accessed from the

"Home" index within the "Address" page group. This syntax is essential for accurately navigating

complex data structures in Pega applications.

When configuring an external data source using the Integration Designer in Pega, essential

information includes:

C . A plan for mapping the data and REST response fields. Effective integration with an external data

source requires a clear mapping plan to align the data structure of the source with the data model of

the Pega application. This includes configuring how the REST API responses are parsed and how

individual data fields are mapped to the properties in Pega.

To improve the performance of a report listing customer order cases where the Order Total value is a

critical criterion:

A . Order Total. Optimizing the Order Total property allows for faster sorting and filtering operations

specifically on this field, which is crucial for performance, especially when dealing with large datasets

where queries are based on financial thresholds.

In Pega, when configuring data pages to source UI controls such as drop-down lists, it's crucial to

select the configuration that optimally uses memory and efficiently serves the data to the users. For

this scenario, the correct answer is Option F: List, ACME-Products-Data-Color, ReadOnly, Node.

List vs. Page: Choosing 'List' is appropriate because the requirement is to populate a drop-down list

with multiple entries (colors in this case). 'Page' would be used for single record data, which is not

the case here.

Object Type: 'ACME-Products-Data-Color' is chosen because the data represents a list of color

options provided by the manufacturer, which is typically static reference data, fitting the 'Data' class

layer rather than the 'Work' layer which is used for case management or the 'Work-ColorFeedback'

which would be used for storing feedback or interactions specific to colors.

Edit Mode: 'ReadOnly' is the correct mode since users are selecting a color from a pre-defined list

and are not expected to edit these values directly.

Scope: 'Node' is selected to minimize memory usage. By setting the scope to 'Node', the data page is

loaded once per node (server instance) and shared across all requestors (users) on that node, which

is memory efficient for data that doesn't change often and is applicable across all users, such as a list

of colors.

This configuration ensures that the data page is loaded efficiently in a read-only list format at the

node level, reducing the overall memory footprint while making the color selections available across

the application.

Reference: Pega Academy's Data Pages module, which covers data page types, scopes, and best

practices for optimizing application performance and memory usage.

In Pega, enabling field-level auditing for properties is typically done through the property rule form.

By enabling the auditing feature on specific property rule forms, changes to those properties are

automatically tracked and recorded by the system. This setup is essential for compliance,

transparency, and historical data analysis purposes, allowing organizations to monitor and audit

changes to critical data fields systematically.

To locate the "Purchase Insurance" field used in testing the calculation of the "TotalCost" field

without a configured UI:

B . User Pages. In the Clipboard, User Pages typically hold data related to the current user session

and case processing, including fields like "Purchase Insurance" which are manipulated during a case

session and influence other data calculations in the case, such as "TotalCost".

When diagnosing an issue with a calculated property value using the Tracer tool:

B . Breakpoints. This feature allows you to pause the execution at certain points, enabling you to

inspect the processing of the rules and properties, which is helpful in identifying where and why a

property is not calculating as expected.

C . The Watch function. By watching specific properties, you can monitor changes to their values in

real time as the process executes, which helps in determining the point at which the unexpected

result occurs, all with minimal overhead on application performance.

For ABC BankCorp's mobile app experience related to the Transaction Dispute application, certain

requirements necessitate configuring distinct mobile app channels to accommodate different

functionalities or visual designs for users and CSRs.

A . CSRs can create other case type instances on the mobile app: This functionality difference

between what CSRs and users can do within the app indicates the need for separate app channels.

The ability of CSRs to handle additional case types beyond what is available to general users requires

a distinct channel configuration to support the specialized functionalities needed by CSRs.

B . Mobile app color palettes are different for users and CSRs: The requirement for different color

palettes for users and CSRs pertains to the app's visual design and branding. To ensure that each

group experiences the app with the intended branding elements, separate app channels are required

to implement the distinct color palettes and themes.

Customizing currency units and date/time format according to the user's location (C) can typically be

achieved within a single app channel through localization settings and does not inherently

necessitate separate channels. Supporting all mobile phone operating systems (D) is a compatibility

requirement that is also not a determining factor for creating distinct channels but rather relates to

the app's development and testing across platforms.

Reference: The principles of mobile app development in Pega, as detailed in Pega's mobile

documentation, include the creation of distinct channels for different user roles or branding needs to

ensure a tailored and cohesive app experience for various user groups.