Free PEGACPBA24V1 Practice Questions – 2026 Updated

In a Pega Agile project, the Business Architect (BA) is a key liaison between business stakeholders and the technical team. Their responsibilities include collaborating with stakeholders to define the vision and roadmap, which involves planning for current and future application needs (C). This plan is translated into a product backlog, which the BA is responsible for building and refining with user stories, thus managing the project team's backlog (A). To ensure the developed solution meets the business requirements, the BA also develops scenarios and acceptance criteria to test the application's functionality (B), confirming the user stories are implemented correctly.

D. Assign IT team members user stories to work on.

This is incorrect. In Agile methodologies like Scrum, the development team is self-organizing and pulls work from the prioritized backlog during sprint planning; work is not assigned by an individual.

E. Execute the assigned work on schedule.

This is incorrect. The responsibility for building and implementing the application features (executing the work) lies with the development team, such as System Architects, not the Business Architect.

---

1. Pega Academy

Pega Business Architect (PEGACPBA24V1) Mission

"The Pega Business Architect role" module

"Key responsibilities of a Business Architect" lesson.

This lesson explicitly states that a Pega Business Architect is responsible for "building a backlog of user stories" which aligns with (A) Manage the project team's backlog. It also states the BA must "work with stakeholders to define business objectives" and "define business requirements

" which supports (C) Plan current and future application needs.

2. Pega Academy

Pega Business Architect (PEGACPBA24V1) Mission

"Validating a Pega application" module

"Testing an application" lesson.

This section details the BA's role in quality assurance

stating

"As a Business Architect

you are responsible for application testing and validation. You confirm that the application meets the business requirements by creating test cases and scenarios." This directly supports (B) Develop scenarios to test application functionality.

3. Pega Academy

Pega Business Architect (PEGACPBA24V1) Mission

"Designing a Pega application" module

"Defining the scope of the MLP" lesson.

This lesson describes how the BA works with stakeholders to define business outcomes and the scope of the Minimum Lovable Product (MLP). This activity is a core part of (C) Plan current and future application needs.

The Explore Data landing page in Pega Platform is a powerful tool for business users to interact with and understand the data within their applications. Its primary functions are to view, analyze, and visualize data. Users can create ad-hoc reports by applying filters, sorting columns, and grouping records to organize the data meaningfully. Furthermore, the Explore Data page allows for the creation of various charts and graphs, such as pie charts, to visually represent data patterns and insights, which can then be added to user portals or dashboards.

B. Edit medical facility data for a health insurance application.

The Explore Data page is designed for data analysis and reporting (read-only operations), not for transactional data entry or editing existing records.

C. Create a new Sales data field to reference an Insight Rule.

Creating new data fields (properties) is a data modeling task performed during application development in App Studio or Dev Studio, not a function of the Explore Data page.

1. Pega Academy: Pega Certified Business Architect (24.1) Mission

Module: Reporting in Pega Applications

Lesson: Exploring data.

This lesson explicitly states

"The Explore Data landing page provides a convenient way to view

filter

and group the data for any data type in your application. You can also use the Explore Data landing page to create charts and other visualizations that you can add to your user portal." This directly supports options A and D.

2. Pega Documentation: Exploring data with the Explore Data landing page.

Section: "Exploring data" details the process: "To explore data

you create a report by selecting a data type and adding columns to the report. You can then filter

group

and sort the data in the report to focus on the information that you need." This confirms option A. The document also describes how to "Create a chart" from the explored data

confirming option D. It makes no mention of editing data records or creating new data fields.

The Pega case life cycle design guidelines state that stages should represent a significant change in the status of a case or a transfer of authority. Stage names should be nouns or noun phrases that describe the business context.

Option D, with stages "Submission," "Manager Approval," and "Fulfillment," best models the primary path of the business transaction. "Submission" and "Fulfillment" are appropriate nouns representing key milestones. "Manager Approval" is a descriptive noun phrase that accurately reflects the specific requirement where the case is transferred to a manager for a decision, making it the most precise choice among the options.

A. Option A: The stage "Manager Review" describes an action rather than a state of the case. Additionally, the flow is incorrect as the employee review should occur before fulfillment, not after.

B. Option B: While "Approval" is a valid stage name, "Manager Approval" (Option D) is more specific and descriptive, aligning more closely with the explicit business requirement that a manager performs the approval.

C. Option C: The stage names "Submit Request" and "Approve Request" are verb phrases. Pega best practice is to use nouns or gerunds to name stages, as they represent a milestone or a state in the case life cycle.

1. Pega Academy

Business Architect (Pega Platform 24.1)

"Designing a case life cycle" module: This module specifies the best practice for naming stages. It states

"Name the stage to describe the section of the business process. Use a noun or noun phrase for the name. For example

a stage in which a new insurance claim is processed can be named Triage." This supports using noun phrases like "Manager Approval" for clarity and context.

2. Pega Platform 24.1 Documentation

"Stages in a case life cycle": This document defines a stage as representing "a significant change in the status of a case

a transfer of authority

or a change in the business process." The transfer of the request to the manager for a decision is a clear transfer of authority

justifying a distinct stage. The document reiterates the naming convention: "As a best practice

use a noun or noun phrase to name a stage." Option D adheres to this guideline more specifically than the other options.

The most appropriate scenario to remove a landing page is when it has been replaced by a new one and is officially deprecated. Deprecation is a formal process in application development to mark a feature or component as obsolete and discouraged from use. Removing the deprecated landing page is the final step in the replacement process, ensuring that users and developers do not access outdated functionality, thereby maintaining application quality and consistency.

B. You are developing a landing page for people managers only.

This describes adding a new, role-specific landing page. It does not provide a reason to remove an existing one; other pages would likely remain for other user roles.

C. You are developing a new landing page for all users.

This involves creating a new page, which might coexist with other landing pages. It does not inherently require the removal of an existing page unless it is a direct replacement.

D. You are developing a landing page not in the main menu by default.

This is a configuration choice for a new page's visibility. A landing page can be functional and necessary without being in the main navigation menu.

1. Pega Platform Documentation - Rule-Obj-Class form — Completing the History tab:

Section: Usage field

Content: The documentation explains the "Deprecated/Obsolete" status. "Select Deprecated/Obsolete to indicate that this rule is deprecated and that its use is discouraged. You can also provide a message to developers to explain the reason for the deprecation and to identify a replacement rule." This official process directly supports the scenario of replacing and subsequently removing a deprecated component like a landing page.

2. Pega Academy - Low-Code App Builder (24.1) Module: Designing user views:

Topic: Creating views for case types

Content: This module covers the creation and modification of user interface elements. The underlying principle is iterative development

where older or less efficient views are replaced with improved versions. Removing a deprecated page is a logical step in this iterative lifecycle to prevent the use of outdated designs.

A Persona in Pega represents a specific type of user, defined by their role, goals, and how they interact with the application. The creation of a new Persona is necessary when a new, unique combination of user access (Channel interface), responsibilities (work routing), and capabilities (permissions) is identified. This combination defines a distinct user role that is not covered by existing Personas. For example, a "Manager" Persona would have a different portal, receive different work (approvals), and have different permissions than a "Customer Service Representative" Persona.

A. The existing Channel interfaces are too limited for the completion of work to occur.

This describes a need to create or modify a Channel (a user portal), which could be assigned to an existing Persona. It does not inherently require a new Persona.

B. An additional user needs to interact with an application.

This is an operational task of creating a new user account (Operator ID) and assigning them to an existing Persona. It does not necessitate creating a new user role.

C. A new Case Type is created in an application.

A new Case Type represents a new type of work. Access to this new work can be granted to existing Personas; it does not automatically require the creation of a new one.

1. Pega Platform™ Documentation

"Personas": "A persona is a composite user model that represents a whole group of users with a similar role

behavior

and goals... You can configure a persona by associating it with a specific channel and access group." This directly links the Persona to the combination of channel and permissions (via access group).

Reference Location: Pega Platform > App Studio > User interface > Portals > Personas

2. Pega Academy

"Pega Express Delivery" Course

"Personas and Channels" Module: This module teaches that a Persona is a key artifact in the Pega Express methodology used to define a user role. It emphasizes that each Persona has specific needs which translate into the portal (Channel) they use and the work they perform

which is governed by permissions and routing. Creating a new Persona is required when a new set of these combined attributes is needed.

Reference Location: Pega Academy > Pega Express Delivery > Discover > Personas and Channels

3. Pega Platform™ Documentation

"Access groups": "An access group is a collection of settings that define the permissions and privileges of a user or a group of users... By associating an access group with a persona

you can control the actions that the persona can perform in your application." This confirms that permissions are a core component of the Persona definition.

Reference Location: Pega Platform > Security > Access control > Access groups

In Pega Platform's case life cycle management, when a case status is configured on a specific step, the system updates the status of the case at the beginning of that step. The question specifies that the "Process ticket" step is configured to set the status to "Pending-Verification". Therefore, the case status is updated to "Pending-Verification" as soon as the "Process ticket" step is initiated. This status reflects the work currently in progress for that step and persists until another configuration changes it.

A. When Verify solution step starts: This is incorrect. The "Verify solution" step occurs after the "Process ticket" step, so the status would have already been set.

C. When the Process ticket step completes: This is incorrect. The case status is updated at the beginning of a step to reflect the current state, not after the work is finished.

D. When the Triage stage completes: This is incorrect. While the completion of the "Triage" stage triggers the next stage, the status change is directly tied to the initiation of the specific step where it is configured.

1. Pega Academy

Pega Platform Foundation Mission

"Case Life Cycle and Status" Module: This module explains that the pySetFieldDefaults data transform

which is invoked when a step begins

is often used to set properties like the case status. The standard behavior is to apply the status configured on a step

process

or stage upon entry.

2. Pega Documentation

"Setting a case status": "You can set the status of a case at the beginning of a step

a process

or a stage. When the case advances to that step

process

or stage

the system automatically updates the case status." This directly confirms that the status is set when the step starts. (Reference: Pega Platform™ Documentation

Case management > Designing a case life cycle > Configuring a case life cycle > Setting a case status).

3. Pega Documentation

"Case life cycle for a top-level case": The documentation illustrates the flow of a case

where status changes are associated with the entry into stages and processes (which contain steps). The status reflects the current phase of work. (Reference: Pega Platform™ Documentation

Case management > Case processing > Case life cycle for a top-level case).

The user story requires a "cancel" option to be available "at any time" while the service request (case) is open. A case-wide action (also known as an optional action) is specifically designed for this purpose. It is configured at the case type level and is accessible to users throughout the case life cycle, regardless of the current stage or assignment. This allows a user to initiate the cancellation process whenever needed, directly fulfilling the requirement.

B. Configure the Cancel button on the user views to resolve the case: This is inefficient and not scalable, as it would require manually adding and configuring a button on every single user view within the case type.

C. Add an alternate stage to the case life cycle: An alternate stage defines the process for an exception or deviation (like cancellation), but it does not provide the user interface control to initiate that process from anywhere in the case.

D. Add a stage-only action to each stage in the case workflow: This would require duplicating the same action for every stage, which is redundant and difficult to maintain. A case-wide action is the correct, centralized approach.

---

1. Pega Academy

Pega Platform Foundation Mission

Configuring optional actions module.

Reference: In the "Optional actions" topic

it states

"Optional actions supplement the tasks that users can perform as they work on a case. Unlike standard processes

optional actions are available to users at any time

as long as the case is open." This directly supports the use of a case-wide action for a requirement that specifies availability "at any time."

2. Pega Platform Documentation

Case processing

Section: Optional actions.

Reference: The documentation distinguishes between case-wide and stage-only optional actions. It clarifies that a case-wide action "is available in all stages of the case life cycle

" whereas a stage-only action "is available only in the specific stage that you select." This confirms that option D is incorrect for an "at any time" requirement and that option A is the correct design.

3. Pega Platform Documentation

Case life cycles

Section: Alternate stages.

Reference: The documentation describes alternate stages as a way to "model out-of-sequence events in the life cycle of a case... For example

you can use an alternate stage to process a cancellation request for an online order." While the cancellation process might reside in an alternate stage

the initiation of that process from anywhere in the case is best handled by a case-wide action

making option C an incomplete solution.

In Pega Platform case design:

• Collect Information steps create an assignment for a user to input data into a form, matching the action where a user enters reservation details.
• Approval steps are specific assignments routed to a supervisor (manager) to explicitly accept or reject a case, matching the timesheet review scenario.
• Decision steps are automated processes where the system evaluates logic or conditions (such as checking a request type) to determine which path the workflow should take next.
• Automation steps perform system-side actions without human intervention, such as sending correspondence (emails) or updating databases.

Pega Documentation: Configuring the Case Lifecycles. "Collect information... Assigns a task... to a user... to collect users' personal details." / "Approve/Reject... Assigns a task to a user, typically a manager... to approve or reject the Case." / "Decision... Evaluates an Expression... to determine which Step is next." / "Automation... Provides preconfigured functionality, such as sending an email..." (Source 1.4)

Pega Academy: Designing a Case Life Cycle. "Collect information Steps are Steps that require user action or input." / "Automation Steps are steps performed by the system... send emails..." (Source 1.1, 1.2)

Pega Academy: Work approval. "Case approvals are decision points at which one or more users decide whether to approve or reject a case." (Source 2.1)

This solution maps Pega Platform automation shapes to their specific business requirements:

1. Send email: Used to generate and send automated correspondence (confirmations) to interested parties.
2. Change to a stage: When a case is rejected, the workflow must often revert to a previous phase (e.g., a "Correction" stage) to allow the employee to modify data. This shape transitions the case flow to a specific stage.
3. Push notification: Specifically designed to send alerts to mobile devices, matching the requirement for a "mobile notification."
4. Create PDF: This automation converts a section or view of the case data into a portable document format (PDF) and automatically attaches it to the case file, satisfying the requirement to attach a finalized report.

Pegasystems Inc., "Sending emails," Pega Academy, [Online]. Available: https://academy.pega.com/topic/sending-emails/v1. (Accessed for verification of correspondence automation).

Pegasystems Inc., "Controlling the flow of a case," Pega Academy, [Online]. Available: https://academy.pega.com/topic/controlling-flow-case/v1. (Describes the "Change to a stage" automation for alternate paths like rejection).

Pegasystems Inc., "Sending push notifications," Pega Academy, [Online]. Available: https://academy.pega.com/topic/sending-push-notifications/v1. (Confirming mobile-specific alerting).

Pegasystems Inc., "Creating PDF files," Pega Academy, [Online]. Available: https://academy.pega.com/topic/creating-pdf-files/v1. (Verifies the functionality of generating and attaching case reports).

In Pega, Action Sets configured on a control execute sequentially from top to bottom. The sequence is initiated by the trigger event, a user clicks the button.

The first configured action in the list is "Refresh-This section". Inside this action, a Data Transform (SetDefaultValues) is defined. When a section refresh includes a data transform, the system executes the data transform on the server to update the clipboard data before regenerating the HTML. Consequently, the system applies a data transform first, and then the system refreshes the section in the browser with the updated data.

The second action, "Set Value," is listed below the refresh action. It runs after the refresh completes. This action contains a specific condition (PaymentConfirmed), so the order ID value is set only if that condition is met.

Pega Platform Documentation, "Defining action sets": Confirms that actions in an action set execute in the order in which they are listed in the configuration (top to bottom).

Pega Platform Documentation, "Refresh This Section action": Details that data transforms configured within a refresh action are used to update the context (clipboard) before the section is re-rendered.

Pega Academy, "Configuring action sets": Describes the behavior of events (Click) triggering a chain of actions (Refresh, Set Value) and the execution flow between client and server.

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.

In Pega's case management framework, a parent case's life cycle is dependent on the completion of its child cases. By default, a parent case cannot be resolved until all of its child cases have been resolved. This ensures that all required sub-processes, such as payment and packaging for a purchase order, are fully completed before the overall transaction is closed. The parent case typically includes a "Wait" step that pauses its processing until it receives a signal that all its child cases have reached a resolved status.

A. Pac-56 must resolve before Pay-37 can resolve.

This is incorrect because child cases are siblings and operate independently unless an explicit dependency is configured between them.

B. PO-11 must resolve before Pay-37 and Pac-56 resolve.

This is incorrect as it inverts the dependency model. A parent case's resolution depends on the completion of its child cases, not the other way around.

C. PO-11 can resolve when either Pay-37 or Pac-56 resolves.

This describes an "Any" dependency, which is not the default behavior. For a purchase order, both payment and packaging are logically required for completion.

1. PegaSystems Official Documentation: In the topic "Dependencies between cases

" the documentation states

"By default

a parent case is not resolved until all of its child cases are resolved." This directly confirms the principle that all child cases must be completed.

Source: Pega Platform 24.1 Documentation

"Case management > Dependencies between cases > Configuring a parent case to wait for child cases to resolve."

2. Pega Academy Courseware: The "Business Architect" mission explains the concept of case dependencies. In the "Case Design" module

it is detailed that when you add a "Create Case" step

the parent case automatically waits for the child case to be resolved before it can continue. If multiple child cases are created

the parent waits for all of them by default.

Source: Pega Academy

"Business Architect (24.1)" Mission

"Case Design" Module

"Creating a child case" Lesson.

An Approve/Reject step is a specific configuration in Pega used to model a business decision where a user must formally approve or reject a case.

Scenario B is a classic example: a manager reviews a self-evaluation and either approves it, allowing the case to proceed, or rejects it, sending it back to the employee for rework. This directly maps to the approve/reject outcomes.

Scenario A also represents a formal approval process. An expense report must be approved. The logic described (routing based on amount) determines which manager performs the Approve/Reject step, but the step itself is central to the process. Both managers will ultimately perform an approve or reject action.

C. This scenario describes a standard business process with work distribution. It involves routing tasks to different teams for fulfillment, not a formal approval or rejection decision point.

D. This describes conditional routing based on data (severity). The primary action is classifying and assigning the case to the appropriate work group, not approving or rejecting the support request itself.

1. Pega Academy

Business Architect (24.1) Mission

Module: Case life cycle design

Lesson: Approval steps. This lesson states

"An approval is a decision that a user makes on a case... For example

a manager must approve or reject a purchase request that exceeds a certain amount." This directly supports scenario A. It also explains that a rejection can return the case to the originator for correction

which supports scenario B.

2. Pega Platform Documentation

"Adding an Approve/Reject step to a case." The documentation specifies

"Add an Approve/Reject step to a case type to define a point in a business process in which a user must decide whether to approve or reject a case." It further clarifies that approval advances the case

while rejection can trigger actions like sending a notification or routing the case for rework. This aligns with the decision-making nature of scenarios A and B

as opposed to the work distribution logic in C and D.

3. Pega Platform Documentation

"Routing assignments." This document describes how routing directs assignments to the appropriate user or work queue based on business logic. Scenarios C and D are examples of routing logic (routing by department or severity) rather than the binary approval decision handled by an Approve/Reject step.

Pega best practices for naming steps in a case life cycle mandate a "verb + noun" format. This convention ensures that the step name clearly and concisely describes the action being performed, making the process easy for business users to understand.

- "Notify Candidate" (verb: Notify, noun: Candidate) accurately describes the action of sending an email invitation.

- "Schedule Interview" (verb: Schedule, noun: Interview) perfectly represents the task of selecting the date and location.

Both options adhere to the "verb + noun" guideline and clearly describe specific actions from the scenario.

B. Ask Questions: While this follows the "verb + noun" format, it is a less precise description of the manager's task ("captures notes from the discussion") compared to how well "Schedule Interview" describes its corresponding action.

C. Technical Exercise: This option is a noun phrase and lacks a verb. It describes an object, not an action, which violates the fundamental "verb + noun" naming convention for Pega steps.

1. Pega Academy

Pega Platform for the Business Architect (24.1)

Module: Designing a case type

Lesson: Adding steps to a case type.

This lesson explicitly states: "When you name a step

use a 'verb + noun' naming convention. For example

'Approve request' or 'Select interview location'. Use a name that is meaningful and relevant to business users." This directly supports "Schedule Interview" and the general principle.

2. Pega Documentation

Case management

Designing a case life cycle

Section: Adding a step to a process.

The documentation advises: "In the 'Step name' field

enter a short

action-oriented name for the step. As a best practice

start the step name with a verb

for example

'Approve loan request'." This reinforces the "verb + noun" rule

making "Technical Exercise" incorrect and "Notify Candidate" and "Schedule Interview" correct.

The requirement is to make a promotion available only when a specific condition is met. In Pega, the visibility of a UI element is controlled by the "Visibility" attribute. By setting this attribute to a "When" condition, the element (the promotion) will only be displayed on the screen when the condition (cart total >= 100) evaluates to true. This directly implements the business rule described in the scenario.

B. Required: True

This attribute makes a field mandatory for user input; it does not control whether the field is visible on the form.

C. Default Value: USD100

This attribute pre-populates a field with a specific value. It does not control the visibility of the field based on a condition.

D. Read-only: True

This attribute prevents a user from editing a field's value. It controls the field's editability, not its visibility.

---

1. Pega Academy Documentation: Configuring element visibility. In the "Visibility" section of a control's properties

you can select "Condition (when rule)" or "Condition (expression)" to define the logic that determines whether the control is visible at run time. This directly supports using a "When" condition for visibility.

Reference: Pega Platform 8.8 Documentation > User experience > UI elements > Configuring element visibility.

2. Pega Academy Documentation: When condition rules. This documentation explains that "When" rules are used to define conditional logic that can be reused in various parts of an application

including controlling the visibility of UI elements. The scenario cart total >= 100 is a perfect example of a condition that would be defined in a When rule.

Reference: Pega Platform 8.8 Documentation > Decision management > About When condition rules.

3. Pega Academy Module: User Interface Configuration. This module details the configuration options for UI elements. In the lesson on "Configuring Control Properties

" it explicitly covers the "Presentation" tab

where the "Visibility" setting is located and demonstrates its use with conditional logic.

Reference: Pega Academy > Pega Platform for Pega Business Architects > Low-Code App Builder > User Interface Configuration > Configuring Control Properties section.

Pega's Center-out™ business architecture is founded on three core principles. First, it centralizes business logic and artificial intelligence into a "brain" that is consumed by all channels, ensuring consistency (Manage intelligence centrally). Second, it focuses on achieving specific business outcomes by designing around customer Microjourneys™ (Focus on outcomes, align your process). Third, it leverages the Situational Layer Cake™ to manage business variations (e.g., by region, product, or channel) in a layered, reusable model, which enables enterprise-wide scalability (Manage variations to be scale-ready).

B. Complicate data access, keep logic complex.

This is an anti-pattern. The Center-out approach aims to simplify and abstract data access and business logic, not complicate it.

E. Drive business logic with Channels.

This describes the channel-siloed "outside-in" approach, where each channel has its own logic, leading to inconsistency. Center-out is designed to prevent this.

1. Pega Academy

Pega Business Architect (24.1) Mission: In the "Pega's Center-out business architecture" module

the three core principles are explicitly stated as:

Principle 1: Focus on customer outcomes with Microjourneys. (Supports option C)

Principle 2: Use a central brain to manage all logic and decisioning. (Supports option A)

Principle 3: Manage variations for scale. (Supports option D)

2. Pega Documentation

"Center-out business architecture": This document outlines the approach

stating

"The Center-out approach avoids the pitfalls of both top-down and bottom-up by starting in the center

where the customer and the business logic intersect... The Center-out business architecture has three layers: Customer-facing channels

The Pega brain

and Enterprise systems of record." This architecture directly supports centralizing intelligence (the brain) away from the channels (refuting option E).

3. Pega Documentation

"Situational Layer Cake": This documentation explains how Pega manages variations for scale. "The Situational Layer Cake is a powerful feature of the Pega Platform™ that allows you to create a highly reusable and scalable application architecture... It helps you organize your application to reflect your business structure

promoting reuse and managing variations effectively." This directly supports option D.