Pegasystems PEGACPSA23V1 Practice Exam Questions & Answers

To design the case so that the Item Return stage is skipped if the item will not be returned, the best approach is:

B . Add a condition to skip the Item Return stage when a return is not necessary. This configuration involves setting a condition at the beginning of the Item Return stage or prior stages, determining whether the return is necessary based on case data (e.g., a property indicating item condition or customer decision). If the condition evaluates to true (no return needed), the process skips the Item Return stage and proceeds to the next appropriate stage.

To define the scope of a Data Page that holds currency exchange rates for all users:

A . Application. Setting the scope of the Data Page to Application ensures that the exchange rates are maintained consistently across all users and sessions, without duplicating data for each user, node, or requestor. This is particularly effective for data like currency exchange rates that are universal and do not change from user to user within the same application runtime.

For a user view that includes a list of four urgency options selectable by radio buttons, the goal is to present a single choice among predefined options in a user-friendly manner.

C . Configure a picklist with radio buttons for the urgency options: This approach directly meets the requirement by allowing users to select one urgency level from the provided options using radio buttons. A picklist configured with radio buttons effectively presents discrete choices in a clear format, ensuring that only one urgency option can be selected at any time, which aligns with the functionality described.

Configuring a field group (A) is generally used for grouping related fields but does not inherently provide the singular selection mechanism of radio buttons.

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 grant User A access to the 'My Cases' page, which User B has, the most effective method would be:

C . Update the User A account to access the same portal as User B. This solution ensures that User A has the same structural access as User B, including all the pages and capabilities available in the portal. The portal configuration typically includes access to various pages like the 'My Cases' page.

Options A, B, and D do not specifically ensure that User A gains access to the 'My Cases' page as they do not address portal-level access settings.

Creating a new rule in Pega Platform is appropriate when a specific behavior or functionality not provided by out-of-the-box features is needed. In this case, a developer creating a parallel process to audit changes made by a service agent requires a new rule. This rule will handle the logic and flow for tracking and documenting changes in a separate process, ensuring that the audit trail is maintained without affecting the primary case processing, aligning with best practices for maintaining system integrity and traceability.

Given a data page set to reload if older than 30 minutes, understanding the timing for when the data page is reloaded is essential for ensuring that users have the most current information. The data page is created at 7:43. Based on the Reload if Older Than setting, it will reload if accessed after 30 minutes from its creation or the last reload.

C . 8:40: The data page would be reloaded at 8:40 because this is the next access time that falls outside the 30-minute validity period established from the data page's last known load time or creation. Although the user refreshes the product information at 8:10 and 8:45, the key moment for reload based on the given timeline and settings would be 8:40, which is 30 minutes after the 8:10 refresh, not 8:45 since that's the time of access, not reload.

The options 8:13 (A) and 8:10 (B) are too soon for a reload based on the initial creation time and do not account for the 30-minute refresh policy correctly. Option D (8:45) represents a time of user action, not the actual reload based on the described criteria.