Free PEGAPCSA87V1 sample questions

Correct answer: In the 'Compliance Review' stage settings, define a 'Skip stage when' condition that evaluates if the loan amount is less than or equal to $1,000,000.

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.

Correct answer: True

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.

Correct answers: Configure the approval step to route to the user's manager.; Enable the 'Disallow self-approval' checkbox in the advanced section of the approval step.

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.

Correct answer: A case type setting for the Case ID prefix.

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.

Correct answer: On the 'Setup & Cleanup' tab of the unit test case.

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.

Correct answer: Configure Field Level Auditing on the `.PermitStatus` property.

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.

Correct answer: Attach content control

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.

Correct answer: A case lifecycle with a 'Data Collection' stage, a Decision Shape in the process flow that calls a Decision Tree to evaluate complexity, routing within the assignment shape to the appropriate work queue, and a Goal and Deadline defined in an SLA rule on the assignment.

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.

Correct answer: Scope: Requestor, Refresh Strategy: Do not reload when.

The 'Requestor' scope creates a single instance of the data page for the entire user session. Since the data is static for the session, the 'Do not reload when' refresh strategy is appropriate, meaning the page is loaded once on the first access and then reused throughout the session without making further API calls. 'Thread' scope would create a copy for each case/work item, which is inefficient. 'Node' scope would share the data across all users on the same server node, which is also a valid performance strategy, but 'Requestor' scope precisely matches the 'once per user session' requirement.

Correct answer: A Validate rule

A Validate rule is used for business logic validation that involves comparing property values. In this case, it would compare the 'Date of Birth' property with the current date. Edit Validate rules are for single-field format validation (e.g., ensuring a string is a valid email format) and are less suitable for comparisons. Triggers and Declare Expressions are for procedural logic and calculations, not validation.