Here are all the actual test exam dumps for IT exams. Most people prepare for the actual exams with our test dumps to pass their exams. So it's critical to choose and actual test pdf to succeed.

Exam PEGACPSA23V1 Topic 1 Question 31 Discussion

Actual exam question for Pegasystems's PEGACPSA23V1 exam
Question #: 31
Topic #: 1
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, the user submits the request for a review of the patient's insurance policy. Because multiple users enter requests, the duplicate requests can occur. A request is considered a duplicate if the patient name, procedure type, and procedure date match an existing request. You have been given two requirements:
Ensure that users can identify duplicate requests. If a case is duplicated, it is not written to the database.
Otherwise, write the case to the database. Which two options configure the application so that users can identify duplicate requests? (Choose two)

Suggested Answer: B,C Vote an answer

by Tim at Jul 04, 2024, 05:46 AM

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
Nick name: Submit Cancel
oldsport
2025-11-27 17:44:30
Selected Answer: AB
Correct Answer

A. Configure weighted conditions
B. Add a duplicate search step to the case life cycle design

Why This Is Correct

A: Weighted conditions define what makes a case a duplicate. For example, matching the patient name, procedure type, and procedure date can be assigned weights. Pega uses these weights to determine if a case is a duplicate and should be blocked from being saved. This works together with the duplicate search step to identify duplicates accurately.
B: Adding a duplicate search step in the case life cycle allows Pega to automatically check for duplicate cases at a specific point before the data is saved to the database. This ensures that users are notified if a similar case already exists, preventing duplicate entries. It is the standard method in Pega Infinity 24 for handling duplicates.

Why Other Options Are Incorrect

C: Using a decision table with a decision shape is not required for Pega’s standard duplicate search feature. Decision tables are typically used for other business logic, not for the built-in duplicate detection.
D: Validation rules only check the correctness of input values within a case. They cannot compare the current case with existing cases to detect duplicates.

Key Point

To prevent duplicate cases in Pega Infinity 24:

- Use the duplicate search step in the case life cycle before data submission.
- Configure weighted conditions to define what fields must match for a duplicate case.
- Avoid relying on decision tables or validation rules for standard duplicate detection, because they are not designed for that purpose.

Glossary (Pega-Specific Terms)

- Weighted Conditions: Rules that assign importance to fields to determine if a case is a duplicate.
- Duplicate Search Step: A case life cycle step that checks for existing cases with similar data.
- Validation Rule: A rule that checks whether a field value is valid but cannot compare across multiple cases.
- Case Life Cycle: The sequence of stages and steps that a case goes through from creation to completion.

See: https://academy.pega.com/topic/duplicate-search/v7
upvoted 1 times
...
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.