PMP, CAPM, Scrum, Six Sigma & ITIL 4: practice drill
10 realistic exam questions, graded as you go, with the exact rule or statute citation for every answer. Start free, no sign-up.
Timed mock exam
11 questions in 13 minutes, drawn from every topic. No answers shown until the end, then a full score breakdown, your weakest topics and a review of what you missed.
Prices are in US dollars, plus tax where it applies. Stripe, our payment processor, calculates tax at checkout.
All sales are final. If something is really wrong, such as a duplicate charge or a purchase that does not unlock what you bought, write to support@careerexampro.com and we will put it right.
One-time payment. Nothing renews.
You have an exam ticket for this practice test. Start the timed mock exam to use it.
Exact question counts, passing scores, and allowed reference materials vary by testing window and state/agency. Always confirm current rules with the official testing provider.
Sample questions
Midway through a product release cycle, a senior vice president instructs two Developers to move an executive dashboard to the top of the Product Backlog ahead of regulatory compliance work. Under the 2020 Scrum Guide, what is the governing rule for Product Backlog ordering?
The Product Owner is solely accountable for Product Backlog ordering, so executives must convince the Product Owner.
A governance committee of executives and Developers votes weekly to reprioritize urgent Product Backlog items.
The Scrum Master directly reorders the Product Backlog whenever leadership flags a higher-visibility priority.
Developers may place urgent executive items at the top of the Product Backlog provided they inform the Product Owner.
Show the answer
A. The Product Owner is solely accountable for Product Backlog ordering, so executives must convince the Product Owner.
According to the 2020 Scrum Guide, the Product Owner is one person—not a committee—who is solely accountable for maximizing product value and effective Product Backlog management, including ordering items. While the Product Owner may delegate tasks to others, they remain accountable, and anyone wishing to change the Product Backlog must do so by trying to convince the Product Owner.
During stakeholder analysis for a municipal transit modernization, a state environmental regulator holds statutory authority to suspend construction permits at any time, yet shows little interest in routine engineering details or weekly meetings. How should this stakeholder be classified and engaged using a Power/Interest grid?
High Power, High Interest (Manage Closely), involving them in daily stand-ups and detailed design reviews.
Low Power, High Interest (Keep Informed), sending detailed weekly task logs and team sprint velocity metrics.
Low Power, Low Interest (Monitor), providing only passive quarterly newsletters unless a permit expires.
High Power, Low Interest (Keep Satisfied), providing concise compliance updates without excessive operational detail.
Show the answer
D. High Power, Low Interest (Keep Satisfied), providing concise compliance updates without excessive operational detail.
On the Stakeholder Power/Interest grid (used in PMBOK Stakeholder Engagement, ASQ CSSGB Stakeholder Analysis, and ITIL 4 Engage practices), stakeholders with high authority/power but low day-to-day interest fall in the 'Keep Satisfied' quadrant. Engaging them with concise, proactive compliance summaries prevents sudden permit blocks without causing communication fatigue.
Halfway through a two-week Sprint, the Developers discover that a payment-gateway integration is far more complex than expected and that two lower-priority Sprint Backlog items cannot be finished, although the Sprint Goal remains achievable. According to the 2020 Scrum Guide, what should occur?
The Scrum Master extends the Sprint timebox by four days so the team finishes every item forecasted in Sprint Planning.
The Developers temporarily relax automated regression tests so every originally selected Sprint Backlog item is completed.
The Developers renegotiate Sprint Backlog scope with the Product Owner while keeping the Sprint Goal and quality intact.
The Scrum Team immediately cancels the Sprint because any scope change invalidates the initial Sprint Backlog forecast.
Show the answer
C. The Developers renegotiate Sprint Backlog scope with the Product Owner while keeping the Sprint Goal and quality intact.
The 2020 Scrum Guide states that the Sprint Goal is the single objective and commitment for the Sprint Backlog, creating coherence and focus while allowing flexibility regarding the exact work needed to achieve it. During the Sprint, quality does not decrease, the Sprint timebox is fixed, and scope may be clarified and renegotiated with the Product Owner as more is learned without endangering the Sprint Goal.
Reference: The 2020 Scrum Guide — The Sprint & Sprint Backlog Commitment (Sprint Goal)
Taking this exam soon?
Tell us which exam domains or calculation drills you want more practice on.