PEGACPSA23V1 Exam Dumps : Certified Pega System Architect

In the context of creating a customer loyalty account where the customer's contact information is captured and displayed within the case, organizing and relating this data efficiently is key.

• B. An Embedded data field: This option allows the contact information (name, email, phone number, address) to be structured as part of the case data in a coherent and integrated manner. Embedding this information ensures it is directly associated with each loyalty account case, facilitating data management and access within the application's data model.

A Data reference field (A) links to data instances outside the case, which is not the primary requirement here. A Case reference field (C) is used for linking cases together, which does not apply to this scenario of capturing contact information. A Query field (D) is intended for retrieving data based on a query, which is not relevant for directly embedding and displaying entered contact information within a case.

Service Level Agreements (SLAs) in Pega are used to define and enforce time limits for completing work and other time-based conditions:

B. A transaction review is completed within 24 hours. This is a direct application of SLAs, where a specific time frame (24 hours) is set as a target for completing a process step, such as a transaction review. SLAs ensure that such time-bound requirements are met, facilitating prompt and efficient service delivery.

In a Credit Card Payment case type, configuring the pySetFieldDefaults data transform to set the default value of the payment amount to the minimum amount due is the most straightforward approach. This data transform is used to initialize default values for properties when a case is created. It ensures that whenever a new case is started, the payment amount field is automatically populated with the minimum amount due, simplifying the user's task and reducing the likelihood of errors.