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.