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)

Drag the appropriate ruleset version type on the left to the corresponding scenario on the right.

You are configuring duplicate case search logic in a case type. How do you ensure that resolved cases are not evaluated as potential duplicates?

Several Development teams work on different enhancements.
The release date for each enhancement is uncertain. Which two options allow each team to keep its work separate? (Choose Two)

You are configuring an accident claim case with two child cases for an automobile insurance company, as shown in the following figure:

The business requirement changes to allow the parent case to continue independently of the child case processes How do you configure the Wait step for this requirement?
Available Choices (select all choices that are correct