The business requirement is to allow the parent case to proceed independently of its child cases. The Wait step is used to pause a case, often to wait for child cases to reach a certain status. To meet the requirement for independent processing, the Wait step must be configured to not enforce a dependency. Option A describes configuring the step to allow the parent case to continue regardless of the child case status, which directly fulfills the requirement by effectively removing the pause condition related to the child cases.

B. Configure the step to continue the parent case when the child cases reach auditor approval.

This creates a specific dependency on a child case status, forcing the parent case to wait, which contradicts the requirement for independence.

C. Configure the step to continue the parent case when the child cases reach the payment pending review status.

Similar to option B, this imposes a wait condition based on a child case status, preventing the parent case from proceeding independently.

D. Configure the step so that only one child case must be resolved before the parent case can continue.

This configuration still forces the parent case to wait for a child case to be resolved, which is a dependency, not independent processing.

1. Pega Academy: Business Architect (24) mission

Module: Pausing and resuming case processing

Lesson: Pausing a case. This lesson explains the configuration of the Wait step

including options to wait for dependencies (like child cases) or to allow the case to proceed. The option to allow users to continue the process manually or to set no wait condition aligns with making the parent case independent.

2. Pega Platform Documentation: Adding a Wait step to a case. The documentation details the "Wait for" options

which include pausing until child cases are resolved or reach a specific status. To achieve independence

one would not select these dependency-based options and instead configure the step to allow immediate or manual continuation.