PEGAPCSA87V1 Pega Certified System Architect (pcsa) 87v1 Practice Questions

Declare Expressions are designed for automatic calculations where a target property's value is derived from other source properties. By setting the target to .TotalLoanAmount and the expression to .PrincipalAmount + .FeesAmount, the Pega engine ensures that whenever the source properties change, the target is automatically and immediately recomputed. This is the most efficient and declarative way to meet the requirement.

The Tracer tool is the primary debugging utility for observing rule execution in real-time. By enabling the 'Rule Resolution' event type in the Tracer settings, a developer can see the detailed steps Pega's rule resolution algorithm takes to find and select a rule, including which rules were candidates and which were discarded based on class, ruleset, circumstances, and other factors.

True. Locking a ruleset version is a critical step in the deployment process. It makes the rules within that version immutable, ensuring that the version tested in a QA environment is the exact same version deployed to production, which is a fundamental principle of DevOps and release management.

To get only open cases, you must filter out resolved ones, typically by checking the work status. To find cases that have passed their deadline, you must filter on the .pySLAName property where its value is 'Passed Deadline'. Adding columns for case ID and urgency is for display, not for filtering.

To get only open cases, you must filter out resolved ones, typically by checking the work status. To find cases that have passed their deadline, you must filter on the .pySLAName property where its value is 'Passed Deadline'. Adding columns for case ID and urgency is for display, not for filtering.

Pega's class structure enables powerful rule reuse through inheritance. There are two types: Pattern inheritance (based on the class name structure, where YourOrg-YourApp-Work-CaseType inherits from YourOrg-YourApp-Work) and Directed inheritance (explicitly specified in the class rule form). This dual mechanism allows for flexible and extensive rule reuse across the application.

The best practice for displaying a variable number of items from a list is to use a repeating dynamic layout. This layout iterates over a source, such as a Page List property, and renders a section for each item. This is highly scalable and the standard Pega approach. Using multiple layouts with visibility conditions is inefficient and not scalable. A grid is a legacy control, and while it works, repeating dynamic layouts are more modern and flexible. A data page alone fetches data but does not render it in a repeating format; it must source a repeating layout.

In a data transform, the 'Set' action is used to assign a value to a target property. The 'Target' column specifies the property to be updated (in this case, .BillingInfo.PolicyNumber). The 'Source' column specifies the value or property to be copied from (in this case, .Insurance.PolicyID). The syntax does not require an equals sign '='. 'Update Page' copies an entire page structure, which is not what is required here. 'Append and Map to' is for lists.

The standard, most direct way to conditionally skip a stage is by configuring the 'Skip stage when' condition within the stage's properties in Case Designer. This keeps the logic encapsulated with the stage itself. Using a decision shape within the process is less efficient as the stage is still technically entered. A 'Change Stage' shape is for explicit transitions, not for skipping. A validation rule would prevent entry but not skip the stage gracefully.

This is true. In the Report Viewer tab of a Report Definition, you can enable the 'Display chart' option and select a chart type. You can also check 'Display summary data only in chart' to show details in the list below. When this report is added as a widget to a dashboard, it can render both the chart and the underlying data list.

First, the assignment must be routed to the manager. Then, the 'Self-approval' check ensures that if the creator is their own manager (e.g., a CEO), the approval is automatically sent one level higher.

First, the assignment must be routed to the manager. Then, the 'Disallow self-approval' check ensures that if the creator is their own manager (e.g., a CEO), the approval is automatically sent one level higher.