Pegasystems PEGACPSA23V1 - Questions & Answers

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. Pega Academy's Data Pages module, which covers data page types, scopes, and best practices for optimizing application performance and memory usage.

In scenarios involving a large dataset, such as a database of over 10,000 book titles, the most efficient way to allow users to find and select an item is by using an autocomplete control. This approach enhances user experience by filtering options based on user input, making it easier to navigate through large lists of data.
Why not a drop-down? A drop-down control (Options A and B) would not be practical for such a large number of items because it would require loading all items at once, which can lead to performance issues and a poor user experience. Why an autocomplete control? The autocomplete control (Option C) is designed for scenarios like this. It allows the user to begin typing the name of a book, and the control suggests matching titles based on the input, narrowing down the options dynamically. This approach is much more userfriendly and efficient for large datasets.
Why sourced from a data page? Sourcing the autocomplete control from a data page (Option C) is the best practice because it allows for the efficient loading and caching of data. Data pages can be configured to refresh at appropriate intervals or under specific conditions, ensuring that the data is up-to-date.
Furthermore, using a data page abstracts the data source from the control, making the application easier to maintain and update. This setup ensures a smooth and efficient user experience, allowing for quick and easy selection from a vast database of book titles

Routing tasks to specific groups within an organization is a common requirement in case management systems. For the scenario involving voice over requests with distinct tasks for editors and actors, creating separate work queues for each group is the most straightforward and effective approach.
A . Create two new work queues, one for editors and one for actors: This option allows for the segregation of tasks based

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

In Pega applications, work parties represent entities associated with a case. When configuring status updates for patients who are not users of the application, it is essential to use a class that accurately represents external individuals. A . Data-Party-Person: This class is designed to represent individual people as parties in a case. Using this class to create a work party for a patient allows the application to store relevant personal information and contact details necessary for sending status updates about medical test processing. Since patients are the recipients of the information and not operators or organizational entities within the system, this class is the most appropriate choice. The other options, such as Data-Party-Operator (used for application users), Data-Party-Org (used for organizations), and Data-
Party-Com (used for commercial entities), do not fit the context of individual patients receiving updates.
Pega Academy's courses on case management detail the use of work parties in cases, explaining the purpose of various Data-Party classes and how they are applied in real-world scenarios to manage communications and interactions.

In the scenario where a customer service representative (CSR) might need to provide written information about different account types during a case, adding flexibility to the case lifecycle is key. C . Add a case-wide optional action: This approach allows the CSR to initiate the action of sending or requesting information at any point during the case, without being tied to a specific stage or assignment. Case-wide optional actions are accessible from anywhere within the case, providing the necessary flexibility to respond to the customer's request at the moment it occurs, regardless of the current case stage or assignment. The other options, such as adding a user view (Option A), adding an optional action to a specific stage (Option B), or adding a router (Option D), either limit the action to a particular context or don't directly address the need to provide information flexibly throughout the case lifecycle. Pega's case management documentation highlights the use of case-wide optional actions as a means to introduce flexibility into the case workflow, allowing users to perform actions that are relevant at any point in the case process, thereby enhancing the ability to respond to dynamic requirements and customer requests.