Try 60 free APM PFQ questions across the exam domains, with answers and explanations, then continue in PM Mastery.
This free full-length APM PFQ practice exam includes 60 original PM Mastery questions across the exam domains.
The questions are original PM Mastery practice questions aligned to the exam outline. They are not official exam questions and are not copied from any exam sponsor.
Count note: this page uses a 60-question full-length PFQ practice format for fundamentals review. Always confirm final exam-day rules, delivery details, and candidate instructions directly with APM before your scheduled exam.
Set a 60-minute timer and answer all 60 questions before reading explanations. Track misses by project context, planning, governance, people, risk, quality, or delivery-control fundamentals.
Use this page as a PFQ fundamentals diagnostic, not as the only measure of readiness. The most useful result is the pattern behind your misses.
| Result pattern | What it usually means | Next step |
|---|---|---|
| Strong score and misses are scattered | Your basic terminology and process awareness may be close. Review explanations and keep timing steady. | |
| Many life-cycle or planning misses | Revisit project stages, planning purpose, baseline concepts, and control points. | |
| Many scope, schedule, or resource misses | Drill the difference between product scope, work scope, scheduling logic, and resource constraints. | |
| Many risk, issue, or quality misses | Review the difference between future uncertainty, current problems, assurance, and control. | |
| Timing breaks down | Practice shorter timed blocks, then return to a full 60-question run. |
Use this worksheet immediately after the run, before rereading the explanations.
| Field | Record |
|---|---|
| Overall score | ___ / 60 questions |
| Timing result | Finished early / on time / rushed late |
| Highest-miss area | life cycle / planning / scope / scheduling / risk and issue / quality / communication / leadership |
| Most expensive mistake type | confused term / wrong process stage / weak role judgment / overthinking fundamentals / other: ___ |
| Next focused page | ___ |
This static page is useful for one full diagnostic pass. PM Mastery is the better place for repeated practice because it gives you varied attempts and progress history instead of one page you can memorize.
| Need after this diagnostic | Use PM Mastery for… |
|---|---|
| New mixed attempts | Timed PFQ sets that reduce answer-recognition bias. |
| Fundamentals repair | Focused terminology, life-cycle, planning, scope, schedule, risk, quality, communication, and teamwork drills. |
| Explanation review | Item-level explanations that help you separate adjacent project-management terms. |
| Progress tracking | A single web/mobile account with practice history across sessions. |
| Final readiness checks | Varied timed attempts after weak areas have been repaired. |
For the cleanest diagnostic result, answer the questions under timed conditions before reading the explanations.
| Checkpoint | Approximate time budget | What to do |
|---|---|---|
| Questions 1-20 | 20 minutes | Keep terminology decisions quick; do not overbuild scenarios. |
| Questions 21-40 | 40 minutes cumulative | Watch for risk-versus-issue and assurance-versus-control wording. |
| Questions 41-60 | 60 minutes cumulative | Finish with enough time to review marked fundamentals traps. |
If you retake this free diagnostic, treat the second attempt as a reasoning check rather than a fresh score. Some stems and answers will be familiar, so the percentage can overstate readiness.
For readiness decisions, give more weight to varied timed attempts in PM Mastery than to repeating one static page.
| Item | Detail |
|---|---|
| Issuer | Association for Project Management |
| Exam route | APM PFQ |
| Official exam name | APM Project Fundamentals Qualification (PFQ) |
| Full-length set on this page | 60 questions |
| Exam time | 60 minutes |
| Topic areas represented | 10 |
| Topic | Approximate official weight | Questions used |
|---|---|---|
| Understand Project Management and the Operating Environment | 10% | 6 |
| Understand Project Life Cycles | 7% | 4 |
| Understand Roles and Responsibilities within Projects | 2% | 1 |
| Understand Project Management Planning | 19% | 12 |
| Understand Project Scope Management | 14% | 8 |
| Understand Resource, Scheduling and Optimisation in a Project | 10% | 6 |
| Understand Project Risk and Issue Management in Context | 14% | 8 |
| Understand Quality in the Context of a Project | 10% | 6 |
| Understand Communication in the Context of a Project | 8% | 5 |
| Understand Leadership and Teamwork within a Project | 6% | 4 |
Topic: Understand Leadership and Teamwork within a Project
A project to roll out a new HR system has all the required specialists assigned full-time. However, the team is split across three countries, rarely meets in person, and handovers between time zones are causing misunderstandings. Which team-development challenge is most clearly shown?
Best answer: A
What this tests: Understand Leadership and Teamwork within a Project
Explanation: This situation points to dispersed working. The team has the right people and they are available, but being spread across locations and time zones is creating communication and coordination difficulties.
Dispersed working is a team-development challenge that occurs when project team members are separated by location, time zone, or limited face-to-face contact. In this scenario, the important clue is that the required specialists are already assigned full-time, so the problem is not skill mix or availability. The misunderstandings during handovers arise because the team is working across countries and time zones, which can reduce collaboration, shared understanding, and team cohesion.
A challenge such as accountability would involve unclear ownership of tasks or decisions. Conflict would involve direct disagreement or tension between people. Here, the stem mainly describes the practical difficulty of coordinating a geographically spread team.
The main challenge is that the team is geographically separated, making coordination and shared understanding harder.
Topic: Understand Project Management Planning
Why is an approved baseline useful during project delivery?
Best answer: B
What this tests: Understand Project Management Planning
Explanation: An approved baseline is used as a reference point for monitoring and control. By comparing actual progress with the agreed plan, the project team can identify variances and decide whether corrective action is needed.
A baseline supports monitoring and control because it gives the project a stable, approved point of comparison. During delivery, actual progress, cost, scope, or performance can be checked against that agreed position to see whether the work is proceeding as intended. If there is a gap between actual results and the baseline, the project manager and governance can investigate, report the variance, and decide on corrective action or change control.
Without a baseline, it is much harder to judge whether the project is on track, because there is no agreed standard against which to measure performance. The closest distractors describe other useful project management artifacts, but they do not provide the reference point needed for control.
A baseline provides the approved reference point needed to monitor progress and control deviations.
Topic: Understand Leadership and Teamwork within a Project
A project team leader can influence team performance by setting clear direction, encouraging collaboration and ____.
Best answer: B
What this tests: Understand Leadership and Teamwork within a Project
Explanation: Leadership influences team performance through direction, motivation and support for effective teamwork. Motivating team members fits this directly, while the other options are governance, control or procurement activities rather than leadership actions.
In PFQ terms, leadership is about influencing people so the project team can achieve its objectives. A project team leader improves team performance by giving the team clarity, building commitment and encouraging people to work well together. Motivation is central because it affects engagement, effort and cooperation across the team.
A leader typically influences performance by:
Tasks such as approving business justification, keeping configuration records or authorising contracts may be important on a project, but they do not describe the main way a team leader influences how the team performs.
Motivation is a core leadership action that directly affects how well the team works together and performs.
Topic: Understand Project Scope Management
A project team discovers that two different versions of an approved design drawing are being used. They need to confirm the current version and trace who authorised each update. Which PFQ concept best fits this situation?
Best answer: B
What this tests: Understand Project Scope Management
Explanation: This situation is about identifying, recording, and tracking product versions. That is configuration management, which helps ensure the team uses the correct approved item and can trace its status over time.
Configuration management is used to identify product items, record their version and status, and maintain traceability of approved changes. In this case, the main problem is that different versions of the same drawing are in use, so the team needs to establish which version is current and what approvals led to it. That is a product-control question rather than a decision about whether to approve a new change.
Change control is the process for assessing and deciding whether a proposed change should be accepted. Here, the key need is version identification and status tracking, which sits within configuration management. The main takeaway is that configuration management controls product information, while change control decides on proposed alterations.
Configuration management controls product versions and status so the team can identify the correct approved drawing and its history.
Topic: Understand Leadership and Teamwork within a Project
In a temporary project team, which statements explain why leadership matters?
Which option contains the correct set?
Best answer: D
What this tests: Understand Leadership and Teamwork within a Project
Explanation: Leadership matters in temporary project teams because people are brought together for a limited time and need direction, motivation, and collaboration quickly. Good leadership helps the team align around goals, work well together, and maintain performance as the project changes.
Temporary project teams do not usually have long-established relationships, routines, or reporting lines, so leadership has a strong effect on team performance. It helps create a clear purpose, gives direction, builds trust, and encourages collaboration across people who may not have worked together before. Leadership also helps maintain motivation and focus when priorities change or pressure increases during the project.
Structured communication is still needed on a project. Leadership supports communication, but it does not replace communication planning or agreed communication methods.
The key idea is that leadership improves how quickly a temporary team becomes effective and stays effective.
These statements reflect how leadership helps a temporary team align quickly, work together effectively, and sustain performance.
Topic: Understand Project Management and the Operating Environment
A service desk handles user incidents every day using an established process to keep systems running. Which PFQ concept does this describe?
Best answer: C
What this tests: Understand Project Management and the Operating Environment
Explanation: This describes business as usual because the work is continuous, repeatable, and focused on maintaining current operations. A project would be temporary and set up to deliver change, not to run an established service day after day.
Business as usual refers to ongoing operational activity that keeps an organisation functioning. In the stem, the service desk is following an established process every day to maintain current service performance, so the work is operational rather than temporary. That is different from a project, which has a defined start and finish and is created to deliver change or a specific output.
A useful check is:
The key distinction here is maintaining an existing service versus delivering a temporary change.
It is ongoing operational work that maintains an existing service rather than delivering a temporary change.
Topic: Understand Project Risk and Issue Management in Context
Complete the statement.
Risk management addresses uncertain events that may affect a project in the future, whereas issue management addresses events that ___.
Best answer: B
What this tests: Understand Project Risk and Issue Management in Context
Explanation: The key difference is timing and uncertainty. Risks are possible future events, but issues are present events or problems that already exist and need immediate management.
In PFQ terms, a risk is an uncertain event or set of circumstances that, if it occurs, can affect project objectives. That means risk management is concerned with something that might happen in the future. An issue is different because it already exists or is happening now and needs action to resolve or contain it.
This is why projects usually record risks in a risk register and issues in an issue log. The main distinction is not whether the event is internal or external, or whether it is large or small; it is whether the situation is still uncertain or has become a current fact. If it has already happened, it is no longer a risk to manage as uncertainty; it is an issue to address.
An issue is a current reality requiring action, while a risk is still uncertain and may or may not occur.
Topic: Understand Quality in the Context of a Project
Which option contains only examples of quality control?
Best answer: C
What this tests: Understand Quality in the Context of a Project
Explanation: Quality control means checking outputs, or sometimes operational processes, against agreed quality requirements. Comparing finished deliverables with criteria and testing them against specifications are both quality control activities.
Quality control is the part of quality management that checks whether outputs meet the required standard. In this question, comparing the user guide with acceptance criteria and testing the online form against its specification are both direct checks of deliverables against defined requirements.
Setting defect tolerances is done earlier to define the expected standard, so that is part of quality planning. Auditing whether the project is following the organisation’s quality system is about confidence in the way quality is being managed, which is quality assurance rather than quality control.
A useful distinction is that quality control checks the result, while quality assurance checks the approach used to achieve it.
These are both checks of completed outputs against defined quality requirements, which is quality control.
Topic: Understand Project Management Planning
A project manager agrees the project’s planned dates and costs with the sponsor at the start of a digital service rollout. In each progress report, she compares actual performance against those agreed figures. What is the main purpose of the baseline in this situation?
Best answer: B
What this tests: Understand Project Management Planning
Explanation: A baseline is the approved reference point for the project plan. It allows the project manager to compare what was planned with what has actually happened and report any differences.
In project management, a baseline is the approved version of part of the project management plan, such as schedule or cost, that is used as a basis for comparison. In this scenario, the manager is using the agreed dates and costs to check actual performance and identify variance from plan. That is the core purpose of a baseline: it supports monitoring and control by showing whether the project is on track against what was originally agreed.
A business case explains why the project should be done, a responsibility assignment approach shows who does what, and a communication plan sets out how information will be shared. None of those is the main comparison point for planned versus actual progress.
A baseline is the agreed version of the plan used as the reference point for measuring actual progress and identifying variance.
Topic: Understand Project Life Cycles
A company is replacing its customer portal. The project has fixed approval points for design, build and rollout, but the portal screens are developed in short cycles using user feedback before release. Which life cycle description best fits this project?
Best answer: B
What this tests: Understand Project Life Cycles
Explanation: This project uses both linear and iterative features, so it is a hybrid life cycle. The fixed approval points show linear planning, while repeated development cycles with user feedback show iterative development.
A hybrid life cycle is used when a project combines structured, sequential elements with iterative development. In this scenario, the fixed approval points for design, build and rollout show planned linear control, while developing portal screens in short cycles with user feedback shows iterative delivery. That mix is the key indicator of a hybrid approach.
A purely linear life cycle would not normally refine the product through repeated cycles, and a purely iterative life cycle would not be defined mainly by fixed sequential stage approvals. An extended project life cycle is about considering activities before and after delivery, not about mixing linear and iterative ways of working.
It combines linear planning and governance with iterative development of the solution.
Topic: Understand Project Risk and Issue Management in Context
A possible future delay in receiving equipment may affect a project’s objectives, but it has not happened yet. In APM PFQ terms, what is this called?
Best answer: B
What this tests: Understand Project Risk and Issue Management in Context
Explanation: A risk is an uncertain event or set of circumstances that may affect project objectives if it occurs. Because the delay is only a possible future event and has not yet happened, it fits the risk concept rather than an issue.
In APM PFQ, a risk is something uncertain that could affect the achievement of objectives if it happens. The key clue is that the equipment delay is possible and future-based, not current and confirmed. That makes it a risk.
An issue is different because it already exists and needs action now. An assumption is something accepted as true for planning purposes. A change request is a proposal to alter some aspect of the project. The simplest test is: if it might happen, it is a risk; if it has happened already, it is an issue.
It is a risk because it is an uncertain future event that could affect the achievement of project objectives.
Topic: Understand Project Management and the Operating Environment
Which statements describe project objectives rather than programme or portfolio-level purposes?
Best answer: A
What this tests: Understand Project Management and the Operating Environment
Explanation: Project objectives are specific aims for delivering a defined output or outcome within a particular project. The statements about delivering a payroll system and relocating a team are project-focused, while the others describe wider coordination of benefits or strategic investment decisions.
A project objective is a specific, defined aim for a single project, usually focused on delivering a particular output, capability, or change. In this question, delivering a payroll system and relocating a team to a refurbished office are both clear, bounded pieces of work with a direct delivery focus.
By contrast, coordinating several related change initiatives to realise benefits is a programme-level purpose, because programmes align related projects to achieve outcomes and benefits. Prioritising investment across projects to support strategy is a portfolio-level purpose, because portfolios focus on selecting and balancing change initiatives to meet organisational objectives.
The key distinction is that projects deliver specific outputs, while programmes and portfolios provide broader coordination or strategic direction.
These are specific delivery aims for a defined piece of work, which is characteristic of a project objective.
Topic: Understand Project Risk and Issue Management in Context
During a digital service rollout, a supplier fails to deliver a required training pack on the agreed date. The delay has already happened and the project team must decide what to do next. Which PFQ concept best matches this situation?
Best answer: C
What this tests: Understand Project Risk and Issue Management in Context
Explanation: This situation is an issue because the problem has already happened and is affecting the project now. In PFQ terms, risks are uncertain future events, but an issue is a current matter that needs management action.
The core distinction is whether the problem is still uncertain or has already occurred. In the stem, the supplier has already missed the agreed delivery date, so the project is dealing with a present problem, not a possible future event. That makes it an issue.
A risk is something that might happen and could affect the project if it occurs. Once that event actually happens, it is no longer managed only as a risk; it must be handled as an issue that needs action, ownership, and resolution. A good test is to ask: “Has it happened yet?” If the answer is yes, treat it as an issue.
The closest distractor is risk, but the missed delivery is no longer uncertain.
An issue is a problem that has already occurred and now needs action or resolution.
Topic: Understand Project Management Planning
Why should stakeholder analysis be carried out before planning stakeholder engagement on a project?
Best answer: C
What this tests: Understand Project Management Planning
Explanation: Stakeholder analysis is used to understand who the stakeholders are, what they need, and how much influence they have. That information is then used to shape an appropriate engagement approach for each stakeholder or stakeholder group.
The purpose of stakeholder analysis is to help the project decide how to engage with people and groups affected by, or able to affect, the project. By identifying stakeholder interest, influence, expectations, and attitudes, the project manager can plan suitable levels of communication and involvement. This makes engagement planning more effective because it is based on stakeholder needs and project impact, rather than using the same approach for everyone.
A scope definition option belongs to scope management, a critical path option belongs to scheduling, and an issue-recording option belongs to issue management. The key link here is that stakeholder analysis directly informs how engagement should be planned.
Stakeholder analysis informs engagement planning by showing who matters most and how they should be involved or communicated with.
Topic: Understand Project Management Planning
Complete the statement. In developing a business case, the sponsor is accountable for the business justification, while the project manager provides ______.
Best answer: C
What this tests: Understand Project Management Planning
Explanation: The sponsor is accountable for the business case because it explains why the project should proceed. The project manager supports that work by supplying realistic delivery information, such as likely time, cost, risk, and approach.
In PFQ, the business case is owned by the sponsor because it provides the business justification for the project and links the work to organisational objectives and expected benefits. The project manager helps develop it by contributing delivery-related input, such as estimates, assumptions, risks, dependencies, and planning information. That input helps the sponsor judge whether the proposed project is viable and worthwhile.
A common mistake is to confuse contributing project data with owning the business case itself.
The project manager typically contributes practical delivery information to inform the sponsor’s business case, but does not own the justification.
Topic: Understand Project Management Planning
Which term describes examining stakeholders’ interest, influence and attitude so the project can decide how to engage with them?
Best answer: D
What this tests: Understand Project Management Planning
Explanation: Stakeholder analysis is used to understand stakeholders and their likely impact on the project. That information then informs engagement planning, including how and when different stakeholders should be involved or communicated with.
Stakeholder analysis is the activity of identifying stakeholders and assessing factors such as their interest, influence, needs, and attitudes toward the project. In APM PFQ, this analysis helps the project manager and sponsor decide the most appropriate engagement approach for each stakeholder or stakeholder group.
Without stakeholder analysis, engagement planning is likely to be generic and may miss key people, concerns, or levels of influence. A communication plan may record how communication will happen, but stakeholder analysis provides the insight that should shape that plan and wider engagement activity. The key idea is that analysis comes first, then the engagement approach is tailored using that information.
Stakeholder analysis assesses who stakeholders are and how they should be engaged.
Topic: Understand Quality in the Context of a Project
What is the purpose of a benefit review?
Best answer: D
What this tests: Understand Quality in the Context of a Project
Explanation: A benefit review checks whether the project has delivered the benefits that were expected in the business case or benefits plan. Its focus is not phase approval, product inspection, or lessons learned, but benefit realisation.
A benefit review is a review used to determine whether the expected benefits from a project have actually been realised. It looks beyond whether the project delivered outputs on time or to specification and asks whether those outputs produced the intended business improvement or value. Because benefits may only appear after the deliverables are in use, a benefit review often takes place after implementation or even after project closure.
This makes it different from other review types:
The key point is that a benefit review focuses on outcomes and realised value, not just delivery performance.
A benefit review is carried out to assess whether the benefits identified for the project have actually been achieved.
Topic: Understand Leadership and Teamwork within a Project
A project team has just been formed, and several members are unclear about their roles and how they should work together. What is the main benefit of the project manager using clear and supportive leadership behaviour at this stage?
Best answer: D
What this tests: Understand Leadership and Teamwork within a Project
Explanation: Leadership behaviour can improve team performance by giving direction, building confidence, and helping people work well together. In a newly formed team, clear and supportive leadership is especially useful because members often need guidance on roles and ways of working.
The core concept is that leadership influences team performance. When a team is newly formed or uncertain, leadership behaviour that is clear and supportive helps people understand expectations, align around goals, and begin collaborating effectively. This can reduce confusion, improve trust, and create the conditions for better teamwork and delivery.
In this situation, the project manager is not mainly carrying out a planning, risk, or quality activity. The benefit comes from shaping how the team works together. Effective leadership helps a team move from uncertainty toward productive working relationships, which is why it matters most when roles and interactions are still unclear.
The key takeaway is that leadership behaviour supports team effectiveness, while the other options describe different project management functions.
Clear and supportive leadership gives early direction and helps a new team coordinate its work more effectively.
Topic: Understand Quality in the Context of a Project
What is the purpose of quality management in a project?
Best answer: C
What this tests: Understand Quality in the Context of a Project
Explanation: Quality management exists to make sure project outputs meet agreed requirements and are fit for purpose. In PFQ terms, it is about defining, checking, and assuring the level of quality needed, not about scope approval, risk recording, or resource allocation.
In a project, quality management focuses on making sure the deliverables meet the required standards and stakeholder needs. Its purpose is not simply to inspect work at the end, but to plan quality requirements, control the quality of outputs, and provide assurance that the right processes are being followed. This helps the project produce outputs that are fit for purpose and acceptable to the customer or user.
A useful way to see it is:
The key distinction is that quality management is about meeting requirements, whereas nearby concepts deal with changing scope, managing uncertainty, or organising resources.
Quality management is concerned with planning, controlling, and assuring quality so project outputs satisfy agreed requirements.
Topic: Understand Project Life Cycles
In a typical APM linear life cycle, what is the main purpose of the transition phase?
Best answer: B
What this tests: Understand Project Life Cycles
Explanation: The transition phase focuses on moving the project’s outputs into operational use. In a linear life cycle, this is distinct from the early work of shaping the project and the final work of formally closing it.
In an APM linear life cycle, each phase has a different purpose. The transition phase is concerned with handing over completed outputs so they can be used, supported, and embedded in the operational environment. That makes it different from concept, which explores the need and feasibility; definition, which develops requirements and plans; and closure, which formally ends the project and captures learning. Recognizing the purpose of each phase helps distinguish where a project is in its life cycle.
The transition phase is where the completed outputs are transferred into use so the business can adopt and operate them.
Topic: Understand Project Management Planning
Why is a deployment baseline in an iterative life cycle often different from one in a linear life cycle?
Best answer: A
What this tests: Understand Project Management Planning
Explanation: A deployment baseline reflects how and when outputs will be deployed. In a linear life cycle this is often planned as a single main deployment, while in an iterative life cycle it is commonly aligned to multiple releases or increments.
The key idea is that the deployment baseline should match the life cycle being used. In a linear life cycle, deployment is often planned around a single major release at or near the end of the project, so the baseline is usually more fixed and end-focused. In an iterative life cycle, deployment may happen several times as usable increments are completed, reviewed, and agreed. That means the deployment baseline is more likely to be arranged around multiple planned releases rather than one final deployment point.
This difference is about aligning deployment planning to the way work is delivered. It is not about replacing change control, creating a work breakdown structure, or assigning responsibilities.
An iterative life cycle may deploy outputs release by release, so the deployment baseline is usually set around those planned increments rather than one final deployment.
Topic: Understand Quality in the Context of a Project
What is the main purpose of quality assurance in a project?
Best answer: A
What this tests: Understand Quality in the Context of a Project
Explanation: Quality assurance focuses on the suitability and effectiveness of the processes used to achieve quality. Its purpose is to give confidence that the project is using appropriate methods, rather than checking the final output itself.
Quality assurance is the part of quality management that provides confidence that quality requirements will be fulfilled because the right processes are in place and being followed. In a project, it is about whether the approach to quality is appropriate, consistent, and effective. This is different from checking completed deliverables for errors or setting the quality requirements at the start. The key idea is process confidence: if the quality processes are suitable and applied properly, the project is more likely to produce outputs that meet expectations.
The closest distractor is inspecting deliverables, but that is quality control rather than quality assurance.
Quality assurance is concerned with checking that the processes used to achieve quality are suitable and consistently applied.
Topic: Understand Communication in the Context of a Project
A project team is spread across three locations and will run a requirements workshop by video call instead of meeting in person. Compared with face-to-face communication, which is the main disadvantage of the virtual method in this situation?
Best answer: A
What this tests: Understand Communication in the Context of a Project
Explanation: The main disadvantage is that virtual communication makes it harder to see body language, facial expression, and other non-verbal signals. In a requirements workshop, this can make misunderstanding or missed concerns more likely.
Virtual communication is useful when project participants are in different places, but it also has drawbacks. One important disadvantage is the reduced ability to observe non-verbal communication such as body language, eye contact, and subtle reactions. In a requirements workshop, those signals help people test understanding, notice uncertainty, and resolve confusion quickly. When those cues are weaker or missing, the risk of misunderstanding increases.
This matters most when the team needs shared understanding, discussion, and clarification. By contrast, reduced travel, easier attendance for remote people, and the ability to record sessions are typical advantages of virtual methods, not disadvantages.
Virtual communication can reduce visibility of body language and other cues, making misunderstanding more likely.
Topic: Understand Project Life Cycles
A retail company is refurbishing stores to a fixed design while also developing a mobile app whose features will be refined through user feedback. What is the main benefit of using a hybrid life cycle for this project?
Best answer: C
What this tests: Understand Project Life Cycles
Explanation: A hybrid life cycle is helpful when a project contains different types of work. In this scenario, the store refurbishment is predictable, while the app features need refinement through feedback, so combining linear and iterative approaches is the key benefit.
A hybrid life cycle is used when different parts of a project need different delivery approaches. In the scenario, the physical store refurbishment is well defined and suits a more linear sequence of phases, while the mobile app features are likely to change as users give feedback, which suits an iterative approach. The benefit of a hybrid life cycle is that it allows the project to use the most appropriate method for each part of the work instead of forcing one approach onto everything.
This is different from an extended life cycle, which looks beyond delivery and handover into operation, benefits realisation, and eventual withdrawal or disposal. The key point is that hybrid is about mixing delivery approaches within the project life cycle.
A hybrid life cycle is used when some parts of the project are stable and predictable, while others need iteration and feedback.
Topic: Understand Project Scope Management
Which option contains only stages of a typical project change control process?
Best answer: A
What this tests: Understand Project Scope Management
Explanation: Change control manages proposed changes in a controlled way. The usual stages are to log the request, assess its impact, decide whether to approve it, and then update records and communicate the outcome. Assigning a risk owner belongs to risk management, not change control.
Change control is used to handle proposed changes before they are made to approved project scope or other baselines. A typical sequence is to record the change request, assess its likely impact, make a decision to approve or reject it, and then update the relevant project records or baselines and communicate that decision. This helps keep the project controlled and traceable.
The statement about assigning a risk owner is different. That is a risk management activity, where responsibility for managing a risk is allocated to someone. It may happen in the same project, but it is not a stage of the change control process.
A good check is whether the activity helps move a change from request to decision to controlled update.
These statements follow the normal change control flow: record, assess, decide, then update records and communicate the outcome.
Topic: Understand Resource, Scheduling and Optimisation in a Project
A project relies on one specialist supplier to provide a critical piece of equipment. Which option contains the points that should be emphasised in the procurement strategy for this supplier-dependency situation?
Best answer: C
What this tests: Understand Resource, Scheduling and Optimisation in a Project
Explanation: Procurement strategy sets out how external resources will be obtained and managed. In a project that depends on one critical supplier, it should cover the sourcing approach, engagement timing, and how supplier dependency will be handled if performance problems arise.
Procurement strategy is the project’s high-level approach to securing goods or services from outside the organisation. When a project depends on one specialist supplier, the strategy should address when that supplier needs to be engaged, the approach to obtaining the required external resource, and how the project will manage dependency if the supplier delays or underperforms. These are procurement decisions because they shape how external supply is secured and controlled.
Daily task allocation for internal team members is different. That belongs to detailed resource planning or scheduling, not procurement strategy. The key distinction is between managing external supply arrangements and assigning internal work.
These points all relate to how an external supplier will be selected, engaged, and managed, which is the purpose of procurement strategy.
Topic: Understand Project Scope Management
In a typical project change-control process, a requested scope change is first assessed for impact. The next typical idea is to make a _____ to the person or group that will decide whether the change should proceed.
Best answer: D
What this tests: Understand Project Scope Management
Explanation: A typical change-control flow moves from assessment to recommendation, then decision, implementation, and closure. After analysing the impact of a change request, the project team usually recommends what should happen next to the appropriate decision-maker.
In project change control, the common ideas are assessment, recommendation, decision, implementation, and closure. Applied here, the change has already been assessed, so the next step is not to carry it out or close it. Instead, the assessed information is used to form a recommendation for the person or group with authority to decide whether the change should be approved, rejected, or deferred. Only after that decision would implementation happen, followed later by closure once the change record is completed. A nearby but different concept is configuration identification, which belongs to configuration management rather than this stage of change control.
After assessment, the usual next step is to recommend a course of action before a formal decision is made.
Topic: Understand Project Management Planning
Which term describes the identification, definition, planning, tracking and realisation of beneficial outcomes that help support a project’s justification?
Best answer: C
What this tests: Understand Project Management Planning
Explanation: Benefits management is the term for managing expected beneficial outcomes from a project. Those expected benefits are a key part of why the project is justified in the first place and why that justification may be reviewed during the project.
In APM PFQ, benefits management is concerned with identifying, defining, planning, tracking and realising the beneficial outcomes a project is expected to deliver. This links closely to project justification because a project should only proceed if it is expected to create worthwhile benefits for the organisation or its stakeholders. If the expected benefits are unclear, unrealistic or no longer achievable, the justification for continuing the project is weakened. The closest near-miss is the business case, which records and presents the justification, while benefits management focuses on the benefits themselves and how they will be achieved and reviewed.
Benefits management focuses on planning and tracking benefits so the project’s justification can be established and reviewed.
Topic: Understand Roles and Responsibilities within Projects
Which statements describe sponsor responsibilities on a project?
Best answer: C
What this tests: Understand Roles and Responsibilities within Projects
Explanation: The sponsor is the senior role that champions the project, owns its business justification, and supports major decisions. Managing daily activity and maintaining detailed schedules sit with the project manager, not the sponsor.
A sponsor is responsible for the project’s continued business justification and for giving senior-level direction and support. This means owning the business case and helping resolve major decisions or escalations. By contrast, the project manager is responsible for planning, coordinating, and controlling the day-to-day delivery work, including managing routine progress and maintaining detailed schedules.
In this question, the statements about owning the business case and providing senior direction fit the sponsor role. The statements about coordinating team work and maintaining the detailed schedule fit the project manager role.
A useful distinction is that the sponsor leads from the business perspective, while the project manager leads the delivery work.
The sponsor owns the business case and provides senior direction, while day-to-day coordination and schedule control are project manager responsibilities.
Topic: Understand Project Management Planning
For an office relocation project, the sponsor wants evidence that the move is worthwhile before approving it. The project manager is also preparing a document covering scope, schedule, risks and communications. Which statement best distinguishes these two documents?
Best answer: A
What this tests: Understand Project Management Planning
Explanation: The key distinction is purpose. A business case justifies the project by showing why it is needed and what benefits it should deliver, while the project management plan describes how the work will be organised, monitored and controlled.
In APM PFQ terms, the business case and the project management plan serve different purposes. The business case supports investment and approval decisions by explaining why the project should be done, what value or benefits are expected, and whether the project is viable. In the scenario, that is the document the sponsor needs before approving the office move.
The project management plan is different: it brings together how the project will be delivered and controlled. It typically covers areas such as scope, schedule, resources, risk, communication, and governance arrangements. In the scenario, the document being prepared by the project manager fits this purpose.
A simple way to remember the distinction is: business case = why, project management plan = how.
A business case justifies the project, while a project management plan sets out how delivery and control will be managed.
Topic: Understand Project Management and the Operating Environment
Before selecting detailed project responses or controls, the team can use _____ analysis to improve awareness of the operating environment.
Best answer: C
What this tests: Understand Project Management and the Operating Environment
Explanation: PESTLE analysis helps a project team understand its external operating environment at a high level. It is used early to build awareness of factors that may affect the project before more detailed responses, plans, or controls are chosen.
PESTLE is a framework for scanning the wider environment around a project. It looks at political, economic, social, technological, legal, and environmental factors that could influence the project. At PFQ level, its main value is awareness: it helps the team understand context and possible external influences before deciding detailed responses or controls.
This means PESTLE is not itself a schedule tool, a configuration activity, or a way to map individual stakeholders. It supports early understanding of the project environment so later decisions are better informed. A close distractor is stakeholder analysis, but that focuses on people and groups affected by the project rather than the broader external environment.
PESTLE analysis is used to scan the external operating environment before deciding specific project actions.
Topic: Understand Project Risk and Issue Management in Context
A project team is planning an office relocation. A furniture supplier warns that severe weather next month could delay delivery, but no delay has happened yet. Which term best describes this situation?
Best answer: B
What this tests: Understand Project Risk and Issue Management in Context
Explanation: This situation is a risk because the possible delay is uncertain and has not yet occurred. In PFQ terms, a risk is an uncertain event or set of circumstances that, if it happens, can affect project objectives.
A project risk is about uncertainty. The supplier has warned that bad weather might cause a delivery delay in the future, so the event is possible but not yet real. That matches the risk concept used in project management: something uncertain that could affect time, cost, scope, quality, or other objectives if it occurs.
An issue is different because it already exists and needs resolution now. Here, there is no actual delay yet, only the possibility of one. The key distinction is whether the problem has happened already or is still uncertain.
When the event becomes real, it would stop being treated only as a risk and would also need issue management.
It is an uncertain event that may affect the project in the future, so it is a risk.
Topic: Understand Project Risk and Issue Management in Context
What is the main purpose of the analysis stage in a typical project risk management process?
Best answer: A
What this tests: Understand Project Risk and Issue Management in Context
Explanation: The analysis stage is used to understand the significance of identified risks. It helps the project compare risks by considering factors such as likelihood and impact, so attention can be directed to the highest-priority risks.
In a typical risk management process, analysis happens after risks have been identified. Its purpose is to examine each risk so the project can judge how serious it is, commonly by considering likelihood and impact. This allows risks to be prioritised and supports informed decisions about where effort should be focused. Analysis does not mainly create the list of risks, define detailed responses, or deal with issues that have already happened. The key point is that analysis helps the team understand and rank uncertainty before choosing what action to take.
Analysis examines how likely risks are and what effect they could have so the project can focus on the most important ones.
Topic: Understand Resource, Scheduling and Optimisation in a Project
Which term describes adjusting activity dates to resolve resource over-allocation, even if this changes the planned completion date?
Best answer: B
What this tests: Understand Resource, Scheduling and Optimisation in a Project
Explanation: Resource levelling is a resource optimisation technique used when demand for resources exceeds availability. It adjusts activity timing to remove over-allocation, and unlike smoothing, it may change the completion date.
Resource levelling is used to deal with resource overload by rescheduling activities so the available people or equipment can complete the work. The key point is that the schedule is adjusted to match resource limits, even if that means the project finishes later than originally planned.
This differs from resource smoothing, which aims to improve resource use without moving the planned end date. Time boxing fixes the time available for work, and critical path analysis identifies the sequence of activities that determines project duration rather than redistributing resources.
The main clue is the option that allows the completion date to change in order to solve over-allocation.
Resource levelling resolves resource conflicts by changing the schedule, and this can move the project end date.
Topic: Understand Project Scope Management
Which PFQ concept is the formal process for assessing proposed changes, considering their impact, and deciding whether they should be approved before implementation?
Best answer: A
What this tests: Understand Project Scope Management
Explanation: Change control is specifically about managing requests to alter approved work or outputs. It ensures proposed changes are assessed for impact and formally decided before being implemented.
In PFQ, change control is the process used to manage proposed changes in a controlled way. It typically involves identifying the requested change, assessing its effect on areas such as scope, time, cost, and quality, and then deciding whether to approve, reject, or defer it. The key idea in the stem is that the change is only proposed and must be evaluated before action is taken.
This differs from related concepts because change control focuses on decision-making about alterations to the approved baseline or deliverables. A close distractor is configuration management, but that is mainly about identifying, recording, and controlling versions and status of project products, not deciding whether a proposed change should go ahead.
Change control is the process used to assess proposed changes, evaluate their effects, and approve or reject them before implementation.
Topic: Understand Quality in the Context of a Project
Decision gates are review points used to decide whether a project should ______.
Best answer: C
What this tests: Understand Quality in the Context of a Project
Explanation: Decision gates are formal review points, usually between stages, used to assess whether a project remains viable and should move forward. Their purpose is to support a decision to continue, change direction, or stop the project.
A decision gate is a formal review point used to decide whether a project should proceed. At this point, relevant information such as progress, continued justification, risk, and readiness for the next stage is reviewed. The outcome is typically a go, amend, or stop decision.
This is different from reviews that look back after delivery or checks that focus only on product defects. Decision gates are about controlling whether the project should continue based on current evidence. The key idea is that they help governance bodies decide if moving ahead is still justified.
Decision gates support go/no-go decisions on whether the project should proceed, change, or stop.
Topic: Understand Project Risk and Issue Management in Context
Why is project risk management described as proactive?
Best answer: A
What this tests: Understand Project Risk and Issue Management in Context
Explanation: Risk management is proactive because it focuses on uncertainty that may affect project objectives in the future. The aim is to identify, assess, and plan responses before the risk happens, not just react afterward.
In APM PFQ terms, a risk is an uncertain event or set of circumstances that could affect project objectives if it occurs. Risk management is therefore proactive because the team looks ahead, considers what might happen, and decides how to respond in advance. This helps reduce threats, increase opportunities, and improve control of the project.
By contrast, reacting only after something has happened is usually issue management. Once the event has already occurred, it is no longer a risk in the same sense; it has become a current problem or situation to manage. The key distinction is future uncertainty versus present reality.
Risk management is proactive because it addresses possible future events in advance, rather than waiting until they become actual problems.
Topic: Understand Resource, Scheduling and Optimisation in a Project
What is the main purpose of a milestone in a project schedule?
Best answer: A
What this tests: Understand Resource, Scheduling and Optimisation in a Project
Explanation: A milestone is used to highlight a key point in the schedule, such as a review, approval, or phase completion. It is not an activity that consumes time and effort, and it is not a deliverable that the project produces.
A milestone is a marker in the schedule that shows a significant event or point in time. Typical examples include stage completion, approval to proceed, contract award, or handover readiness. In PFQ terms, it helps track progress by showing important checkpoints.
An activity is different because it is work that takes time and usually uses resources. A deliverable is also different because it is the output or product created by the project work. So the purpose of a milestone is not to describe work or define output, but to identify an important point in the schedule. The option about assigning people relates more to responsibility or resource planning than to milestones.
A milestone is a schedule marker used to show an important event, decision, or completion point rather than work or output.
Topic: Understand Resource, Scheduling and Optimisation in a Project
What is the main purpose of critical path analysis in a project schedule?
Best answer: D
What this tests: Understand Resource, Scheduling and Optimisation in a Project
Explanation: Critical path analysis is a scheduling technique used to identify the sequence of activities that determines the earliest possible completion date. In PFQ, the focus is on its purpose, not on calculating float or path lengths.
Critical path analysis helps the project team understand which activities have the greatest effect on the project completion date. If one of these critical activities slips, the overall schedule is likely to slip as well. That is why its main purpose is to support schedule planning, monitoring, and control by highlighting the activities that directly drive the end date.
It is different from related concepts such as resource levelling, time boxing, and milestones. Those are useful scheduling ideas, but they do not describe the purpose of critical path analysis itself. The key takeaway is that PFQ tests what critical path analysis is for, rather than requiring detailed schedule calculations.
Critical path analysis is used to show which activities directly drive the project end date and therefore need close control.
Topic: Understand Resource, Scheduling and Optimisation in a Project
A milestone in a project schedule is a ____.
Best answer: A
What this tests: Understand Resource, Scheduling and Optimisation in a Project
Explanation: A milestone is a key point or event in the schedule used to mark progress. It is not work being performed and it is not a tangible output being produced.
A milestone is a significant point in time in a project schedule, such as approval being given or a phase being completed. It is used to show progress or a key event and usually has zero duration. By contrast, an activity is work that takes time and effort, and a deliverable is a product, result, or output that the project creates. The key distinction is that a milestone marks a point; it does not describe the work itself or the item being produced.
A useful check is:
The closest distractors confuse a schedule marker with either the work or the output.
A milestone marks progress at a specific point and typically has zero duration, unlike an activity or a deliverable.
Topic: Understand Project Management and the Operating Environment
Which situation is most suitable for managing through a project structure rather than business as usual?
Best answer: A
What this tests: Understand Project Management and the Operating Environment
Explanation: A project is used for temporary work that creates a specific change, product, or outcome. The office relocation has a defined objective and end point, so it fits a project structure rather than ongoing operational work.
A project structure is appropriate when work is temporary, has a clear objective, and is intended to deliver a defined change. In this case, relocating an office within five months is a one-off piece of work with a specific outcome and an end date. That is different from business as usual, which covers ongoing, repetitive activities needed to keep normal operations running.
The other situations are recurring operational tasks. Processing invoices, handling password resets, and carrying out regular stock checks are all routine activities that continue as part of normal service. The key distinction is temporary change delivery versus ongoing operational continuity.
A project structure suits temporary work that delivers a specific, defined change and then ends.
Topic: Understand Project Scope Management
A team is planning a digital form project. They agree that designing the form, user guidance, and testing are included in the project outputs, but ongoing helpdesk support after launch is excluded and will remain business as usual. Which concept is the team applying?
Best answer: B
What this tests: Understand Project Scope Management
Explanation: Scope management is about controlling what is inside and outside the project. In the scenario, the team is deciding which outputs and activities belong to the project and which will stay with business as usual.
Scope management defines and controls the boundaries of a project. It covers what work will be done, what outputs will be produced, and what is explicitly excluded. In this scenario, the team has decided that the form, user guidance, and testing are part of the project, while ongoing helpdesk support is not. That is a clear example of setting scope boundaries. This is different from changing an approved scope later, tracking versions of project items, or checking whether outputs meet quality standards. The key point is that scope management is about inclusion and exclusion of project work and outputs.
It is defining and controlling what work and outputs are included in the project and what is excluded.
Topic: Understand Project Risk and Issue Management in Context
Why should issue resolution be tracked to closure? Which option contains the correct set of reasons?
Best answer: D
What this tests: Understand Project Risk and Issue Management in Context
Explanation: Issue resolution is tracked to make sure actions are followed through until the issue is genuinely resolved and formally closed. It also provides visibility if progress stalls so further action or escalation can happen.
An issue already exists and is affecting, or could affect, the project now, so it needs active management until it is closed. Tracking issue resolution to closure helps the project team confirm that agreed actions have been carried out, check that those actions have actually resolved the problem, and see whether progress is delayed and needs escalation. This gives control and accountability, usually through an issue log or similar record.
Estimating probability is part of risk thinking, because risks are uncertain future events. An issue has already happened, so the focus is resolution, monitoring, and closure rather than probability assessment.
Tracking issue resolution ensures actions are completed, confirms the issue is actually resolved, and highlights when escalation is needed before closure.
Topic: Understand Project Management and the Operating Environment
Which option best states the key purpose of project management?
Best answer: D
What this tests: Understand Project Management and the Operating Environment
Explanation: Project management is concerned with applying the right methods, skills and control to deliver a project successfully. Its purpose is to achieve the project’s objectives, not to run ongoing operations or manage wider organisational investment choices.
In APM PFQ, project management is the application of processes, methods, knowledge, skills and experience to achieve project objectives. This focuses on controlling and directing the work so the project can be delivered successfully. The key idea is that project management is about managing a specific project from start to finish to achieve its defined objectives.
The closest distractors are broader organisational concepts. Coordinating related projects for strategic benefit is programme management, while selecting and prioritising projects is portfolio management.
Project management exists to direct and control the work needed to achieve the project’s objectives successfully.
Topic: Understand Project Management Planning
A project team identifies expected cost savings and service improvements, then checks whether those benefits still support the reason for investing in the project. Which PFQ concept best matches this activity?
Best answer: B
What this tests: Understand Project Management Planning
Explanation: Benefits management is concerned with identifying, planning, and reviewing the benefits a project is expected to deliver. Those expected benefits help show whether the project remains justified, because they support the reason for doing the project in the first place.
In PFQ terms, benefits management links what the project is expected to improve with why the project should be done. If the expected savings, service gains, or other benefits no longer support the original reason for investment, the project’s justification becomes weaker. This is why benefits management is closely connected to project justification.
The business case records and presents the justification, but benefits management provides key evidence for it by defining and reviewing the expected benefits. Success criteria are measures used to judge whether the project has succeeded, and stakeholder analysis looks at stakeholder interests and influence. The key idea here is that expected benefits help explain and maintain the reason for the project.
Benefits management identifies and reviews expected benefits so the project’s justification can be tested.
Topic: Understand Resource, Scheduling and Optimisation in a Project
Which statements correctly describe the purpose of milestones in a project schedule?
Select the option containing the correct set.
Best answer: B
What this tests: Understand Resource, Scheduling and Optimisation in a Project
Explanation: Milestones are markers in a schedule that identify significant points or events, such as phase completion, approvals, or key deliveries. They do not represent the duration of detailed work activities.
A milestone is a significant point or event in a project schedule. Its purpose is to show important moments that help track progress, such as the end of a phase, a formal approval, or the achievement of a key delivery event. Milestones make a schedule easier to monitor because they highlight notable points without adding detailed task information.
They are not used to show how long an activity takes. Unlike activities, milestones typically represent a point in time rather than work with duration. A useful way to remember this is that milestones mark progress and key events, while activities show the work needed to reach them.
The closest distractor is the statement about activity duration, which describes tasks, not milestones.
Milestones are used to mark significant points or events, not to show the duration of activities.
Topic: Understand Project Scope Management
A cost breakdown structure helps a project team control costs by ______.
Best answer: C
What this tests: Understand Project Scope Management
Explanation: A cost breakdown structure is used to organise and view project costs in a clear hierarchy. This helps the team understand where money is planned or spent and supports monitoring and control during the project.
A cost breakdown structure (CBS) groups project costs into a logical structure, usually linked to parts of the project or categories of expenditure. Its main value is that it makes costs easier to understand, track, and compare with the plan. When costs are structured clearly, the project team can see where spending is occurring, identify variances, and support better cost control decisions.
The other ideas belong to different project management tools. Responsibility assignment is about who does the work, sequencing is about scheduling, and defining products is about scope. A CBS focuses specifically on cost visibility and control.
A cost breakdown structure organises project costs by element, making them easier to understand, monitor, and control.
Topic: Understand Project Scope Management
In configuration management, identification is the activity that ______.
Best answer: A
What this tests: Understand Project Scope Management
Explanation: Identification in configuration management is about deciding what will be controlled and how it will be uniquely described. It creates clarity over configuration items and versions so later control, status reporting, and checking can happen consistently.
Configuration management helps keep control of a project’s products and related information. Identification is the activity that defines the configuration items and gives them clear names, references, and version details so everyone knows exactly what is being controlled. This may include documents, components, or other deliverables that need formal control.
Once items are identified, the project can then manage changes to them, record their current status, and confirm that the actual product matches the approved information. Without identification, later configuration activities become unreliable because people may not be referring to the same item or version. The closest distractors describe other configuration management activities, not identification itself.
Identification establishes what items are under configuration control and gives them unique references and version details.
Topic: Understand Project Scope Management
Which situation most clearly needs agreed change control rather than an informal team update?
Best answer: C
What this tests: Understand Project Scope Management
Explanation: Formal change control is needed when an agreed scope baseline may change. Adding new equipment on a linear project changes the approved scope, so it should be assessed and authorised rather than handled informally.
In PFQ terms, scope decisions need agreed control when they alter the approved scope baseline or the agreed deliverables. A linear project usually defines scope early, so adding new equipment after approval is a clear change request and should follow change control. That allows the project to assess effects on time, cost, resources, quality, and benefits before approval.
By contrast, some updates do not change approved scope. Reordering work within an iterative time box, correcting a typo, or breaking work into smaller tasks are usually delivery or planning adjustments rather than scope changes. The key test is whether the decision changes what the project has agreed to deliver, not just how the team organises the work.
Adding a new deliverable after the scope baseline has been agreed is a scope change that should go through formal change control.
Topic: Understand Project Risk and Issue Management in Context
A supplier has already missed a delivery date, and the delay is now affecting the project schedule. In APM PFQ terms, what is this?
Best answer: D
What this tests: Understand Project Risk and Issue Management in Context
Explanation: An issue is something that exists now or has already happened and is affecting the project. In this scenario, the missed delivery has already occurred and is impacting the schedule, so it is an issue rather than a risk.
In APM PFQ terms, a risk is an uncertain event or set of circumstances that may affect project objectives if it happens. An issue is different because it is current: it already exists or has already occurred and now needs managing or resolution. Here, the supplier has already missed the delivery date, and the effect on the schedule is already being felt. That means the uncertainty has passed, so the situation is no longer a risk. The key distinction is whether the event is still uncertain or is already happening.
It is an issue because it has already happened and is currently affecting the project.
Topic: Understand Project Management Planning
An internal change project is introducing a new HR system across five offices. The sponsor and project manager agree the rollout sequence, target dates and handover points, and the team will use this as the reference for deployment activity. Which concept does this describe?
Best answer: D
What this tests: Understand Project Management Planning
Explanation: The scenario describes an agreed reference for how rollout will happen, including sequence, dates and handover points. In PFQ terms, that is a deployment baseline, used to compare actual deployment activity against what was planned.
A deployment baseline is the agreed reference point for planned delivery or deployment activity. In this scenario, the rollout sequence, target dates and handover points have been agreed and will be used to monitor the HR system rollout. That makes it a deployment baseline.
A business case justifies why the project should be done. Stakeholder analysis identifies interested parties and their needs. A risk register records uncertain events that may affect the project. None of those provides the agreed reference for deployment activity.
The key clue is the phrase “used as the reference for deployment activity.”
A deployment baseline is the agreed reference used to compare and control planned delivery or deployment activity.
Topic: Understand Communication in the Context of a Project
A project manager finds that some stakeholders are receiving the wrong level of detail, while others are not being updated often enough. Which project artifact should set out who needs information, the format to use, and how often it should be shared?
Best answer: C
What this tests: Understand Communication in the Context of a Project
Explanation: The problem is about controlling project communications so the right people get the right information in the right way and at the right time. That is the purpose of a communication plan.
A communication plan is used to organise and control how information is shared in a project. It typically sets out who needs communication, what information they need, the format or method to use, and how often communication should happen. In this situation, stakeholders are getting unsuitable detail or insufficient updates, so the issue is best addressed by the communication plan.
A stakeholder analysis helps identify stakeholder interests and influence, but it does not by itself schedule and structure ongoing communications. A progress report is one communication output, not the plan for all communications. A risk register records risks and responses, so it does not control routine project information flows.
A communication plan defines the audience, method, format, timing, and frequency for project communications.
Topic: Understand Communication in the Context of a Project
A project team is split across three sites, and the travel budget is very limited. The project manager is considering a face-to-face workshop for the weekly progress update. Which disadvantage of face-to-face communication is most relevant here?
Best answer: A
What this tests: Understand Communication in the Context of a Project
Explanation: In this situation, the main drawback of face-to-face communication is the effort and cost of bringing people together. For a dispersed project team, arranging the same place and time can be impractical compared with virtual methods.
A key disadvantage of face-to-face communication in projects is that it usually requires participants to be available in the same place at the same time. When team members are spread across different sites, this can increase travel cost, take more time to organise, and delay communication. That matters most in the scenario because the team is geographically dispersed and the travel budget is limited.
Face-to-face communication does have strengths, such as allowing quick clarification, use of body language, and stronger relationship building. However, those are advantages, not disadvantages. In this case, the deciding factor is the difficulty and expense of arranging in-person contact.
Face-to-face communication often needs people to be in the same place at the same time, which can make it expensive and hard to coordinate.
Topic: Understand Project Management Planning
In project planning, the estimating funnel is used to show that estimate ranges usually ____ as the project progresses.
Best answer: A
What this tests: Understand Project Management Planning
Explanation: The estimating funnel shows how uncertainty changes over time. Early in a project, estimates are less certain and usually cover a wider range; as the project progresses and more information is available, that range normally narrows.
The core purpose of the estimating funnel is to represent uncertainty in estimates over the life of the project. At the start, limited information means estimates are broader and less precise. As planning and delivery continue, assumptions are tested and more detail becomes available, so the likely range for time or cost estimates usually narrows. The funnel therefore helps explain why early estimates should not be treated as exact figures. It shows a reduction in uncertainty over time, not the removal of uncertainty altogether.
The estimating funnel represents reducing uncertainty, so estimate ranges typically become narrower as more information is known.
Topic: Understand Communication in the Context of a Project
Which item would typically be included in a project communication plan?
Best answer: B
What this tests: Understand Communication in the Context of a Project
Explanation: A communication plan usually describes what information will be shared, who needs it, how it will be sent, and when. Its typical contents focus on managing project communication, not scope, risk, or scheduling details.
A project communication plan helps ensure the right people receive the right information in the right way at the right time. Typical contents include stakeholder or audience groups, their information requirements, communication methods such as meetings or email, timing or frequency, and sometimes responsibilities for sending or approving communications. In this question, the option about stakeholder information needs, methods, and frequency matches those normal contents.
The other options describe material that belongs mainly to different project management areas. A communication plan may refer to those areas, but it does not primarily define them.
A communication plan normally sets out who needs information, how it will be communicated, and how often.
Topic: Understand Communication in the Context of a Project
In a project communication plan, which term describes how responses to communications will be collected and used?
Best answer: D
What this tests: Understand Communication in the Context of a Project
Explanation: Feedback arrangements are the part of a communication plan that explain how two-way communication will work. They show how recipients can comment, ask questions, or confirm understanding so the project can adjust communications if needed.
A communication plan is not only about sending information; it should also support effective two-way communication. Feedback arrangements define how responses will be gathered, such as questions, comments, confirmations, or reactions from stakeholders, and how the project will use that information. This helps check whether messages were understood and whether communication needs to be changed. In this question, the focus is specifically on the planned way to receive and use responses, which is why feedback arrangements is the best match. The closest distractor is communication methods, but that refers to the channels used to send messages rather than the planned response process.
Feedback arrangements set out how recipients can respond to communications and how that feedback will be captured and acted on.
Topic: Understand Project Life Cycles
A project that uses defined phases for overall planning but develops part of the solution through repeated cycles is using a ______ life cycle.
Best answer: D
What this tests: Understand Project Life Cycles
Explanation: A hybrid life cycle is used when a project includes both linear and iterative features. In this statement, the overall work is planned in defined phases, while some development happens through repeated cycles, which matches hybrid.
A hybrid life cycle combines elements of more than one life cycle approach, most commonly linear planning with iterative development. In the statement, the project has defined phases for overall planning, which is a linear feature, but it also develops part of the solution through repeated cycles, which is an iterative feature. That combination is the key sign of a hybrid life cycle.
A purely linear life cycle would mainly progress through sequential phases without iterative development. A purely iterative life cycle would rely on repeated cycles as the main way of developing the solution. An extended life cycle refers to the wider life span around the project, such as before formal start or after handover, not the combination of delivery approaches within the project.
A hybrid life cycle combines linear planning features with iterative development features in the same project.
Topic: Understand Project Management and the Operating Environment
Programme management is the coordinated management of which of the following?
Which option contains the correct set?
Best answer: D
What this tests: Understand Project Management and the Operating Environment
Explanation: Programme management brings together related projects and associated change activities so they can be coordinated as one group. It does not mean managing unrelated business-as-usual work or the organisation’s entire portfolio.
The core idea of programme management is coordination across a group of related projects and the change activities needed to embed outcomes and realise benefits. It sits above individual projects, helping ensure the related work fits together and supports a shared objective. In contrast, business-as-usual operations are ongoing routine work, and portfolio management is concerned with selecting and overseeing the wider set of change investments across an organisation.
A useful check is:
The closest distractor is the one that includes the whole portfolio, because portfolio and programme are linked terms but they are not the same concept.
Programme management coordinates related projects and change activities, not unrelated operational work or the full organisational portfolio.
Topic: Understand Project Management Planning
A project manager is planning a digital service rollout. She identifies end users, suppliers, and department heads, assesses their level of interest and influence, and records how each should be engaged during the project.
Which concept does this describe?
Best answer: A
What this tests: Understand Project Management Planning
Explanation: The activity described is stakeholder analysis. It focuses on identifying stakeholders and understanding their interest, influence, and engagement needs so the project can plan effective involvement and communication.
Stakeholder analysis is a planning activity used to identify people or groups affected by the project, assess their interest and influence, and decide how they should be engaged. In this scenario, the project manager is mapping stakeholders and considering how to work with them, which is a clear example of stakeholder analysis.
Progress reporting is different because it communicates project status such as schedule, cost, or performance. Quality control is different because it checks whether deliverables meet requirements. Benefits management focuses on defining, tracking, and realising expected value from the project. The key distinction is that stakeholder analysis is about people and engagement, not status updates or product checking.
This is stakeholder analysis because it identifies stakeholders and assesses their interest, influence, and engagement needs.
Topic: Understand Quality in the Context of a Project
A project delivering a new internal HR portal holds a monthly review to check that agreed development standards and procedures are being followed so defects are prevented before testing. Which management area does this activity describe?
Best answer: B
What this tests: Understand Quality in the Context of a Project
Explanation: This activity is about preventing defects by reviewing whether the right processes and standards are being followed. In PFQ terms, that is quality assurance, not inspection of finished outputs.
Quality assurance is concerned with confidence that quality requirements will be met by using appropriate processes, standards, and procedures. In this scenario, the team is reviewing how work is being done each month so problems can be prevented before they appear in testing. That makes the focus process-based and preventative.
Quality control is different because it checks completed outputs to identify defects, for example through testing or inspection. Issue management would apply if a problem had already occurred and needed action. Change control would apply if the team were assessing a proposed change to approved baselines or scope. The key distinction is prevention through process review rather than detection after work is produced.
It focuses on checking that the project’s processes and standards are being applied to prevent defects.
Use the APM PFQ Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Use the full PM Mastery practice page above for the latest review links and practice route.