PEGACPSA23V1 Exam Dumps : Certified Pega System Architect

When diagnosing a problem with a calculated property value that is returning an unexpected result, the Trace tool in Pega is invaluable for investigating the issue without impacting application performance. Specifically, the use of Breakpoints and the Watch function can provide deep insights:

• A. Breakpoints: Allow you to pause the execution of the process at specific points, making it easier to examine the state and values of properties at those moments. This can help in identifying where in the process the unexpected value is being set or calculated.
• C. The Watch function: Enables you to monitor the values of specified properties as the process executes. This can be particularly useful for tracking how the value of the calculated property changes over time or at specific steps in the process, helping to pinpoint the cause of the unexpected result.

The Event monitor (B) and The Clipboard tool (D) are valuable features within Pega's diagnostic tools suite, but they serve different purposes. The Event monitor is more about tracking and analyzing system events, while The Clipboard tool is used for viewing and manipulating the current state of clipboard pages, not specifically designed for diagnosing problems with property calculations in the same direct manner as Breakpoints and the Watch function.

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.

For accommodating passengers traveling with service animals, efficiently capturing necessary information (type of animal, size, and medical information) is critical. This requirement is conditional, triggered only when a passenger declares travel with a service animal.

• A. Add a process to the case life cycle for service animal accommodation and apply a condition: This option allows for the integration of a dedicated process within the overall case life cycle specifically for gathering service animal information. The process is conditionally executed, based on whether the passenger has declared the need for service animal accommodation. This ensures that the additional information is requested only when relevant, keeping the case life cycle streamlined and focused.

Applying an optional action (B) offers flexibility but might not guarantee the collection of this information as part of the standard workflow. Configuring a separate stage (C) could unnecessarily segment the case life cycle, especially if service animal accommodation is a conditional step rather than a distinct phase. Creating a child case (D) for service animal accommodation could complicate case management, especially for a requirement that is inherently part of the main travel arrangement process rather than a standalone case.