First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1Pega Express Methodology
In the Pega Express delivery methodology, which activity produces a working, demonstrable application in the shortest possible time and is used to validate understanding with business stakeholders?
- The microjourney design workshop
- The enterprise data model review
- The Build-a-Little-Build-a-Lot cycle Correct answer.
- The project kickoff presentation
Explanation
Pega Express centers on Build-a-Little-Build-a-Lot, an iterative cycle where a small slice of the application is built, demonstrated, and refined with stakeholders. This short feedback loop lets the team validate assumptions early instead of committing to a large design before any working software exists.
Question 2Pega Express Methodology
A team is starting a new Pega application and wants to agree on the primary outcome the business wants to deliver to its customers. Which Pega Express artifact should they create first?
- A data page catalog
- A deployment pipeline
- A microjourney Correct answer.
- A case type hierarchy
Explanation
Pega Express begins with the microjourney, a description of the end-to-end experience that delivers a specific outcome to a persona. Stages and steps are derived from it, so it precedes detailed case type and data design. The other artifacts are downstream implementation concerns.
Question 3Pega Express Methodology
During a design session, stakeholders describe how a customer applies for a product, gets assessed, and receives a decision. In Pega Express terminology, what is this end-to-end description called?
- A microjourney Correct answer.
- A data object
- A persona
- A service level agreement
Explanation
A microjourney captures the sequence of stages and steps a persona goes through to reach a single outcome. It is expressed in business language and becomes the backbone of the case type design. Personas, data objects, and SLAs are separate design elements used within it.
Question 4Pega Express Methodology
Which Pega Express role is primarily accountable for prioritizing the backlog and ensuring the delivered increments provide the highest business value?
- The System Architect
- The Product Owner Correct answer.
- The Business Architect
- The Delivery Consultant
Explanation
The Product Owner represents the business and owns prioritization of the work, deciding what the team builds next to maximize value. Architects and consultants contribute design and technical guidance but do not own business priority. This separation keeps the backlog aligned to business outcomes.
Question 5Pega Express Methodology
A Pega Express team has finished a design session and identified a first increment. What is the recommended next action according to the methodology?
- Freeze the scope for the entire release
- Complete all integrations before any case logic is built
- Build a small working slice and demonstrate it to stakeholders Correct answer.
- Document every requirement in a complete specification before coding
Explanation
Pega Express favors building a small, working slice early and demonstrating it so stakeholders can react and refine requirements. This reduces the risk of building the wrong thing at scale. Comprehensive upfront specification and scope freezing contradict the iterative approach.
Question 6Pega Express Methodology
When drafting a microjourney, a team lists stages such as Submit, Review, and Fulfill. What do these stages represent in Pega Express terms?
- The major phases the case passes through toward its outcome Correct answer.
- The access groups required to work the case
- The data pages loaded at case creation
- The processing modes assigned to each assignment
Explanation
Stages are the major phases of a case that group related steps and represent progress toward the outcome. Each stage contains steps that define the work performed. Processing modes, data pages, and access groups are implementation-level concerns configured within those stages.
Question 7Pega Express Methodology
A stakeholder asks why the team is holding a short design session rather than producing a full requirements document. Which principle of Pega Express best explains this choice?
- Technical architecture must be finalized before any business discussion
- Documentation is prohibited in agile delivery
- Collaborative design with stakeholders replaces lengthy written specifications Correct answer.
- Design decisions should be deferred until every integration is confirmed
Explanation
Pega Express uses collaborative, facilitated design sessions so business and technical participants reach shared understanding quickly and directly. This replaces heavy written specifications that are slow to produce and often misread. Documentation still exists where useful; the point is emphasis on collaboration over exhaustive documents.
Question 8Pega Express Methodology
In a Pega Express project, which artifact captures the specific people or groups for whom the microjourney is designed and whose needs drive prioritization?
- The class hierarchy
- The persona Correct answer.
- The decision table
- The case life cycle
Explanation
A persona describes a group of users or customers with shared needs and goals, and it anchors the microjourney to a real audience. Prioritization is judged by the value delivered to that persona. Case life cycles, class hierarchies, and decision tables are design and implementation artifacts.
Question 9Pega Express Methodology
A team delivers a working increment and demonstrates it to stakeholders, who request a change to the approval path. What is the most Pega Express-aligned response?
- Reject the change because the design was already approved
- Restart the entire design phase from the beginning
- Incorporate the change into the next small iteration and re-demonstrate Correct answer.
- Log the change and schedule it for the next major release
Explanation
The Build-a-Little-Build-a-Lot cycle expects feedback from demonstrations to feed directly into the next small increment. Absorbing the change quickly keeps the application aligned with business needs and avoids accumulating a large change backlog. Deferring to a major release or rejecting feedback defeats the purpose of early demonstration.
Question 10Pega Express Methodology
Which statement best describes the relationship between a microjourney and a case type in Pega Express?
- A case type is designed first and the microjourney is documented afterward
- A microjourney and a case type are unrelated artifacts
- A case type replaces the need for a microjourney
- A microjourney is a business-level description that the case type implements Correct answer.
Explanation
The microjourney is expressed in business terms and describes stages and steps from the persona's perspective. The case type is the application construct that implements those stages and steps. Design therefore flows from the business description into the implementation.
Question 11Pega Express Methodology
A project team is deciding how much of the application to design before starting to build. Which approach aligns with Pega Express guidance?
- Design just enough for the next increment, then build and learn Correct answer.
- Design only the user interface and defer all process logic
- Design the entire application in detail, then build it in one phase
- Skip design entirely and build directly from stakeholder conversations
Explanation
Pega Express recommends designing just enough to start building the next valuable increment, then learning from the result. This keeps design effort proportional to what can be validated soon. Full upfront design or skipping design both create avoidable risk.
Question 12Pega Express Methodology
Which outcome indicates that a Pega Express design session has been successful?
- The full data model has been normalized and approved
- Every technical rule to be built has been specified in detail
- Participants agree on the journey, stages, and steps for the next increment Correct answer.
- All future change requests have been pre-approved
Explanation
A successful design session produces shared understanding of the microjourney, its stages and steps, and a clear next increment to build. It is not intended to specify every rule or finalize the data model. Agreement on scope for the next build is the practical measure of success.
Question 13Pega Express Methodology
A team is mapping a microjourney and identifies a step where the customer uploads supporting documents. Which Pega Express concept should the team use to describe the work performed at that point?
- A data page
- A stage
- A persona
- A step Correct answer.
Explanation
Steps are the individual units of work within a stage, such as uploading documents or submitting a form. Stages group related steps into broader phases. Personas describe the audience and data pages support data retrieval, so neither describes the work unit itself.
Question 14Pega Express Methodology
Why does Pega Express emphasize demonstrating working software to business stakeholders rather than presenting design documents for sign-off?
- Stakeholders are unable to read design documents
- Demonstrations are cheaper to produce than any document
- Documents cannot capture business terminology
- Working software reveals real behavior that documents can obscure Correct answer.
Explanation
A demonstration shows how the application actually behaves, exposing misunderstandings that a document may hide behind ambiguous wording. Stakeholders can react to concrete behavior and give more precise feedback. Cost, literacy, and terminology are not the underlying rationale.
Question 15Pega Express Methodology
During a Pega Express engagement, the team must decide which of several candidate microjourneys to build first. Which criterion best aligns with the methodology?
- The journey with the most complex integrations
- The journey the developers find most technically interesting
- The journey with the fewest stakeholders involved
- The journey that delivers the highest business value soonest Correct answer.
Explanation
Pega Express prioritizes work by business value so the organization realizes benefit early and validates direction with real feedback. Technical complexity or developer interest are not valid prioritization drivers. Stakeholder count alone does not reflect value delivered.
Question 16Pega Express Methodology
A Pega Express team is preparing for its first build increment. Which set of activities best reflects the intended sequence?
- Gather all requirements, build the full case type, then demonstrate once
- Configure security, then design the journey, then build integrations
- Design the journey, build a thin slice, demonstrate, gather feedback Correct answer.
- Build all reports, then design the journey, then test
Explanation
The methodology cycles through designing the journey, building a thin but working slice, demonstrating it, and incorporating feedback. This sequence front-loads learning and keeps effort focused on validated value. The other sequences either delay demonstration or place supporting concerns ahead of the journey.
Question 17Pega Express Methodology
Which statement accurately reflects how Pega Express treats documentation of the application design?
- Documentation is eliminated entirely in favor of verbal communication
- Documentation is generated exclusively after go-live
- Documentation is produced only when it adds value to the team and stakeholders Correct answer.
- Documentation must be exhaustive before any build begins
Explanation
Pega Express favors lightweight, purposeful documentation that supports collaboration and delivery rather than exhaustive artifacts. The application itself, built iteratively, often serves as the most reliable expression of design. Documentation is neither banned nor required to be exhaustive upfront.
Question 18Pega Express Methodology
A Pega Express team identifies that a microjourney's value depends on a decision the business cannot yet describe precisely. What is the most appropriate action?
- Remove the decision from the journey permanently
- Delay the entire project until the decision logic is fully specified
- Build the surrounding journey with a placeholder decision and refine it in later iterations Correct answer.
- Escalate to force the business to commit to a rule immediately
Explanation
Pega Express accommodates uncertainty by building the parts of the journey that are understood and refining the unclear decision as understanding grows. This keeps progress moving while avoiding premature commitment to logic that may change. Blocking the whole project or forcing an immediate rule creates unnecessary risk.
Question 19Pega Express Methodology
In Pega Express, why are personas and microjourneys typically defined together during design rather than separately?
- Because microjourneys are only used for internal staff
- Because personas determine the application's class structure
- Because the journey's stages and steps only make sense relative to the persona experiencing them Correct answer.
- Because personas cannot exist without a case type
Explanation
A microjourney describes how a specific persona reaches an outcome, so its stages and steps are meaningful only in relation to that persona's goals. Defining them together keeps the design anchored to real user needs. Personas do not dictate class structure, and journeys are not limited to internal staff.
Question 20Pega Express Methodology
A team has completed several iterations and stakeholders keep requesting additions that expand scope beyond the original outcome. Which Pega Express-aligned action best keeps delivery focused?
- Accept every request to preserve stakeholder goodwill
- Stop demonstrating to avoid surfacing new requests
- Freeze the backlog and refuse all further changes
- Re-anchor each request to the agreed microjourney outcome and prioritize accordingly Correct answer.
Explanation
Pega Express keeps work tied to the defined outcome, so new requests are evaluated against whether they advance that microjourney. This allows valuable additions while preventing uncontrolled scope growth. Accepting everything or refusing everything both abandon the discipline of value-based prioritization.
Question 21Pega Express Methodology
Which pairing of Pega Express concept to its definition is correct?
- Step: a major phase of the case toward the outcome
- Stage: a single unit of work assigned to a user
- Persona: the data structure supporting the case
- Microjourney: the end-to-end path a persona takes to an outcome Correct answer.
Explanation
A microjourney is the end-to-end path a persona follows to achieve a specific outcome. Stages are the major phases within it, and steps are the individual units of work inside those stages. A persona is the audience, not a data structure.
Question 22Pega Express Methodology
A program is scaling Pega Express across multiple teams working on related microjourneys. Which practice best preserves the methodology's benefits at scale?
- Have each team build independently with no shared design conventions
- Abandon iterative demonstrations to save time across teams
- Coordinate on shared personas, outcomes, and reusable components across teams Correct answer.
- Merge all teams into a single unit to avoid coordination
Explanation
Scaling preserves Pega Express benefits when teams align on shared personas, outcomes, and reusable assets so increments compose into a coherent application. Independent silos create duplication and inconsistent experiences. Merging teams or dropping demonstrations sacrifices the feedback and reuse advantages.
Question 23Pega Express Methodology
Which statement best explains why Pega Express favors a thin but complete slice of a journey over a fully built single stage?
- A thin slice is easier to estimate than any stage
- A thin slice validates the end-to-end outcome and integration points early Correct answer.
- A complete stage always requires more developers
- Stages cannot be demonstrated until all steps are built
Explanation
Building a thin slice across the whole journey exercises the end-to-end outcome, including handoffs and integration points, so risks surface early. A fully built single stage may look complete but leaves cross-stage assumptions untested. Ease of estimation and staffing are not the core rationale.
Question 24Pega Express Methodology
A newly formed Pega Express team is choosing its first demonstration audience. Which choice best supports the methodology's feedback goals?
- Business stakeholders who can judge whether the outcome is met Correct answer.
- External auditors who verify compliance
- Vendors who supply infrastructure
- Only the development team, to review code quality
Explanation
Demonstrations are aimed at business stakeholders who can confirm whether the increment delivers the intended outcome and provide direction. Code review, compliance audit, and infrastructure supply are separate concerns. Involving the right audience is what makes the feedback actionable.
Question 25Case Management
In Pega case lifecycle design, which stage type is intended to run automatically without waiting for a user action, such as an automated data enrichment step inside a case type?
- A process stage configured with an automation shape Correct answer.
- A primary stage that requires an assignment
- An alternate stage reached only through a manual decision
- An optional stage that pauses until a manager approves
Explanation
A process stage is designed to execute automation without user interaction, so it is the right choice when work must proceed automatically. Primary stages normally contain assignments that wait for an operator, and alternate stages are entered only through explicit branching.
Question 26Case Management
A case type needs to collect customer details, then verify them, then issue a decision. Which Pega construct organizes these sequential phases of the case lifecycle?
- A stage Correct answer.
- A section
- A report definition
- A data page
Explanation
Stages represent the major phases of a case lifecycle and appear in order in the case explorer. Data pages, sections, and report definitions are supporting rules for data, UI, and reporting rather than lifecycle phases.
Question 27Case Management
Which Pega artifact defines the sequence of steps, such as assignments and automations, that a case performs within a single stage?
- A harness
- A case type
- A process Correct answer.
- A flow action
Explanation
A process lists the shapes, including assignments and automations, that execute within a stage. Flow actions and harnesses are UI-related rules, and a case type is the overall definition that contains stages and processes.
Question 28Case Management
A designer wants a case to move to a different stage when a customer withdraws the application. Which Pega mechanism should be used to leave the current stage before its normal completion?
- A validation rule on the assignment
- A declarative expression on the property
- A stage transition configured on the case-wide or stage-level change stage action Correct answer.
- A UI control on the review screen
Explanation
Stage transitions define how a case moves between stages, including early exits triggered by a change stage action. Validation, declarative expressions, and UI controls affect data or display but do not by themselves move a case to another stage.
Question 29Case Management
In a Pega case type, what is the purpose of the Create Stage configuration on a stage?
- It selects the report definition used by the stage
- It determines which process runs when the case enters the stage
- It defines the SLA that applies to the stage
- It controls whether the stage creates a new case or operates on the parent case Correct answer.
Explanation
The Create Stage setting determines whether entering the stage starts a new case, such as a child case, or continues with the current case. Process selection is handled separately, and SLA and reporting settings are unrelated to this configuration.
Question 30Case Management
A child case must be created to handle a background verification while the parent case waits for its result. Which Pega pattern best supports this requirement?
- A validation rule on the child assignment
- A create case shape in the parent process that starts the child case Correct answer.
- A stage transition in the parent case to the child case type
- A data transform on the parent case
Explanation
The create case shape starts a child case from within the parent process and can be configured to wait for the child to resolve. Stage transitions, data transforms, and validation rules do not create child cases.
Question 31Case Management
A case type requires that a manager approve a request before the case can proceed, and the approval must be tracked as a separate assignment in the case lifecycle. Which Pega construct should be added to the process?
- A data page that caches manager details
- A section rule that displays approval text
- An assignment shape routed to a manager work queue Correct answer.
- A report definition filtered by manager
Explanation
An assignment shape creates a task routed to an operator or work queue and records it in the case lifecycle. Data pages, report definitions, and section rules support data and display but do not create tracked assignments.
Question 32Case Management
Which Pega feature directly executes a configured stage transition, rather than returning a decision value for the process to apply?
- A validation rule with a custom message
- A declarative decision tree referenced by a process
- A stage transition with a condition Correct answer.
- A UI control with a visibility condition
Explanation
Stage transitions can be conditioned so that the case moves to a target stage only when the defined criteria are met. A decision tree can select a stage or status value, but the referencing process must apply that result to execute a transition. The question asks for the feature that executes the transition directly.
Question 33Case Management
In Pega, what does the case-wide status represent?
- The stage the case is currently in
- The SLA goal associated with the case
- The assignment currently open for the operator
- A user-defined label describing the current state of the case across stages Correct answer.
Explanation
Case-wide status is a configurable label that describes the case state and is independent of the stage name. Stage and status are separate concepts, and SLA goals and open assignments are different attributes.
Question 34Case Management
A designer wants the case to skip a stage when a customer is already verified. Which configuration achieves this in a Pega case type?
- Remove the stage's SLA configuration
- Mark the stage as optional and add a skip condition on the stage Correct answer.
- Add a validation rule to the stage's assignment
- Change the stage's process to an automation-only shape
Explanation
A stage can be marked optional and given a skip condition so the case bypasses it when the condition is true. Validation, process shape choice, and SLA settings do not control whether a stage is skipped.
Question 35Case Management
Which Pega rule type is used to define the overall structure of a case type, including its stages, processes, and data model?
- A section rule
- A flow rule
- A case type rule Correct answer.
- A data transform rule
Explanation
The case type rule defines the case structure, including stages, processes, and the data model. Flow, section, and data transform rules are supporting rules used within the case type.
Question 36Case Management
A case must be routed to a specific operator who owns the account associated with the customer. Which Pega routing approach best fits this requirement?
- Route using a broadcast to all members of a team
- Route to a work queue with a skill-based routing policy
- Route to the case's creator
- Route to a specific operator determined by a property or data reference Correct answer.
Explanation
Routing to a specific operator allows the assignment to be directed to the person identified by a property or data reference, such as the account owner. Work queues, broadcasts, and creator routing do not target that specific individual.
Question 37Case Management
What is the purpose of a service level agreement (SLA) configured on a stage in a Pega case type?
- To set deadlines and escalation actions for work in the stage Correct answer.
- To control which operators can access the case
- To define the data model for the stage
- To determine which UI section is displayed
Explanation
A stage SLA defines goals and deadlines and can trigger escalation actions when those deadlines are missed. Data model, UI display, and access control are governed by other rules.
Question 38Case Management
A designer needs to capture why an operator rejected a request, and the reason must be available to later stages. Which Pega practice supports this?
- Add a property to the case data model and set it from an assignment form Correct answer.
- Write the reason to a report definition
- Create a new case type for each rejection reason
- Store the reason in a local variable inside the process
Explanation
Case-level properties persist with the case and remain available to later stages and processes. Local variables are transient, report definitions read data rather than capture it, and creating a case type per reason is unnecessary.
Question 39Case Management
Which Pega feature allows a case type to be extended with additional stages or processes for a specific line of business without modifying the base case type?
- A data page with a scope of requestor
- A UI section with a dynamic layout
- A class hierarchy with inheritance and circumstancing Correct answer.
- A report definition with a filter
Explanation
Class inheritance and circumstancing let a specialized case type reuse and extend a base definition for a particular situation. Report filters, data page scope, and dynamic layouts do not extend case lifecycle definitions.
Question 40Case Management
A case type has a primary stage that must always run and an alternate stage used only when a fraud flag is raised. Which statement correctly describes how stages execute in this design?
- The primary stage runs by default, while the alternate stage runs only when the transition condition is satisfied Correct answer.
- Alternate stages always run before primary stages
- Only one stage can exist in a case type
- All stages execute in sequence regardless of conditions
Explanation
Primary stages form the default path, and alternate stages are entered only through defined transitions or conditions. Stages do not all run automatically, and a case type can contain multiple stages.
Question 41Case Management
Which Pega construct is used to define a reusable set of fields and their validation that can be shared across multiple case types?
- A stage
- A flow action
- A case type
- A data type Correct answer.
Explanation
A data type defines a reusable structure of fields and can be referenced by multiple case types. Flow actions, case types, and stages are case-specific constructs rather than reusable field definitions.
Question 42Case Management
A process contains an assignment followed by a decision shape. What happens in Pega when the assignment is completed?
- The process continues to the decision shape and evaluates its condition Correct answer.
- The case is locked until a manager approves
- The assignment is automatically reassigned to the case creator
- The case immediately moves to the next stage
Explanation
After an assignment is completed, the process continues to the next shape, which may be a decision that evaluates a condition. Stage changes, locks, and reassignment do not occur automatically as a result of completing an assignment.
Question 43Case Management
Which Pega mechanism allows a designer to add a conditional path in a process so that one branch runs when a property equals a specific value?
- A section rule
- A decision shape with a condition Correct answer.
- A data transform
- A report definition
Explanation
A decision shape evaluates a condition and routes the process along the matching branch. Data transforms, section rules, and report definitions do not branch process execution.
Question 44Case Management
A case type must support a scenario where a case is sent back to an earlier stage for rework after a quality review fails. Which Pega capability enables returning to a previous stage?
- A UI control with a read-only condition
- A stage transition configured to target the earlier stage Correct answer.
- A data page scoped to the requestor
- A validation rule on the review assignment
Explanation
Stage transitions can target an earlier stage, allowing a case to return for rework when a review fails. Validation rules, data pages, and UI controls do not move a case back to a prior stage.
Question 45Case Management
In Pega case management, what is the relationship between a case type and a work class?
- A case type and a work class are unrelated concepts
- A work class contains multiple case types that share the same stages
- A work class is used only for reporting on cases
- A case type is instantiated as a work class that stores case data and rules Correct answer.
Explanation
A case type is backed by a work class that holds the case data and the rules that govern it. A work class does not contain multiple case types, and it is not limited to reporting.
Question 46Case Management
A designer needs to ensure that a case cannot enter a stage until a required document is attached. Which Pega approach enforces this?
- Change the stage's create setting
- Add a validation condition on the stage entry or on the preceding assignment Correct answer.
- Add a report definition to the stage
- Configure a stage SLA goal
Explanation
Validation conditions can enforce required data, such as an attached document, before the case proceeds into a stage. SLA goals, create settings, and report definitions do not enforce data completeness.
Question 47Case Management
Which Pega feature should be used to model a case that requires parallel processing of two independent verification tasks before continuing?
- A data transform that copies properties
- A single assignment routed to two operators
- A stage transition to an alternate stage
- A subprocess shape that runs multiple processes concurrently Correct answer.
Explanation
A subprocess shape can start multiple processes in parallel and wait for them to complete before continuing. A single assignment cannot be completed by two operators concurrently, and stage transitions and data transforms do not model parallel work.
Question 48Case Management
A case type must record an audit trail of stage changes for compliance. Which Pega capability provides this without custom development?
- A UI section that lists stages
- The case history and audit features that record lifecycle events Correct answer.
- A data page that caches stage names
- A report definition that queries case data
Explanation
Pega records case lifecycle events in case history and audit data, which can be used for compliance reporting. Report definitions, UI sections, and data pages do not by themselves capture lifecycle events.
Question 49Case Management
A designer wants to reuse a common set of stages across several related case types while allowing each to add its own stages. Which Pega approach supports this?
- Copy the stages into each case type manually
- Use a report definition to combine the case types
- Create a separate data type for each case type
- Define a parent case type with shared stages and create child case types that inherit and extend it Correct answer.
Explanation
Inheritance allows a parent case type to define shared stages that child case types reuse and extend with their own stages. Manual copying, separate data types, and report definitions do not provide reusable lifecycle definitions.
Question 50Case Management
In Pega case management, which element of a case type represents a distinct phase of the case lifecycle that groups related processes and can carry its own entry criteria?
- A flow action
- A data transform
- A section rule
- A stage Correct answer.
Explanation
A stage is the top-level lifecycle phase in a case type and groups the processes that run within that phase. Stages can be given entry criteria, so the case only enters them when the conditions are satisfied. Flow actions, data transforms, and sections are UI and data utilities, not lifecycle phases.