Certified Pega System Architect 24 Free Sample Questions

The Split Join shape is the ideal Pega construct for executing multiple independent flows in parallel and waiting for all to complete. By placing a condition on the flow leading to the risk team approval, it will only execute when the loan amount is USD 50,000 or more, satisfying the requirement for parallel approval efficiently within a single stage. A sequential process is inefficient. A child case adds unnecessary complexity for a task that is part of the same lifecycle.

The Requestor scope creates a single instance of the data page for the user's session, which is shared across all threads (cases, browser tabs). This perfectly matches the requirement to load the data once per session and ensures consistency while minimizing redundant API calls. Thread scope would create a new instance for each case. Node scope would share the data across all users on that server node, which is not what the requirement specifies.

In Constellation, the Table view is the standard and most appropriate component for displaying a list of records with multiple columns, such as attachment name, icon, and date. It provides built-in features for sorting, filtering, and pagination. A Field Group is for organizing related fields of a single record. A Summary Panel is for displaying key-value pairs. A List view is a simpler component, but the Table is better suited for structured, multi-column data.

This scenario is the classic use case for a framework/implementation pattern. The core, reusable claims logic should be in a Framework layer application. Each subsidiary (Auto, Home) should have its own Implementation layer application that is built on the framework. This allows them to inherit all the core functionality while having the flexibility to override rules for their specific needs, such as UI branding and validation, promoting reuse and maintainability.

This is false. SLAs can be configured at multiple levels in a case lifecycle. While they are commonly applied to individual assignments (tasks), they can also be set for an entire case type (overall case deadline) and for individual stages (stage-level deadline), providing granular control over timeliness.

A Summary report is designed for aggregation. By grouping the report data by the package status property (pyStatusWork) and using the Count aggregate function, the report will display exactly what is required: a count of packages for each distinct status ('Pending', 'In Transit', etc.). A List report would simply show all individual packages.

PegaUnit tests use assertions to automatically validate outcomes. The correct approach is to define the input data (e.g., set .PurchaseAmount to 1500) on the Setup & Cleanup tab, and then on the Results tab, create an assertion of type 'Property' to validate that the output property .CustomerLevel has the expected value of "Gold" after the data transform runs.

The Wait step is specifically designed for this purpose. It allows a case to pause its processing at a specific point in the flow until one or more defined conditions are met, such as a property being set to a specific value or a certain amount of time elapsing. In this scenario, it would be configured to wait until the property holding the vendor's clearance code is no longer null.

The PegaRULES:User4 role provides basic user-level access, which includes the ability to view and run reports that they have access to. The PegaRULES:WorkMgr4 role has additional privileges, including the ability to create and modify reports. The PegaRULES:SysAdm4 and PegaRULES:SysArch4 roles have even higher levels of administrative and development privileges.