This sequence follows the standard Pega Express / Journey Centric Delivery project lifecycle phases (Discover, Prepare, Build):

1. Prepare for project kickoff meeting: This is the initial step in the Prepare phase. The Business Architect (BA) helps organize and prepare for the kickoff to align stakeholders on the project vision and scope (Minimum Lovable Product) defined during the Discover phase.
2. Capture sessions on discrete aspects of the case type: Following the kickoff, the team conducts Directly Capture Objectives (DCO) sessions. Here, the BA and team drill down into the specific details ("discrete aspects") of the Microjourneys and Case Types to understand requirements.
3. Refine backlog stories: Once requirements are captured, the BA works to refine (groom) the user stories in the backlog. This involves adding acceptance criteria and details to ensure stories meet the "Definition of Ready" for the development team to build.
4. Playback configurations: Finally, after the development team has configured the solution based on the refined stories (during the Build phase), the BA leads or participates in Playbacks. These sessions demonstrate the configured application to stakeholders for validation and feedback.

Pega Academy - Pega Express Delivery Approach:

Context: "The Prepare phase starts with the project kickoff... During Prepare, you use DCO to define the solution details... You create and refine the backlog of user stories... You conduct Playbacks to validate the application with stakeholders."

Source: Pega Academy, "Pega Express methodology" and "Applying Pega Express Phases" modules.

Pega Academy - The Role of the Business Architect:

Context: "As a Business Architect, you... participate in refining the backlog... and reviewing completed configurations [Playback]."

Source: Pega Academy, "Business Architect" Mission, Module: "Role of a Pega Business Architect".

Pega Documentation - Journey Centric Delivery:

Context: Describes the flow from Project Initiation (Kickoff) -> Discovery/DCO (Capture) -> Construction (Refine/Build) -> Validation (Playback).

Reference: Pega Community / Pega Express "Delivery Phases" documentation.

In Pega Platform, reporting is categorized based on the type of metrics used: Business Metrics or Process Metrics.

Business reports analyze the actual data entered into a case to track operational performance or volume. The item "Total customer inquiry cases per state per product line" aggregates case data based on business properties (State and Product Line), classifying it as a business report.

Process reports track the performance of the workflow itself (how work is performed), utilizing system-generated metrics like time, effort, and SLA compliance. The item "Average duration and timeliness per assignment" measures the efficiency of task completion and adherence to deadlines, which identifies it as a process report.

Pega Academy, "Reporting concepts", Section: Business and process metrics.

Quote: "Business metrics represent the data that you enter into a case... Process metrics represent how work is performed."

Context: Defines the distinction between tracking case data (Business) vs. tracking time/throughput (Process).

Pega Platform Documentation, "Report Browser" & "Standard reports".

Context: Documentation on standard reports confirms that "Timeliness" and "Duration" fall under "Monitor Process" or "Analyze Performance" categories (Process reports), while case counts by property fall under "Analyze Quality" or "Monitor Assignment" business data views.

Route to a skilled work group: This is used when the assignment requires a specific skill (e.g., Russian language) or certification, and any available member of that group can complete it.

Route to a work queue: This is appropriate for an organizational unit like Accounts Receivable where the work (auditing billing requests) is generic and can be done by any available user in that team's queue.

Route to a specific user: This is used when the task must go to a single, named individual holding a specific role (e.g., a Vice President) regardless of their immediate availability or skill set.

Route to the current user: This maintains user affinity by ensuring subsequent steps in a sequential task or screen flow are assigned to the user who started the work, completing the series of screens.

Official Vendor Documentation (Pega Platform):

Reference: Pega Platform Documentation, Configuring Routing, "Routing work to users, work queues, or specific skill sets."

Details: This section details four primary routing types. Work Queue routing is used for teams/groups (like Accounts Receivable). Skill-based routing is for specific proficiencies (like speaking Russian). Specific User routing targets a unique person (like a VP). Current User routing ensures continuity.

Official Vendor Documentation (Salesforce Flow/Omni-Channel):

Reference: Salesforce Documentation, Omni-Channel Routing, "Routing Methods in Omni-Channel."

Details: Documents the use of Skills-Based Routing to match work items to agents with specific expertise (Russian speaker) and Queue-based routing for generic team assignments (Accounts Receivable).

Peer-reviewed academic publications (BPM/Workflow Management):

Reference: W. van der Aalst, A. H. M. ter Hofstede, B. Kiepuszewski, and A. P. Barros, Workflow Patterns, Distributed and Parallel Databases 14, 5-51 (2003). https://doi.org/10.1023/A:1022883727282.

Details: Discusses routing primitives. The Role-Based/Organizational Routing (Work Queue/Work Group) pattern is used for organizational units. The Resource-Based Routing (Specific User) pattern is for unique individuals. The Rerouting/Handover (Current User affinity) pattern ensures sequential execution by the same party.

Property reference: .Address(1).PostalCode

Field type: Single record data relationship

Property reference: .ShippingAddress.City

Field type: Text

Property reference: .BillingAddress.Telephone

Field type: Multiple record data relationship

Property reference: .Address(1).PostalCode

Field type: Single record data relationship

The .Address(1).PostalCode property indicates a specific postal code within a single address. The (1)

suggests it’s part of an indexed or paged list, but each PostalCode is a single entity within that

address record.

Reference: Pega Platform Business Architect Essentials, Chapter on Data Modeling.

Property reference: .ShippingAddress.City

Field type: Text

The .ShippingAddress.City property represents a single textual value for the city in the shipping

address. This is a straightforward text field.

Reference: Pega Platform Business Architect Essentials, Chapter on Property Types.

Property reference: .BillingAddress.Telephone

Field type: Multiple record data relationship

The .BillingAddress.Telephone property suggests there could be multiple telephone numbers

associated with the billing address. Therefore, this involves a relationship that can contain multiple

records.

Reference: Pega Platform Business Architect Essentials, Chapter on Data Relationships and Classes.

The validation rule is configured to trigger an error when two conditions are met simultaneously due to the "and" operator. The conditions are: 1) The Update Operator property is exactly "[email protected]", and 2) The Case Status property is any value other than "Open".

Option A is the only data set that satisfies both of these conditions. The Update Operator is "[email protected]" (satisfying the first condition), and the Case Status is "Resolved" (satisfying the second condition). Therefore, this combination correctly triggers the error message.

1. Pega Academy

Pega Business Architect (24.1) Mission

Module: Validating case data

Lesson: Configuring validate rules. This lesson explains how to combine multiple conditions using logical operators (AND/OR) to define specific validation logic.

2. Pega Platform™ 24.1 Documentation

App Studio

"Creating a validate rule." This document details the process of setting up validation conditions

specifying that when conditions are joined by "AND

" all conditions must evaluate to true for the validation to trigger.

3. Pega Platform™ 24.1 Documentation

Dev Studio

"Completing the Validate rule form - Conditions tab." This section explicitly describes how to define a set of logical expressions (conditions) that are evaluated in order. It clarifies that for an "AND" relationship

each expression in the set must be true for the validation message to be displayed.

Goal – 20

Deadline – 30

Passed Deadline - 40

To set the urgency values based on the described SLA behavior:

Initial urgency value: 10

When goal elapses: Urgency increases by 10 (Total: 20)

When deadline elapses: Urgency increases by 10 (Total: 30)

When passed deadline elapses: Urgency increases by 20 (Total: 50)

Thus, the urgency values at each milestone are:

Goal: 20

Deadline: 30

Passed Deadline: 50

Reference:

Pega Academy: Service Level Agreements (SLAs)

Pega Documentation: Configuring SLA Urgency and Escalation

Field: Total hours for each type of time tracked (work, vacation, sick)

Method: Calculation

Field: Cumulative total of all hours for the week

Method: Calculation

Field: Updated vacation and sick time balances

Method: Data transform

Total hours for each type of time tracked (work, vacation, sick)

Method: Calculation

The total hours for each type of time (work, vacation, sick) are derived by summing up the

respective hours entered by the employee for each day. This involves simple arithmetic operations

which are best handled by a calculation rule in Pega.

Reference: Pega Platform Business Architect Essentials, Chapter on Calculations and Decision Rules.

Cumulative total of all hours for the week

Method: Calculation

The cumulative total of all hours for the week is computed by summing up the total hours of work,

vacation, and sick time. This is another straightforward arithmetic operation that should be

implemented using a calculation rule.

Reference: Pega Platform Business Architect Essentials, Chapter on Calculations and Decision Rules.

Updated vacation and sick time balances

Method: Data transform

When the employee submits the timesheet, the application needs to update the vacation and sick

time balances by subtracting the entered hours from the available balances. This involves data

manipulation which is appropriately handled using a data transform. Data transforms in Pega are

used to copy and manipulate data.

Reference: Pega Platform Business Architect Essentials, Chapter on Data Transforms and Activities.

The statement is an accurate and official definition of Pega Cloud® Services. It is Pega's as-a-Service (aaS) offering, providing a fully managed environment for clients to build, deploy, and run applications built on the Pega Platform™. Pega handles the architecture, infrastructure, operational management, and security, allowing clients to focus on application development and business outcomes.

The "False" option is incorrect because the provided statement is the standard, official description of the Pega Cloud Services offering. It is not a client-managed solution, nor is it limited to just hosting; it is a comprehensive, fully managed service specifically for Pega Platform applications.

1. Pega Academy: In the Certified Pega Business Architect (CPBA) 24V1 learning path

the "Pega's Delivery Approach" module explains the different environments for Pega projects. The lesson on "Pega Express delivery" introduces Pega Cloud as the recommended

fully managed deployment environment. It emphasizes that Pega Cloud Services manages the platform

allowing the project team to focus on building the application.

2. Official Pega Documentation: The "Pega Cloud" section on Pega Community explicitly states: "Pega Cloud® is the fastest

easiest

and most cost-effective way to get started with Pega. It is a fully managed service that allows you to focus on creating applications that deliver business value

while Pega manages the platform and infrastructure for you." (Source: Pega Community

Pega Cloud Documentation

"Pega Cloud services" overview page).

3. Official Pega Documentation: The "Pega Cloud architecture and services" documentation further details the managed services provided

stating

"Pega Cloud is a fully managed cloud service from Pegasystems... Pega Cloud provides a secure

reliable

and scalable service for all your Pega applications and data." This confirms the "fully managed" nature of the solution for deploying Pega applications. (Source: Pega Community

Pega Cloud Documentation

"Pega Cloud architecture and services" section).

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.