APM PMQ practice questions and answers 2026. Tap an option to test yourself — you'll see the correct answer and a plain-English explanation for every question. Free, no login.
Q11Despite producing a technically excellent product, a project's stakeholders reject it because it no longer aligns with their changing requirements. What does this situation illustrate?
✓ Correct answer: B. Defining success requires stakeholder satisfaction alongside technical quality, not quality alone
Meeting stakeholder needs is an essential measure of success that goes beyond simply achieving technical quality standards. Why the other options are incorrect: • Technical quality represents the primary measure of project success: Technical quality by itself is not sufficient to guarantee a successful project outcome. • Requirements should remain fixed and not evolve once delivery begins: Adapting requirements during a project is frequently necessary and should not be avoided. • Stakeholders ought to have no role in determining what success looks like: Stakeholders play a vital role in shaping what constitutes a successful project. • Achieving high quality ensures that stakeholders will accept the outcome: High-quality outputs do not automatically result in stakeholder acceptance.
Q12Which statement most accurately captures the role of governance within a project environment?
✓ Correct answer: B. To establish frameworks that ensure oversight, control and clear accountability for decisions
Governance puts in place the structures needed for oversight, control and accountable decision-making across the project. Why the other options are incorrect: • To concentrate all decision-making authority with the project manager: Governance distributes authority appropriately rather than channelling all decisions through the project manager. • To substitute formal controls with the judgement of senior managers: Governance relies on and supports controls; it does not replace them. • To eliminate delivery uncertainty by mandating detailed formal reports: Governance helps manage uncertainty but cannot eliminate it entirely. • To guarantee that all stakeholders share identical levels of decision-making power: Different stakeholders hold different levels of authority based on their roles.
Q13During the review of a high-risk project, the project manager pushes for fast approvals to keep things moving, but the board maintains that formal stage-gate reviews are required. What is the most compelling governance reason for the board's stance?
✓ Correct answer: B. Formal reviews give the board oversight and control before additional resources are committed
Formal stage-gate reviews are a governance mechanism that ensures further investment is only committed after informed, structured assessment, protecting the organisation from uncontrolled escalation. Why the other options are incorrect: • Stage-gate reviews eliminate the requirement for the project manager to exercise judgement: Good governance complements the project manager's judgement rather than replacing it. • The project board is responsible for approving every operational decision: Project boards are responsible for strategic oversight, not every operational decision. • Stage-gate reviews ensure the project will be delivered within agreed tolerances: While stage-gates strengthen control, they cannot guarantee that delivery will stay within tolerance. • Formal reviews stop stakeholders from introducing changes to requirements: Governance frameworks do not, and are not designed to, prevent all changes to requirements.
Q14A project team has been asked to roll out a process that has already been used effectively in another part of the organisation, with very little modification required. Which factor most strongly questions whether this work can genuinely be classified as a project?
✓ Correct answer: C. The absence of uniqueness in the work being carried out
A project must involve unique work; simply reproducing an established process significantly undermines this requirement. Why the other options are incorrect: • The fact that the deliverables have already been established: Defined deliverables are common to both project work and BAU activity. • The involvement of stakeholders from multiple divisions: The involvement of stakeholders is not limited to projects. • The requirement to obtain formal governance sign-off: Governance requirements are not exclusive to project environments. • The expectation that the work is completed within a fixed timeframe: Having a deadline does not, by itself, make something a project.
Q15A manager defines a project as 'any piece of work with a beginning and a finishing date'. What is the most valid criticism of this definition?
✓ Correct answer: C. It does not acknowledge that being temporary is not enough on its own — the work must also be unique
Being time-bound is not sufficient to define a project — it must also involve work that is unique. Why the other options are incorrect: • It makes no mention of the role of stakeholders: The involvement of stakeholders is not what fundamentally defines a project. • It fails to account for the need for governance frameworks: Governance structures are not part of the essential definition of a project. • It wrongly implies that all business-as-usual work is ongoing with no fixed endpoints: The primary gap in this definition is the absence of the uniqueness criterion. • It places too much focus on outputs at the expense of outcomes: The distinction between outputs and outcomes is not the core problem with this definition.
Q16A programme manager argues that an internal reporting initiative qualifies as a project, citing the fact that it required funding approval at the outset and resulted in a new dashboard. The team has since been continuously updating reports and adding small features on a monthly basis. Which assessment most accurately reflects the APM definition of a project?
✓ Correct answer: C. It no longer meets the definition of a project, as the work has become a routine operational activity
When work becomes routine and repetitive, it transitions from a temporary endeavour to business as usual, regardless of how it started. Why the other options are incorrect: • It still qualifies as a project because its outputs continue to be developed over time: Continued enhancement does not preserve project status; repeated activity is a sign of BAU. • It only counts as a project if the dashboard keeps changing based on feedback from stakeholders: Ongoing evolution is not what defines a project; the defining characteristic is that it is temporary. • It continues to be a project because it had a formal start and secured funding approval at the beginning: What the work looked like at the start does not determine how it should be classified now. • It qualifies as a project because it engages stakeholders and provides value to the organisation: Delivering value is not enough on its own to differentiate a project from BAU activity.
Q17Which of the following best captures a sophisticated, well-rounded understanding of what project success means?
✓ Correct answer: C. True success requires both the realisation of benefits and the satisfaction of stakeholders
A mature view of success looks beyond time, cost, and quality to focus on the value delivered and the satisfaction of those affected. Why the other options are incorrect: • A project succeeds when it meets its time, cost, and quality targets: Limiting success to time, cost, and quality targets provides an incomplete picture. • Success occurs when all planned outputs have been delivered as expected: Delivering outputs as planned is not enough to constitute true project success. • The project manager's individual performance determines whether the project succeeds: Project success cannot be reduced to the performance of a single individual. • A project is successful when its risk exposure has been reduced to a minimum: Minimising risk is part of good project management but does not in itself constitute success.
Q18When a project sponsor measures success purely by staying within budget, what is the greatest danger of this narrow definition?
✓ Correct answer: B. The project could produce deliverables that never achieve the intended benefits
When success is measured solely by cost, there is a real risk of overlooking whether the project creates value or achieves its intended benefits. Why the other options are incorrect: • Stakeholder relationships may be neglected by the project team: While stakeholder engagement could be affected, the primary concern is whether benefits are delivered. • The project manager's decision-making authority may be undermined: The project manager's authority is not inherently impacted by this definition. • Governance arrangements may grow overly complicated: The complexity of governance structures has no direct connection to this issue. • The project's lifecycle approach may require revision: The choice of project lifecycle is not the central concern here.
Q19Which of the following scenarios is most clearly an example of a project, as opposed to business as usual?
✓ Correct answer: C. Rolling out a new enterprise resource planning system for the first time
Deploying a new ERP system is a one-time, time-limited effort, which aligns with the characteristics that define a project. Why the other options are incorrect: • Producing monthly financial reports using established standard templates: Generating regular reports on a fixed schedule is a BAU activity. • Carrying out ongoing system maintenance and applying regular patches: System maintenance carried out on an ongoing basis is BAU. • Handling customer orders on a daily basis: Processing customer orders day-to-day is a BAU function. • Making routine updates to employee data held in HR systems: Keeping HR records up to date is a routine, BAU task.
Q20When a project manager brings a tolerance breach to the attention of the project board rather than handling it independently, which governance principle does this demonstrate?
✓ Correct answer: C. Decisions must be taken at the level that holds the relevant authority
Governance establishes defined authority levels and requires issues to be escalated when those delegated boundaries are breached. Why the other options are incorrect: • Delegated authority should be set aside whenever uncertainty is present: Delegated authority is not abandoned; escalation is the mechanism for respecting its limits. • The board should retain full control over day-to-day operations: Boards should not be involved in every operational decision. • Escalation is only triggered when the business case collapses: Escalation may be needed for any breach of tolerance, not only business-case failure. • The project manager should deflect responsibility for underperformance: Escalation reinforces accountability rather than helping someone avoid it.
Use the free APM PMQ Exam Prep 2026 sample, download the PDF, then unlock web-based timed mock exams for a full exam rehearsal.
Theory