Pegasystems Certified Pega Business Architect '25 (PEGACPBA25V1)

✅ Option C (Correct)Reasoning: Tool Rules in Pega GenAI are essential for establishing guardrails. They define permissible actions and responses for generative AI agents, ensuring adherence to organizational policies and ethical guidelines. This directly supports governance by controlling agent behavior and providing transparency into their operational boundaries.

❌ Why the other choices are incorrect:

• Option A is incorrect: Generative AI systems require ongoing human oversight to ensure accuracy, fairness, and compliance, not remove it.
• Option B is incorrect: Restricting user interaction based on roles is typically managed by Pega's standard access control (roles, privileges), not primarily by Tool Rules governing agent behavior.
• Option D is incorrect: Agents in Pega GenAI are designed to operate within and comply with business policies and rules, not independently of them, to ensure responsible and effective automation.

✅ Option D (Correct)The Pega GenAI Connect Step is designed to integrate large language models (LLMs) into Pega workflows. Its primary purpose is to automate cognitive tasks such as summarizing case details, generating content, extracting information, or classifying data, thereby streamlining processes and improving efficiency within the application.

❌ Why the other choices are incorrect:

• Option A is incorrect: The GenAI Connect Step facilitates interaction with pre-trained LLMs; it is not used for training large language models on application data.
• Option B is incorrect: While AI might influence design, the GenAI Connect Step's direct function is to apply AI for operational tasks within a case, not to create new Case Types.
• Option C is incorrect: Pega GenAI aims to augment and assist human decision-making by automating specific tasks, not to entirely replace human judgment in critical approval processes.

✅ Option B (Correct)
Reasoning: Pega GenAI Knowledge Buddy is designed to act as an intelligent assistant, enabling users to efficiently find, retrieve, and synthesize information from various enterprise knowledge sources using generative AI. Its primary goal is to enhance knowledge management and information accessibility.
❌ Why the other choices are incorrect:

• Option A is incorrect: While GenAI can assist development, Knowledge Buddy's focus is on knowledge retrieval, not directly generating code snippets. Pega offers other tools for developer assistance.
• Option C is incorrect: Knowledge Buddy uses connections to large language models for its purpose, but its primary purpose is the application of these models to knowledge management, not merely establishing the connection itself.
• Option D is incorrect: Pega has dedicated tools like PegaUNIT and Pega Scenario Testing for creating automated test cases. Knowledge Buddy is not primarily designed for testing automation.

Pega GenAI Autopilot aims to accelerate application development by assisting with various tasks. Two key data management features it provides are:

• Suggesting choices for picklist fields: GenAI can analyze context and suggest relevant values for picklists, streamlining the data model definition process.
• Generating sample records for a Data Object: To facilitate testing, GenAI can create realistic sample data based on the data object's structure, reducing manual effort.

Option A is incorrect as Pega GenAI focuses on creation and suggestion, not permanent deletion of data objects. Option C is incorrect; migrating entire data models from legacy systems is typically a complex ETL task beyond GenAI Autopilot's current scope.

Pega Blueprint is a design tool that significantly accelerates development by guiding business architects to define core application structures. It generates tailored suggestions for Case Types, Stages, and Steps, forming the foundational design of the application. This structured approach ensures a comprehensive and efficient initial setup, reducing discovery time and streamlining the transition to development within Pega Platform.❌ Why the other choices are incorrect:Option A is incorrect: Pega Blueprint facilitates design collaboration and documentation, but its primary function is not to eliminate meetings or simply summarize notes. It structures requirements for development.Option C is incorrect: Pega Blueprint is a design and discovery tool that works in conjunction with Pega Platform, not a replacement for the development environment itself.Option D is incorrect: Pega Blueprint generates a detailed application blueprint and potentially initial application components. It does not automatically code the entire application without human intervention; development in Pega Platform is still required.

✅ Option A (Correct)

Reasoning: Increasing the urgency of a work item is a fundamental SLA escalation action in Pega, making the task a higher priority and more visible to users and managers.

✅ Option C (Correct)

Reasoning: Sending notifications, such as emails to managers or other stakeholders, is a common SLA escalation to inform them when service levels are breached, prompting intervention.

❌ Why the other choices are incorrect:

• Option B is incorrect: Automatically resolving a case without human intervention is not a standard, direct SLA escalation action. Escalations typically aim to expedite completion or draw attention, not close a case prematurely.
• Option D is incorrect: Extending the deadline automatically after it has been missed defeats the purpose of an SLA deadline. Escalation actions focus on addressing the missed deadline, not simply moving it.

✅ Option B (Correct)
Reasoning: Configure a Wait shape after the Client Intake Stage, setting its timer to 72 hours. This precisely pauses case processing for the specified duration. A Case-wide optional action enables clients to upload recordings at their convenience during this waiting period, fulfilling the requirement for optional uploads within the time limit.

❌ Why the other choices are incorrect:

• Option A is incorrect: A validate rule checks data validity; it does not pause case processing or implement a timed wait.
• Option C is incorrect: A Service Level Agreement (SLA) primarily manages task urgency and escalations; it doesn't pause the flow until a deadline for the entire stage.
• Option D is incorrect: A child Case for optional uploads is overly complex. A Wait shape dependent on child case resolution doesn't inherently support a 72-hour time limit without further configuration, nor does it easily handle an optional scenario where the client may not upload.

✅ Option A (Correct)
Reasoning: In Pega, the Work- class is specifically designed to define Case Types. Each customer request, handled as a separate Case, maps directly to an instance of a Case Type built upon the Work- class, enabling the configuration of workflows and assignments.
❌ Why the other choices are incorrect:

• Option B is incorrect: Rule- classes store rules like activities, data transforms, and UI components. They do not define Case Types or manage work instances directly.
• Option C is incorrect: While Work- is a type of base class, 'Base class' itself is too general. The specific class type for defining Cases and workflows is the Work- class.
• Option D is incorrect: Data- classes are used to store application data objects, such as customer profiles or product details. They are not used to define transactional Case Types or manage their workflows.

✅ Option C: Alternate Stage (Correct)

Reasoning: Alternate Stages in Pega's Case Life Cycle are specifically designed to manage exceptions, deviations, or non-standard process flows that diverge from the primary path. Order cancellations or returns are typical examples of such exceptions that are handled within dedicated alternate stages.

❌ Why the other choices are incorrect:

• Option A is incorrect: The Create Stage is the initial phase where a case is instantiated and fundamental data is captured. It does not manage subsequent exceptions like cancellations.
• Option B is incorrect: Primary Stages represent the main, expected business process flow of a case. Exceptions are by definition deviations from this primary, happy path.
• Option D is incorrect: The Resolution Stage is the final phase of a case, where it is formally concluded and closed after all tasks, including any exception handling, have been completed.

✅ Option B (Correct)Reasoning: In Pega, you can configure a step or process to execute conditionally. By setting a 'Start when' condition on the 'Enter payment information' process (or the step invoking it) to only run if the customer is neither a student nor a senior, the payment step is automatically skipped for eligible users. ❌ Why the other choices are incorrect:

• Option A is incorrect: Adding a manual approval step is inefficient and unnecessary for this automatic conditional logic.
• Option C is incorrect: This option only considers students and incorrectly ends the process for others instead of leading to payment.
• Option D is incorrect: The ticket confirmation stage should always occur; it is the payment entry that needs to be conditional, not the confirmation.