# Free PMI-ACP practice questions

> 10 free PMI-ACP practice questions with the correct answer and an explanation.

Page: https://devopscodelab.com/exams/pmi-acp/free-practice-questions/
Practice exams: https://devopscodelab.com/exams/pmi-acp/

### Question 1 of 10

An organization runs an agile suitability assessment for a new regulatory reporting project. The results show high scores for team trust and decision-making autonomy, but the project-attribute scores show requirements that are fixed by law and a deadline that cannot move. What is the MOST appropriate interpretation?

- A. Use a fully adaptive approach because the strong culture scores outweigh any concerns raised by the project attributes in the assessment
- B. Use a fully predictive approach because any fixed requirement means that agile practices would add risk without adding value to the project
- C. Repeat the assessment with a different group of stakeholders because results showing mixed scores indicate the tool was applied incorrectly
- D. Consider a hybrid approach: agile practices for collaboration and incremental delivery, with plan-based controls for the fixed legal scope

**Answer:** D

**Explanation:** Suitability tools score culture, team, and project attributes separately; mixed results commonly point toward a hybrid approach that fits each part of the work. Ignoring the fixed legal scope and deadline would understate real constraints. Choosing a purely predictive approach discards the strong team and culture readiness that agile practices can exploit. Mixed scores are a normal and informative outcome, not evidence that the tool was misused.

### Question 2 of 10

A team is asked to modernize a payroll calculation engine. The rules are well documented, experts can analyze them, and there is a known set of good practices, although analysis takes time. According to the Cynefin framework, which domain does this work MOST likely fall into?

- A. Complicated, where cause and effect can be determined through analysis and expertise
- B. Chaotic, where there is no discernible cause and effect and the team must act immediately
- C. Clear, where cause and effect are obvious to everyone and best practice applies directly
- D. Complex, where cause and effect can only be understood in hindsight through probing

**Answer:** A

**Explanation:** Work that requires expert analysis to find the right answer, with good practices available, sits in the complicated domain (sense-analyze-respond). The complex domain applies when outcomes emerge and require safe-to-fail probes. The clear domain fits work where the answer is obvious without expertise, which is not true here. The chaotic domain describes crises with no visible cause and effect, which does not match a documented rule set.

### Question 3 of 10

A team is building a recommendation feature for a new market where customer behavior is unknown and experts disagree on what will work. Using the Cynefin framework, how should the team approach the work?

- A. Apply the standard recommendation algorithm used in existing markets without any changes
- B. Ask a panel of experts to analyze the market and select the best practice before building
- C. Act immediately to stabilize the situation and only then decide whether analysis is needed
- D. Run several small, safe-to-fail experiments, observe the results, and amplify what works

**Answer:** D

**Explanation:** Unknown customer behavior and expert disagreement indicate the complex domain, where the right approach is probe-sense-respond through safe-to-fail experiments. Expert analysis fits the complicated domain, where answers can be found by analysis. Reusing an existing practice assumes the clear domain. Acting first to stabilize is the response for the chaotic domain, which describes a crisis rather than uncertainty about a new market.

### Question 4 of 10

During a daily coordination meeting, a usually talkative tester sits with arms crossed, avoids eye contact, and gives one-word updates. What should the agile practitioner do?

- A. Point out the tester's body language during the meeting so the whole team can address it together
- B. Check in privately with the tester after the meeting to understand if something is affecting them
- C. Ignore the behavior because daily meetings should focus only on progress toward the iteration goal
- D. Report the change in behavior to the functional manager so that it can be noted in a performance file

**Answer:** B

**Explanation:** Interpreting non-verbal cues and responding with empathy is part of emotional intelligence; a private check-in respects the person while showing care. Calling it out publicly can embarrass the tester and damage psychological safety. Ignoring clear signals may let a problem grow and harm team health. Escalating to a manager for documentation treats a possible personal concern as a performance issue and erodes trust.

### Question 5 of 10

A team has a recurring problem with late integration failures. The team proposes three solutions: more integration environments, contract testing, and an integration specialist. How should the agile practitioner help the team choose?

- A. Choose contract testing on the team's behalf because it is the most modern practice and is widely used in industry
- B. Ask management to select the option, since spending decisions on environments and staffing are outside the team
- C. Facilitate an evaluation of each option against value, cost, and effort, and let the team select and trial one
- D. Implement all three solutions at the same time so that the integration problem is eliminated as quickly as possible

**Answer:** C

**Explanation:** Determining resolution strategies with the team that add the most value means evaluating options against value and cost and letting the team decide and experiment. Choosing for the team removes ownership. Implementing everything at once is costly and hides which change worked. While some spending may need approval, handing the whole decision to management ignores the team's knowledge.

### Question 6 of 10

A product owner presents a story: 'As an admin, I want the reporting module so that I can manage the business.' The team cannot estimate it. Which INVEST characteristics does the story MOST clearly lack?

- A. Estimable and Negotiable, because the team prefers to negotiate the format with the product owner
- B. Small and Testable, because it is too broad to size and has no clear criteria for completion
- C. Valuable and Independent, because it delivers nothing to users and cannot be scheduled on its own
- D. Independent and Negotiable, because it depends on other stories and its details are already fixed

**Answer:** B

**Explanation:** A story covering an entire module with a vague benefit is too large to estimate and has no definition of what done looks like, so it fails Small and Testable. Nothing indicates dependencies or fixed details, so Independent and Negotiable are not the main issues. The story does state a value to an admin, even if vague, so lacking value is not the clearest gap. Negotiable is about details being open for conversation, which is not the problem here.

### Question 7 of 10

A Kanban team handles routine feature work, but production incidents occasionally arrive that must be handled immediately. How should the board be designed to handle both?

- A. Define an expedite class of service with its own lane and WIP limit of one, and track how often it is used
- B. Pause all feature work whenever an incident arrives until the backlog of incidents has been completely cleared
- C. Create a separate team for incidents so that the feature team's board never shows any unplanned interruptions
- D. Mark every production incident as the top priority in the normal lane so that it moves ahead of other items

**Answer:** A

**Explanation:** An expedite class of service with a strict limit lets urgent work bypass the queue while keeping it visible and constrained; tracking its use reveals whether incidents are disrupting flow too often. Placing incidents in the normal lane hides their special handling. Pausing all feature work is excessive. A separate team may be warranted at scale but loses visibility and adds handoffs for occasional incidents.

### Question 8 of 10

A product owner and customer disagree about whether a delivered story meets their needs. The acceptance criteria were met, but the customer's actual workflow differs from what was assumed. What should the agile practitioner do to strengthen collaboration?

- A. Have the team observe the customer's workflow and refine future stories with the customer present
- B. Insist that the customer accept the story because the agreed acceptance criteria were met exactly
- C. Remove the customer from reviews and rely on the product owner to represent their needs from now on
- D. Ask the customer to submit their workflow in writing so that the product owner can create stories

**Answer:** A

**Explanation:** Encouraging direct collaboration between the customer and team, including observing real workflows and refining stories together, closes the gap between assumptions and reality. Insisting on acceptance may be technically correct but does not solve the underlying collaboration issue. Written workflow descriptions are a weaker substitute for observation. Removing the customer worsens the disconnect.

### Question 9 of 10

Which of the following is an example of waste in software development according to Lean principles?

- A. Partially done work that has been coded but not yet integrated or tested
- B. Holding a short retrospective at the end of every iteration of the team
- C. Refactoring code to make it easier to change while preserving behavior
- D. Pair programming on a complex feature to share knowledge between members

**Answer:** A

**Explanation:** Partially done work is one of the seven wastes of software development because it ties up investment without delivering value and can become obsolete. Pair programming is a deliberate practice that improves quality and knowledge sharing. Refactoring keeps the design healthy and reduces future cost. Retrospectives are an investment in continuous improvement rather than waste.

### Question 10 of 10 (choose 2)

A team is starting work on a payments feature that depends on a third-party API the team has never used. Which TWO actions are MOST appropriate to manage this risk? (Choose two.)

- A. Add the risk response work to the backlog and prioritize it early
- B. Run a time-boxed technical spike to integrate with the API early
- C. Defer the integration until the last iteration when the rest is done
- D. Record the risk in a register and review it at the end of the release
- E. Ask the vendor for a written guarantee instead of testing the API

**Answer:** A, B

**Explanation:** A spike reduces uncertainty early by building a small proof of integration, and a risk-adjusted backlog schedules risk response work early alongside features. Reviewing the risk only at the end of the release leaves it unmanaged. Deferring integration pushes the risk to the point where it is most costly. A written guarantee does not reveal technical integration problems.

Ready for a timed run? Take the free 15-question PMI-ACP mini exam: https://devopscodelab.com/app/exams/pmi-acp/mini/

DevOpsCode Lab is not affiliated with PMI. PMI-ACP and related names are trademarks of their owners. We write every question ourselves; these are not real exam questions.
