PMI-ACP Product Practice Test 2 — 15 Questions

Question 1

A stakeholder demands that a feature be completed by next week. The team identifies this as a high-risk task. What should the Product Owner do?

Accepted Answer

Discuss the risks with the stakeholder and negotiate the timeline or scope.. When a stakeholder demands a high-risk feature on a tight timeline, the Product Owner should discuss the risks with the stakeholder and negotiate timeline or scope, because the PO is accountable for maximizing value while protecting the team's sustainable pace. This preserves transparency and allows informed trade-offs rather than committing to an unrealistic date. It also respects the team's self-management and the empirical nature of agile planning.

Answer

Force the team to work overtime to ensure completion.

Answer

Delegate the task to a junior developer to save costs.

Answer

Agree to the request to satisfy the stakeholder.

Question 2

An agile team is using 'Story Points' for estimation. Why is this preferred over 'Hours' for backlog items?

Accepted Answer

It accounts for complexity, effort, and uncertainty without needing precise time forecasting.. Story points are a relative, unitless measure that captures complexity, effort, and uncertainty together, which is why they are preferred over hours for backlog estimation. Because humans are better at comparing items than forecasting absolute durations, relative sizing produces more reliable estimates and avoids false precision. Story points also decouple estimation from individual time tracking, supporting team-based planning.

Answer

It is required by the project management office.

Answer

It makes it easier to track individual performance.

Answer

It ensures that every story takes exactly the same amount of time.

Question 3

During a sprint, a team member discovers a small bug. Where should this task be added?

Accepted Answer

To the product backlog.. In Scrum, the product backlog is the single source of truth for all work that may be needed in the product, including new features, enhancements, and bug fixes. A bug discovered during a sprint should be added to the product backlog so the Product Owner can prioritize it against other items. This keeps all work transparent and prioritized in one place.

Answer

To the personal notepad of the Scrum Master.

Answer

To a separate bug-tracking document outside of the product tool.

Answer

To the project charter.

Question 4

Which of the following is an effective technique for eliciting requirements from stakeholders?

Accepted Answer

Conducting user interviews or focus groups.. Conducting user interviews or focus groups is a direct, interactive elicitation technique that draws requirements straight from stakeholders through structured conversation, allowing the analyst to probe, clarify, and uncover latent needs. PMI-ACP and the Agile Manifesto emphasize 'individuals and interactions over processes and tools,' so face-to-face techniques like interviews and focus groups align with agile values. These methods produce rich, high-quality information that can be validated immediately with the stakeholder.

Answer

Building the entire product first and asking for feedback later.

Answer

Guessing the requirements based on past projects.

Answer

Waiting for the stakeholders to send an email.

Question 5

A team is struggling to keep their backlog refined. What is a sign of poor backlog refinement?

Accepted Answer

The team frequently asks for clarification during the sprint.. Frequent mid-sprint clarification requests signal that stories were not sufficiently refined—lacking clear acceptance criteria, dependencies, or shared understanding—before entering the sprint. Effective backlog refinement (grooming) ensures the team understands the 'what' and 'why' of upcoming stories, typically through the Definition of Ready. When the team constantly interrupts the PO during the sprint, it indicates refinement was superficial or skipped.

Answer

The team finishes all stories in the sprint.

Answer

The backlog is sorted by priority.

Answer

The product owner is involved in refinement.

Question 6

Which of the following describes the 'INVEST' model for user stories?

Accepted Answer

Independent, Negotiable, Valuable, Estimable, Small, Testable.. The INVEST model is a widely used acronym in agile for evaluating user story quality: Independent, Negotiable, Valuable, Estimable, Small, and Testable. These six criteria ensure stories are self-contained, flexible in implementation, deliver business value, can be sized, fit within an iteration, and have clear acceptance criteria.

Answer

Important, Notable, Validated, Explicit, Scalable, Technical.

Answer

Internal, New, Visible, Executable, Simple, Thorough.

Answer

Integrated, Necessary, Verified, Efficient, Structured, Tactical.

Question 7

A product owner needs to show the long-term product roadmap to the board. What is the most appropriate format?

Accepted Answer

A high-level view showing themes and time horizons.. An Agile product roadmap is a high-level, outcome-oriented view that communicates themes, epics, and time horizons (e.g., now/next/later or quarterly) rather than fixed dates and tasks. For a board audience, this format conveys strategic direction and adaptability while avoiding false precision. It aligns with Agile's empirical approach and allows for re-planning as market conditions change.

Answer

A detailed Gantt chart with fixed dates for every task.

Answer

A list of all team members and their assignments.

Answer

A printout of the entire product backlog.

Question 8

A product owner is refining the backlog. What is the best way to handle 'Technical Debt' items?

Accepted Answer

Incorporate them into the backlog and prioritize them alongside features.. Technical debt items should be incorporated into the product backlog and prioritized alongside features, because they represent work needed to maintain or improve the product's quality and maintainability. The product owner, in collaboration with the team, can then decide when to address them based on value and risk. This ensures transparency and allows for informed trade-offs.

Answer

Keep them hidden from stakeholders to avoid concern.

Answer

Ignore them until they cause a system crash.

Answer

Assign them to a separate 'technical' team only.

Question 9

A customer feedback session reveals a major flaw in the current product design. What is the first thing the Product Owner should do?

Accepted Answer

Analyze the feedback and update the backlog to address the issue.. The Product Owner is the sole person accountable for managing and ordering the product backlog, so the correct first response to significant customer feedback is to analyze it and reflect the findings in the backlog. This keeps the product aligned with customer value and allows the team to re-plan in the next refinement or sprint planning session. Deleting, ignoring, or blaming are all reactive behaviors that violate the PO's responsibility to maximize product value.

Answer

Ignore the feedback if the project budget is depleted.

Answer

Blame the development team for the flaw.

Answer

Immediately delete the feature from the product.

Question 10

An agile team is consistently failing to deliver the 'must-have' features by the release deadline. What should the Product Owner do?

Accepted Answer

Collaborate with stakeholders to re-negotiate scope or the release date.. When an agile team cannot deliver must-have features by the release deadline, the Product Owner's responsibility is to manage scope and stakeholder expectations, not to squeeze the team. Collaborating with stakeholders to re-negotiate scope or the release date respects the Agile principle of delivering value within sustainable pace and acknowledges that fixed scope, fixed date, and fixed quality cannot all be guaranteed simultaneously. This is the only option that addresses the root cause through transparent negotiation rather than coercion or quality compromise.

Answer

Remove the Scrum Master for not pushing the team harder.

Answer

Mandate mandatory weekend work for the team.

Answer

Lower the quality standards to get it done faster.

Question 11

A team has too many competing priorities. Which framework helps them focus?

Accepted Answer

MoSCoW prioritization.. MoSCoW prioritization is a widely used agile technique that categorizes requirements into Must have, Should have, Could have, and Won't have. It helps teams focus by explicitly agreeing on what is essential for the current delivery and what can be deferred, thereby reducing competing priorities. In PMI-ACP, MoSCoW is recognized as a simple, effective method for managing scope and ensuring stakeholder alignment on priority.

Answer

First-come, first-served based on email timestamps.

Answer

Random selection of tasks.

Answer

The 80/20 rule of project management.

Question 12

What is the primary role of the 'Definition of Done' (DoD)?

Accepted Answer

To ensure a common understanding of quality and completeness for all work items.. The Definition of Done is a shared, explicit checklist that determines when a product increment is complete and of acceptable quality. It creates a common understanding across the team, PO, and stakeholders of what 'done' means for every backlog item, preventing ambiguity about quality and completeness. Without a DoD, 'done' becomes subjective and technical debt accumulates.

Answer

To list the team members on the project.

Answer

To describe the user's requirements for the product.

Answer

To define the budget limit for the project.

Question 13

A team is working on a legacy product. How should the Product Owner balance new feature requests with maintenance?

Accepted Answer

Allocate a fixed percentage of capacity to maintenance and technical debt.. On a legacy product, the Product Owner should explicitly reserve a portion of each iteration's capacity for maintenance and technical debt so the system remains stable and evolvable while new features are delivered. This is a deliberate, transparent trade-off rather than an all-or-nothing choice. It reflects the agile principle of sustainable pace and the reality that technical debt compounds if ignored.

Answer

Devote 100% of capacity to new features.

Answer

Only perform maintenance during the weekends.

Answer

Only prioritize maintenance when the system fails.

Question 14

Which TWO of the following are characteristics of a good product vision?

Accepted Answer

It is concise and easy to understand.. Option B is correct because a good product vision must be concise and easy to understand so that everyone—developers, stakeholders, and customers—can quickly grasp the product's purpose and direction without wading through complexity. Option E is correct because an effective vision inspires the team and stakeholders, providing a shared, motivating long-term goal that guides decisions and sustains engagement throughout the product's lifecycle. In contrast, option A is wrong because a vision is not a complete feature list; detailed features belong in the product backlog, not the vision. Option C is wrong because a vision should be high-level and business-oriented, not a detailed technical specification. Option D is wrong because the vision is owned by the Product Owner (with stakeholder input) and is meant to be stable over time, not updated daily by the Scrum Master.

Answer

It includes a complete list of all product features.

Answer

It is written in a detailed technical specification.

Answer

It is updated daily by the Scrum Master.

Question 15

Which TWO of the following help ensure stakeholder alignment?

Accepted Answer

Frequent demonstrations of working software.. Option C (Frequent demonstrations of working software) is correct because regularly showing incrementally delivered, functioning software gives stakeholders concrete, verifiable visibility into progress and lets them validate that the product meets their needs, which builds shared understanding and alignment. Option E (Maintaining an open and transparent product roadmap) is correct because a visible, accessible roadmap communicates priorities, direction, and trade-offs so stakeholders share a common view of goals and can raise concerns early rather than after decisions are locked in. The remaining options do not support alignment: A (ignoring stakeholder requests) and B (isolating stakeholders from the development team) actively reduce communication and trust, while D (lengthy weekly status reports nobody reads) is a low-value, one-way communication channel that fails to create genuine shared understanding.

Answer

Ignoring stakeholder requests until the project is finished.

Answer

Keeping stakeholders isolated from the development team.

Answer

Sending lengthy weekly status reports that no one reads.