Pega Certified System Architect (pcsa) 87v1 Free Sample Questions

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.

Pega Platform provides a dedicated feature for formatting case IDs. In the case type's Settings tab, you can define a prefix for work items. This prefix can include text, dates, and other properties, and Pega automatically handles the sequential numbering. This is the standard best practice and does not require custom rule creation in most cases.

When creating a PegaUnit test case, the 'Setup & Cleanup' tab is used to define the test environment. You can specify a data transform to run before the test execution to populate the clipboard with the necessary pages and properties. This ensures the rule is tested under the correct predefined conditions.

Field Level Auditing is the declarative feature designed specifically for this purpose. By opening the property rule for .PermitStatus and enabling auditing on the History tab, the Pega Platform automatically creates History- instances whenever the property value changes, recording the old value, new value, operator, and timestamp. This is the most efficient and best-practice approach.

The 'Attach content' control is specifically designed for handling file attachments. When used in a Pega mobile app, it provides options to upload a file, take a photo with the camera, or record a video, leveraging native device capabilities. The Image control is for displaying images, not capturing them.

This option correctly combines the core Pega features needed. A staged case lifecycle is appropriate for FNOL. A decision shape using a decision tree (or table) is the correct way to automate the complexity evaluation. The routing logic should be configured on the assignment itself to direct it to the correct work queue based on the decision outcome. Finally, an SLA rule with a Goal (e.g., 2 hours) and a Deadline (4 hours) is the standard way to implement the timing requirement on an assignment.