CPSA - Certified Pega System Architect Case Lifecycle Management Questions and Answers 1 — Questions and Answers
Question 1: A case type for processing loan applications follows a standard path: Submission, Review, and Disbursement. However, if an application is flagged for potential fraud during the Review stage, it must undergo a separate Fraud Investigation process. How should a System Architect model this exception in the case lifecycle?
- As an optional process available in the Review stage.
- As a separate primary stage after the Review stage.
- As an alternate stage that the case can move to from the Review stage. (Correct answer)
- As a subcase that is launched during the Review stage.
Correct answer: As an alternate stage that the case can move to from the Review stage.
Alternate stages are designed to handle exceptions or deviations from the primary, or 'happy path,' sequence of a case. When the fraud condition is met, the case can be programmatically transitioned to the Fraud Investigation alternate stage. This keeps the primary path clean and clearly models the exception handling process.
Question 2: During the 'Onboarding' stage of a new employee case, the user may need to update the employee's contact information at any time. This action involves a single screen update. Which of the following is the most appropriate way to configure this functionality?
- An optional process available for the entire case.
- A multi-step process within the Onboarding stage.
- A primary step in the Onboarding stage.
- An optional user action available for the Onboarding stage. (Correct answer)
Correct answer: An optional user action available for the Onboarding stage.
Optional actions are used for tasks that users can perform out of the main sequence. Since this is a single-task action (updating one screen), it should be configured as an optional user action. It can be made available for a specific stage or the entire case.
Question 3: What is the primary function of a stage in a Pega case lifecycle?
- To update the work status of a case.
- To represent a single task or assignment for a user.
- To group related steps and represent a high-level milestone or phase in the case. (Correct answer)
- To define the service-level agreement (SLA) for the entire case.
Correct answer: To group related steps and represent a high-level milestone or phase in the case.
A stage represents the first and highest level of organizing work within a case type. It acts as a container for related steps and processes, signifying a major milestone or phase in the case's journey towards resolution.
Question 4: A System Architect is designing a case lifecycle and needs to ensure the case status is automatically updated to 'Pending-Approval' as soon as the case enters the 'Manager Approval' stage. Where should this status update be configured?
- In the properties of the flow rule for the first step of the stage.
- In the properties of the 'Manager Approval' stage itself. (Correct answer)
- Using a data transform rule that is called by every step in the stage.
- On the case type rule form, in a dedicated status management section.
Correct answer: In the properties of the 'Manager Approval' stage itself.
Pega Platform allows direct configuration of the case status on stage entry. By setting the 'Set case status on stage entry' field in the stage's properties, the status is automatically updated when the case transitions into that stage, ensuring consistency and simplifying the design.
Question 5: Which of the following best describes the difference between an optional process and an optional user action?
- An optional process can only be configured case-wide, while an optional user action is always stage-specific.
- An optional process involves multiple steps, while an optional user action is a single-step task. (Correct answer)
- An optional process automatically advances the case, while an optional user action requires manual intervention.
- An optional process is initiated by the system, whereas an optional user action is initiated by the user.
Correct answer: An optional process involves multiple steps, while an optional user action is a single-step task.
The key distinction is complexity. An optional user action is configured for a single-step task, typically a flow action. An optional process is used for a series of steps and calls an entire flow rule. Both can be configured to be available case-wide or for a specific stage.
Question 6: In a case lifecycle for a purchase request, the 'Fulfillment' stage should only be executed if the total amount of the request is over $1,000. For requests under this amount, the stage should be skipped automatically. How can this logic be implemented?
- By adding an optional action to the preceding stage to jump to the next stage.
- By configuring a 'Skip stage when' condition in the properties of the 'Fulfillment' stage.
- By creating an alternate stage for requests under $1,000. (Correct answer)
- By using a decision shape in the last step of the preceding stage to route the case.
Correct answer: By creating an alternate stage for requests under $1,000.
The 'Skip stage when' condition, found in the stage configuration options, is the declarative, out-of-the-box way to implement this requirement. It allows you to define a when rule that, if it evaluates to true upon attempting to enter the stage, will cause the case to bypass the stage and move to the next one automatically.
