Comprehensive and Detailed Explanation From Exact Extract:
This question tests Pega Express benefits.
* A: Correct. Reduces risk, ensures consistency.Extract: Pega Academy,Pega Express: "Pega Express manages risk and consistency."
* B: Incorrect. Established, not new.Extract: Pega Academy,Pega Express: "Pega Express is a proven methodology."
* C: Incorrect. Supports iterative approaches.Extract: Pega Academy,Pega Express: "Pega Express supports Agile delivery."
* D: Correct. Client-focused and outcome-driven.Extract: Pega Academy,Pega Express: "Pega Express prioritizes client outcomes."
* Pega Academy,Business Architect '23 Mission; CPBA Study Guide 8.8, Pega Express; Pega Help,Pega Express Benefits.

Comprehensive and Detailed Explanation From Exact Extract:
This question tests stage configuration for conditional skipping.
* A: Incorrect. "Never skip" prevents automatic resolution when the customer declines.Extract: Pega Academy,Case Management - Stages: "Stages can be configured to skip based on conditions."
* B: Incorrect. Process-level conditions don't control stage entry; stage conditions do.Extract: Pega Academy,Process Design: "Processes execute within stages, but stage entry is controlled by stage conditions."
* C: Correct. A skip condition on the Customer Survey Stage (e.g., survey interest = false) resolves the case.Extract: Pega Academy,Case Management - Stages: "A stage can be configured to skip with a custom condition, resolving the case if the condition is met."
* Pega Academy,Business Architect '23 Mission; CPBA Study Guide 8.8, Case Lifecycle; Pega Help, Configuring Stages.

Comprehensive and Detailed Explanation From Exact Extract:
This question tests the concept of Personas in Pega, which define user roles with specific channels, routing, and permissions, as covered in the CPBA curriculum.
* A: Incorrect. Limited channel interfaces may require channel configuration, not a new Persona.Extract:
Pega Academy,Personas and Channels: "Channels are configured separately from Personas to support interfaces."
* B: Incorrect. An additional user is managed by creating an operator, not a Persona.Extract: Pega Academy,Work Management: "New users are added as operators, not Personas."
* C: Incorrect. A new Case Type doesn't inherently require a new Persona unless specific roles are needed.Extract: Pega Academy,Case Management: "Case Types define workflows, not user roles."
* D: Correct. A new combination of channel, routing, and permissions defines a new Persona.Extract:
Pega Academy,Personas and Channels: "A Persona is created when a unique combination of channel access, work routing, and permissions is required for a user role."
:
Pega Academy,Business Architect '23 Mission, Module on Personas and Channels.
Pega Certified Business Architect Study Guide, Version 8.8, Section on Personas.
Pega Help Documentation,Configuring Personas.

In Pega, optional actions allow users to perform actions that are not part of the primary process flow but can be performed if needed. This is particularly useful for updating user profile information which may not always be required during the order placement stage. By adding a set of optional actions to the case workflow, customers can update any of the user profile pages individually without disrupting the main flow of the case.
Reference: Pega Academy - Configuring optional actions: Optional actions are used to configure actions that a user can perform at any time during the case lifecycle, providing flexibility and user control.