.png&w=3840&q=75)
Question bank
SAFe Product Owner/Product Manager (POPM)
44 SAFe Product Owner/Product Manager (POPM) questions with the correct answer and a written explanation, organised across 6 exam domains.
- 44 questions
- 6 domains
- Foundation level
certilumQuestion index
Jump straight to any question. Answers and explanations are inline.
Apply AI to Product Roles
6 questions in this domain
- Question 1Single Choice
What must the System Demo showcase in a SAFe Agile Release Train (ART)?
- AThe integrated software or system produced by all teams on the ARTCorrect answer
- BThe individual outputs of each team on the ART
- CThe latest status report from the Release Train Engineer
- DA single high-priority feature demonstrated by one team
Why this is the answer
The System Demo must showcase the integrated software or system produced by all teams on the ART; individual team demos are not enough.
- Question 2Multiple Select
Which of the following statements about the System Demo are true for a Product Owner/Product Manager?
- AIt is a strategic touchpoint for gathering direct feedback from Business Owners and customers.Correct answer
- BIt provides empirical evidence of progress rather than subjective status reports.Correct answer
- CIts primary goal is to show off the work completed by each team.
- DThe Scrum Master is solely responsible for validating the system increment.
Why this is the answer
The System Demo gathers direct feedback and provides empirical evidence; showing off completed work and assigning validation only to the Scrum Master are common traps.
- Question 3Interactive
The code snippet is a simplistic model of a SAFe event. Which SAFe trap does this model commit?
- ATeam vs. System ConfusionCorrect answer
- BMisidentifying the Primary Goal
- CConfusing Roles
- DMisinterpreting WIP Limits
Why this is the answer
It treats the success of individual team demos as a successful system demo, which is the Team vs. System Confusion trap.
- Question 4Single Choice
If no integrated system can be demonstrated during the System Demo, what should the POPM infer?
- AThere is a failure in the integration pipeline and high technical debt or integration risk.Correct answer
- BThe teams have completed all PI Objectives.
- CThe System Demo timebox was too short.
- DThe ART is ready to move to PI Planning.
Why this is the answer
A missing integrated system demo signals integration pipeline failure, high technical debt, or integration risk.
- Question 5Multiple Select
Which two statements are common traps related to the Inspect and Adapt (I&A) event?
- AThinking that I&A is just a meeting for teams to talk about their feelings.Correct answer
- BConfusing the Problem-Solving Workshop with PI Planning.Correct answer
- CThe I&A event is optional in SAFe.
- DThe I&A event is only for the Release Train Engineer.
Why this is the answer
Common traps include thinking I&A is informal and confusing its workshop with PI Planning; I&A is a formal, structured event involving the ART.
- Question 6Interactive
The code snippet is used to calculate a flow metric in a value stream. Which metric does it represent?
- ALead timeCorrect answer
- BCycle time
- CWork in Process (WIP) limit
- DPredictability measure
Why this is the answer
Lead time measures the total time from customer request to delivery, while cycle time starts when work actually begins.
Iteration Execution
12 questions in this domain
- Question 7Single Choice
What does the System Demo primarily showcase in SAFe?
- AIntegrated solution built by all teamsCorrect answer
- BIndividual team outputs
- CTeam velocity trends
- DRelease burn-up chart
Why this is the answer
The System Demo must showcase the integrated software or system produced by all teams on the ART, not separate team-level results.
- Question 8Multiple Select
Which two actions reflect the stakeholder feedback loop at the System Demo?
- AGathering direct feedback from Business Owners and customersCorrect answer
- BValidating that the built increment meets business objectivesCorrect answer
- CComparing team member performance
- DFinalizing the release date
Why this is the answer
The System Demo is a strategic touchpoint where product management and product owners gather feedback and validate whether the increment satisfies business objectives.
- Question 9Interactive
Read the code block. Which System Demo trap is depicted?
- ATreating individual team demos as a System DemoCorrect answer
- BShowing off completed work
- CAssigning validation to the Scrum Master
- DFocusing on quantitative metrics
Why this is the answer
Assuming successful individual team demos equal a successful System Demo is the 'Team vs. System' trap; integration is the prerequisite for the System Demo.
- Question 10Single Choice
What is the primary goal of the System Demo in SAFe?
- AValidate integrated value and gather feedbackCorrect answer
- BShow off completed work
- CReport individual team progress
- DSet team-level performance goals
Why this is the answer
The System Demo's goal is to validate integrated value and gather feedback, not to showcase work completed or serve as a status meeting.
- Question 11Multiple Select
Which two types of data does the Inspect and Adapt event rely on?
- AObjective data, such as velocity and predictabilityCorrect answer
- BSubjective feedback from stakeholdersCorrect answer
- CPersonal opinions about team members
- DExternal market pricing data
Why this is the answer
I&A uses objective metrics and subjective feedback together to distinguish team-level issues from systemic ART-wide bottlenecks.
- Question 12Interactive
What is incorrect in the scenario shown in the code block?
- AProblem-Solving Workshop is confused with PI PlanningCorrect answer
- BRetrospective is confused with Inspect and Adapt
- CSystem Demo is confused with PI Planning
- DWIP limits are confused with capacity planning
Why this is the answer
The Problem-Solving Workshop is the structured event for root-cause analysis; confusing it with PI Planning is a common trap.
- Question 13Single Choice
What is the main purpose of the Problem-Solving Workshop?
- APerform root-cause analysis of systemic issuesCorrect answer
- BAssign blame for failed stories
- CPlan individual team tasks
- DReview personal performance
Why this is the answer
The Problem-Solving Workshop is the core engine of continuous improvement, using structured techniques to move from symptoms to root causes.
- Question 14Multiple Select
Which two improvement responsibilities belong to the POPM?
- ARefining backlog items based on lessons learnedCorrect answer
- BUpdating Definition of Done to prevent technical debtCorrect answer
- CFixing all team-level technical debt
- DRunning every team retrospective
Why this is the answer
POPMs improve readiness by refining the backlog and updating Definition of Done, while team-level debt is handled in team retrospectives.
- Question 15Interactive
Which flow-related trap is demonstrated in the code block?
- AConfusing speed with flowCorrect answer
- BMisinterpreting WIP limits
- CAssuming POPM solely owns technical flow
- DConfusing Retrospective with I&A
Why this is the answer
Increasing individual task speed without addressing bottlenecks often creates larger queues elsewhere; this is confusing speed with flow.
- Question 16Single Choice
Which statement correctly describes lead time and cycle time?
- ALead time is from customer request to delivery; cycle time is from start to completionCorrect answer
- BLead time is from start to completion; cycle time is from request to delivery
- CThey are the same metric
- DLead time applies to features; cycle time applies to stories
Why this is the answer
Lead time measures total time from customer request to delivery; cycle time measures time from start of work to completion.
- Question 17Multiple Select
Which two statements about WIP limits are true?
- AThey prevent multitasking and context switchingCorrect answer
- BThey increase productivity by focusing on completionCorrect answer
- CThey reduce productivity by limiting starts
- DThey are set primarily by the POPM
Why this is the answer
WIP limits restrict active work, preventing multitasking and focusing effort on finishing work, which increases throughput and predictability.
- Question 18Interactive
Which flow accelerator is missing in the code block?
- AEnsuring high-quality acceptance criteriaCorrect answer
- BReducing handoffs
- CAutomating testing
- DSetting WIP limits
Why this is the answer
The POPM contributes to flow accelerators by refining stories to a ready state with high-quality acceptance criteria, preventing sprint delays.
Leadership for PI Planning
7 questions in this domain
- Question 19Single Choice
According to the SAFe playbook, what must the System Demo at the ART level showcase?
- AIndividual team outputs shown separately
- BA list of completed user stories from each team
- CThe team's velocity and burndown charts
- DThe integrated software or system produced by all teams on the ARTCorrect answer
Why this is the answer
The System Demo must showcase the integrated software or system produced by all teams on the ART. Individual team outputs are not sufficient because the focus is on how the components function together.
- Question 20Multiple Select
According to the playbook, which stakeholders provide direct feedback to Product Management and Product Owners during the System Demo?
- ABusiness OwnersCorrect answer
- BCustomersCorrect answer
- CRelease Train Engineers
- DExternal auditors
Why this is the answer
Product Management and Product Owners gather direct feedback from Business Owners and customers during the System Demo. This feedback helps validate whether the built increment meets business objectives and supports backlog refinement.
- Question 21Interactive
When reviewing the list shown in the code block, what SAFe element is being described?
- ATeam Scope
- BSolution IntentCorrect answer
- CTeam backlog
- DWIP limit
Why this is the answer
The list describes intended behavior and capabilities that the solution must satisfy, which aligns with the Solution Intent. The System Demo validates that actual implementation matches this intended behavior.
- Question 22Single Choice
Which statement best describes the common trap of confusing team-level success with system-level success in SAFe?
- AInviting customers to observe the integrated solution
- BAssuming successful individual team demos are enoughCorrect answer
- CReviewing objective evidence of progress
- DUsing quantitative and qualitative measurement
Why this is the answer
A common trap is assuming that successful individual team demos equate to a successful System Demo. In SAFe, integration is the prerequisite for the System Demo.
- Question 23Multiple Select
Which activities are included in the formal Inspect and Adapt event for an Agile Release Train?
- AReviewing the PI System Demo resultsCorrect answer
- BReviewing quantitative and qualitative metricsCorrect answer
- CRunning a Problem-Solving WorkshopCorrect answer
- DAssigning individual blame for delays
Why this is the answer
The I&A event includes reviewing the PI System Demo results, participating in quantitative and qualitative assessment, and conducting a Problem-Solving Workshop to identify systemic issues and improvement actions.
- Question 24Interactive
What should the Product Owner infer from the WIP board state shown in the code block?
- AThe team is within the WIP limit and should pull more work
- BThe team exceeded the WIP limit, increasing multitasking and context switchingCorrect answer
- CLead time equals cycle time, so efficiency is high
- DThe bottleneck is in deployment and WIP limits should be removed
Why this is the answer
Exceeding WIP limits prevents the team from focusing on completion and increases multitasking and context switching. WIP limits are meant to improve throughput and predictability.
- Question 25Single Choice
What is a common trap when considering the primary goal of the System Demo for a Product Owner?
- AFocusing on validation of integrated value
- BGathering feedback from Business Owners
- CThinking the goal is to show off work completedCorrect answer
- DAssessing progress through empirical evidence
Why this is the answer
The primary goal of the System Demo is to validate integrated value and gather feedback. Thinking the goal is to show off work completed is a common trap.
PI Execution
5 questions in this domain
- Question 26Single Choice
What is the primary purpose of the System Demo in the SAFe PI Execution context?
- AThe integrated software or system produced by all teams on the ARTCorrect answer
- BThe individual outputs of separate teams
- CThe current status of each team's backlog
- DThe team's velocity and productivity metrics
Why this is the answer
The System Demo must showcase the integrated system built by all teams on the ART. The POPM focuses on how components work together, not on separate team outputs.
- Question 27Multiple Select
Which of the following are common traps to avoid during the System Demo? (Choose all that apply.)
- AAssuming that successful individual team demos mean a successful System DemoCorrect answer
- BThinking the goal is to validate integrated value and gather feedback
- CAttributing validation of the System Increment solely to the Scrum MasterCorrect answer
- DInviting Product Management and Business Owners to gather feedback
Why this is the answer
Common traps include treating team demos as equivalent to a system demo and assigning validation of the System Increment solely to the Scrum Master. Product Management and Product Owners own this validation.
- Question 28Interactive
Review the excerpt in the code block. Which SAFe System Demo trap is being illustrated?
- ATeam vs. System ConfusionCorrect answer
- BConfusing Roles
- CMisidentifying the Primary Goal
- DContinuous Integration Pillar failure
Why this is the answer
This is the 'Team vs. System' trap: assuming individual team demos equal a successful System Demo. In SAFe, integration is the prerequisite for the System Demo.
- Question 29Single Choice
What is the fundamental purpose of the Problem-Solving Workshop during the Inspect and Adapt event?
- AConduct root-cause analysis of systemic issues to generate actionable improvementsCorrect answer
- BCreate the PI plan and commitment for the next Program Increment
- CReview individual team retrospectives and team dynamics
- DAssign task ownership for team-level technical debt
Why this is the answer
The Problem-Solving Workshop uses root-cause analysis to move from symptoms to causes and create actionable improvement items for the next PI.
- Question 30Multiple Select
Which statements about WIP limits in the context of flow are correct? (Choose all that apply.)
- AWIP limits prevent multitasking and context switching.Correct answer
- BWIP limits increase productivity by focusing effort on completion rather than starting.Correct answer
- CWIP limits are a way to reduce team productivity.
- DWIP limits are primarily used to decrease PI scope.
Why this is the answer
WIP limits reduce multitasking and increase completion-focused work, thereby improving throughput. They do not reduce productivity or serve as a scope-cutting tool.
PI Planning Preparation
8 questions in this domain
- Question 31Single Choice
During a System Demo, what is the primary focus for a Product Owner or Product Manager in SAFe?
- AIndividual team outputs
- BIntegrated system from all ART teamsCorrect answer
- CTeam velocity charts
- DScrum Master status report
Why this is the answer
The System Demo must showcase the integrated solution produced by all teams on the ART; POPMs focus on how components work together, not individual team outputs.
- Question 32Multiple Select
In the context of a System Demo, which two common traps can undermine its value for the Product Owner or Product Manager?
- ASuccessful team demos equal a System DemoCorrect answer
- BValidating integrated value and feedback
- CShowing off completed work instead of feedbackCorrect answer
- DLimiting work in process
Why this is the answer
A System Demo is not the sum of team demos, and its goal is to validate integrated value and gather feedback, not to showcase completed work.
- Question 33Interactive
Examine the pseudo-code below. Which condition indicates a failure in the Continuous Integration pipeline for the ART?
- ASystem is demoable
- BSystem cannot be demonstratedCorrect answer
- CSolution intent is validated
- DNo pipeline failure raised
Why this is the answer
If the integrated system cannot be demonstrated, it indicates a failure in the integration pipeline, signaling high technical debt or integration risk.
- Question 34Single Choice
In the Inspect and Adapt event, what is the main purpose of the PI System Demo for stakeholders?
- AShow off completed team work
- BDemonstrate integrated solution incrementCorrect answer
- CPerform root cause analysis
- DSet WIP limits for next PI
Why this is the answer
The PI System Demo is the first part of I&A where the entire ART demonstrates the integrated solution increment and stakeholders provide feedback.
- Question 35Multiple Select
Which two statements are common traps related to the Inspect and Adapt event in SAFe?
- ATeams discuss feelings informallyCorrect answer
- BProblem-Solving Workshop equals PI PlanningCorrect answer
- CUse data and technical demos
- DReview PI System Demo results
Why this is the answer
I&A is a formal, data-driven event; the Problem-Solving Workshop is specifically for root-cause analysis, not PI Planning.
- Question 36Interactive
Examine the WIP limit logic below. Which active story count would cause a work-in-process violation?
- A3
- B4
- C5Correct answer
- D0
Why this is the answer
A WIP limit restricts active work; when active stories exceed the limit, it prevents multitasking and encourages completion.
- Question 37Single Choice
How does lead time differ from cycle time when measuring the efficiency of a value stream in SAFe?
- ALead: request to delivery; Cycle: start to completionCorrect answer
- BLead: start to completion; Cycle: request to delivery
- CThey measure the same duration
- DLead for features; Cycle for stories
Why this is the answer
Lead time covers the total customer-request-to-delivery duration, while cycle time covers only the active work period.
- Question 38Multiple Select
How can a Product Owner or Product Manager contribute to relentless improvement during I&A?
- ACapture I&A outcomes as backlog itemsCorrect answer
- BRefine backlog using lessons learnedCorrect answer
- CFix all team-level technical debt
- DReplace retrospectives with I&A
Why this is the answer
Relentless improvement requires converting I&A findings into actionable backlog items and applying lessons learned to backlog refinement and PI Planning.
Understanding Product Owner/Product Management Roles and Responsibilities
6 questions in this domain
- Question 39Single Choice
What is the primary purpose of the System Demo for the Product Owner/Product Manager?
- ATo validate the integrated value delivered by the Agile Release Train and gather stakeholder feedback.Correct answer
- BTo give each team a separate opportunity to present their completed stories.
- CTo provide a subjective status report on the ART's progress.
- DTo assign corrective actions to individual team members.
Why this is the answer
The System Demo is a strategic touchpoint to inspect the integrated increment and collect direct feedback from Business Owners and customers, not to present team-level outputs or subjective status reports.
- Question 40Multiple Select
Which of the following are recognized traps in the SAFe System Demo for the POPM?
- AAssuming successful individual team demos equal a successful System Demo.Correct answer
- BTreating the demo as an opportunity to show off completed work rather than to validate integrated value.Correct answer
- CAttributing validation of the system increment to the Scrum Master instead of the Product Manager and Product Owners.Correct answer
- DUsing objective data and metrics to assess the ART's progress.
Why this is the answer
The three common traps are Team vs. System confusion, misidentifying the primary goal as showing off completed work, and confusing roles by assigning validation to the Scrum Master. Using objective metrics is a positive practice, not a trap.
- Question 41Interactive
Refer to the exhibit to identify the value stream condition shown.
- ABottleneckCorrect answer
- BWork in Process limit
- CFlow accelerator
- DCycle time
Why this is the answer
The exhibit shows testing capacity lower than demand, causing work to pile up in a queue. This is a bottleneck, a point in the value stream where capacity is lower than demand.
- Question 42Single Choice
In SAFe, what does lead time measure?
- AThe total time from customer request to deliveryCorrect answer
- BThe time from when work starts to when it is completed
- CThe time a work item spends in an active queue
- DThe time between two successive releases
Why this is the answer
Lead time measures the total time from customer request to delivery, while cycle time measures the time from when work actually starts to completion.
- Question 43Multiple Select
Which practices are flow accelerators that POPMs can support?
- AReducing handoffsCorrect answer
- BAutomating testingCorrect answer
- CEnsuring high-quality acceptance criteriaCorrect answer
- DIncreasing work in process limits
Why this is the answer
Flow accelerators include reducing handoffs, automating testing, and ensuring high-quality acceptance criteria. WIP limits restrict active work rather than increase it, so increasing them is not a flow accelerator.
- Question 44Interactive
Refer to the exhibit. Which SAFe event does this sequence describe?
- AInspect and AdaptCorrect answer
- BPI Planning
- CIteration Retrospective
- DBacklog Refinement
Why this is the answer
The sequence of PI System Demo, quantitative and qualitative assessment, problem-solving workshop, and actionable improvement items describes the Inspect and Adapt event.
Frequently asked questions
Everything about the SAFe Product Owner/Product Manager (POPM) question bank and how to use it.