In case management within Pega, when processing a parent case (P-l) with two child cases (C-l and C-2), the typical configuration requires that both child cases be resolved before the parent case can be resolved. This ensures that all related activities and requirements in the child cases are completed before the overall process (represented by the parent case) is considered complete. This approach is crucial for maintaining the integrity of the case processing lifecycle and ensuring that all necessary tasks are completed before concluding the parent case.

For an internet provider's quiz designed to recommend internet speeds based on varying customer usage profiles, including differentiating between residential and business needs, employing a decision mechanism that efficiently handles multiple input factors is key.
* A. Configure a decision table: Decision tables are ideal for scenarios where the output (recommended internet speed) depends on multiple conditions (quiz answers about internet use). They offer a clear, concise way to map various combinations of inputs to their corresponding outputs, making it easy to update and manage as new conditions or outcomes are introduced. This configuration supports dynamic and nuanced decision-making based on customer responses.
Configuring a view with quiz questions (B) is necessary for collecting inputs but does not determine the outcome. A decision tree (C) could also be used but might become complex with multiple branching conditions. A process with multiple decision shapes (D) could handle the logic but may be less efficient and harder to maintain than a decision table.

To meet management's requirement to only record cases that update an account, configuring the case type to start as a temporary case is essential. This configuration prevents the case from being permanently stored unless specific conditions are met. Additionally, applying a when condition after the first step to check if the case requires updating and then persisting it only if true ensures that only relevant cases are saved. This approach maximizes efficiency and data relevance by only retaining records of cases that lead to account modifications.