Pegasystems Certified Pega System Architect 23 PEGACPSA23V1 Exam Practice Test

Answer : A, C

Local data storage in Pega is typically used for purposes that require data to be readily accessible within the application itself, without the need for frequent external calls. It is ideal for: A. Defining valid values for a property, where a predefined list of values needs to be available for selection within the application, ensuring consistency and validation of data input. C. Storing reference data, which includes static or semi-static data used across the application, such as country codes, department codes, or pricing tiers. This data is integral to the application's operations and is used to populate fields, ensure data integrity, and drive business logic.

Answer : C, D

Configuring a mobile channel in App Studio supports various features that enhance the user experience and application security on mobile devices:

C . Configure a left swipe behavior to open a message. This use case is supported by configuring gesture-based interactions in a mobile app, allowing users to use swipe gestures to access functionalities like opening messages, which enhances usability and interaction in the mobile environment.

D . Lock the application after 20 minutes of inactivity. Setting security features such as automatic locking after a period of inactivity is crucial for maintaining security on mobile devices, protecting sensitive data from unauthorized access.

Answer : B

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.

Answer : B

In Pega, calculating values such as total working hours, sick hours, and vacation hours often involves using data transforms to manipulate and set property values based on logic defined within the application. A 'Calculate field' in a data transform would allow for the dynamic calculation of these values based on inputs such as logged time entries, absence records, and other relevant data inputs. This method is efficient for real-time computation and updates of calculated fields within a table or data page.

Answer : A

To configure the requirement that allows a customer to update their address at any point during case processing, including submission, verification, and approval of the new address, an approach that provides flexibility and accessibility throughout the case lifecycle is needed.

A . Add a case-wide optional action to the workflow for the address submission: This configuration enables the address update functionality to be accessible at any stage of the case processing. A case-wide optional action ensures that the customer can initiate the address change process whenever necessary, without being constrained by the current stage or step in the case. This approach aligns with the requirement

Answer : B

For a purchase request list report that includes columns for case ID and regional cost center, and with a requirement to show the total of purchase requests for each regional cost center, summarizing data correctly is essential.

B . Summarize the case ID column by count: This configuration tallies the number of purchase requests (case IDs) for each regional cost center, effectively meeting the manager's requirement. By summarizing the case ID column by count, the report will display the total number of

Answer : C

To set a fixed yearly fee of USD 75 in a Credit Card Payment case type, the most straightforward and appropriate method is to use a data initialization configuration where the Yearly fee field is set to 75. This approach involves configuring the data model or the default value setting within the case type or relevant data transform to initialize the Yearly fee field at case creation. This ensures that the field is consistently set to the correct amount across all cases without requiring calculations or validations that are meant for data integrity or conditional logic.