PEGACPSA88V1-QUESTION practice question 10 of 15

Users create Insurance Coverage Request Cases to authorize insurance payments. Users enter information that includes the name of the patient, the…

Full set: 82 questions
Users create Insurance Coverage Request Cases to authorize insurance payments. Users enter information that includes the name of the patient, the date of the procedure and the type of the procedure. After entering the information, user submits the request for a review of the patient's insurance policy. Because multiple users enter requests, duplicate request can occur. A request is considered a duplicate if the patient name, procedure type, procedure date match an existing request. You have been given two requirements: - Ensure that users can identify duplicate requests. - If a case is duplicate, it is not written to the database. Otherwise, write the case to the database. Which two options configure application so that users can identify duplicate requests? (Choose two)
Answer options
A: Add a duplicate search step to the case life cycle design. Correct answer
B: Configure a duplicate search decision table and add it to a Decision shape
C: Configure weighted conditions. Correct answer
D: Configure a validate rule to validate matching cases.
Correct Answer:
A. Add a duplicate search step to the case life cycle design.; C. Configure weighted conditions.
Explanation

Pega Platform provides a dedicated, out-of-the-box feature to identify and manage duplicate cases. This functionality can be configured in two primary ways: as a "Search duplicate cases" step in the case life cycle or as a pre-creation check on the case type rule itself. Both methods are configured using either basic conditions (all must match) or weighted conditions (a scoring system). Option (A) describes adding the process step, which is a primary implementation method. Option (C) describes one of the two mechanisms (weighted conditions) for defining the search logic. Together, these represent the key configuration actions required to implement the duplicate case identification feature as taught in the official curriculum.

Why Incorrect

B. Configure a duplicate search decision table and add it to a Decision shape A decision table is a rule used to evaluate a set of conditions against data already present on the clipboard; it does not inherently perform a database search for other cases.
D. Configure a validate rule to validate matching cases. A validate rule is used to verify the format and content of data entered by a user on a form. It is not designed to query the database to compare the current case with other existing cases. ---

References

1. Pegasystems Official Documentation - Pega Platform 8.8: "Searching for duplicate cases"

Section: "Search for duplicates in the case life cycle"

Content: This section explicitly details adding the "Search duplicate cases" automation step to a case type's life cycle. It states, "To guide users who create cases and avoid processing duplicate requests, you can add the Search duplicate cases step to your case type." This directly supports option A.

Section: "Defining duplicate cases"

Content: This section describes the two logic types for defining a duplicate: "To define a duplicate case, you create a set of conditions with case properties and their values. You can create basic conditions that a case must meet to be a duplicate, or you can create a set of weighted conditions..." This directly supports option C as a valid configuration method.

2. Pega Academy - System Architect 8.8 Mission: "Duplicate cases" Module

Lesson: "Configuring a duplicate case search"

Content: This training lesson demonstrates the process of adding the "Search duplicate cases" step to a flow (supporting option A) and then configuring its properties by adding conditions. It shows the options for "Basic conditions" and "Weighted conditions" (supporting option C) as the way to define the duplicate-checking logic. The lesson presents these as the standard, best-practice methods.

Scroll to Top