Try 10 focused CAPM questions on Project Management Fundamentals and Core Concepts, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | CAPM |
| Topic area | Project Management Fundamentals and Core Concepts |
| Blueprint weight | 36% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate Project Management Fundamentals and Core Concepts for CAPM. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 36% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.
These questions are original PM Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.
Topic: Project Management Fundamentals and Core Concepts
A department head asks you to “kick off a project” to replace the current customer portal because “it’s outdated.” No problem statement, expected benefits, or success measures are provided, and several teams will need to change how they handle customer requests.
What should you ask for first before recommending how to proceed?
Best answer: D
What this tests: Project Management Fundamentals and Core Concepts
Explanation: Projects are temporary efforts undertaken to create outcomes that deliver organizational value, often by enabling change in processes, roles, or technology. Before deciding on a life cycle or next steps, you must confirm the intended value (benefits) and how it will be evaluated. Without that, the work can’t be aligned to strategy or judged as successful.
A core reason organizations charter projects is to realize benefits—such as increased revenue, lower costs, improved customer experience, or risk reduction—by implementing change. In this scenario, the request is framed as “outdated,” but the value case is unclear and multiple teams will be impacted, which signals a change effort. The first clarification should establish the target outcomes and measures (often documented in a business case or charter), so the team can align scope, approach (predictive/agile/hybrid), and governance to the value being sought.
Once benefits and success measures are known, you can then elicit requirements/features, plan resources, and build an appropriate schedule that supports the desired change and benefits realization. The key takeaway is that project decisions should be anchored to value delivery, not initial solution ideas.
Projects deliver value by enabling organizational change, so the intended benefits and success measures must be clear before selecting an approach.
Topic: Project Management Fundamentals and Core Concepts
A project coordinator notices recurring rework because different team members interpret stakeholder requests differently. In requirements workshops, the coordinator restates what the stakeholder said in their own words, asks specific follow-up questions, and confirms the stakeholder agrees before documenting the requirement.
Which approach is the coordinator primarily using to reduce ambiguity and rework?
Best answer: A
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The described behavior is active listening: the coordinator paraphrases, probes with clarifying questions, and confirms shared understanding before writing requirements. This directly reduces ambiguity at the source and prevents downstream rework caused by assumptions or misinterpretation.
Active listening is a communication technique used to ensure accurate understanding before decisions or documentation are made. In the scenario, the coordinator reduces ambiguity by reflecting back what was heard (paraphrasing), asking targeted clarifying questions to fill gaps, and gaining explicit confirmation from the stakeholder.
This is especially effective during requirements discovery because it:
The key takeaway is that preventing rework often starts with confirming understanding, not with formal control processes after misunderstandings occur.
Paraphrasing, asking follow-ups, and confirming understanding are core active listening behaviors that prevent misinterpretation early.
Topic: Project Management Fundamentals and Core Concepts
During a schedule review for a predictive project, the sponsor points to an entry labeled “Design sign-off” that has a duration of 0 days. The entry represents a formal approval point used to track progress, and no work is performed during the entry itself.
What is this schedule entry best described as?
Best answer: A
What this tests: Project Management Fundamentals and Core Concepts
Explanation: A milestone is a significant point or event in the project, typically shown with zero duration in the schedule. Because “Design sign-off” represents an approval checkpoint where no work occurs, it fits the definition of a milestone. Activities involve performing work, while durations and due dates describe time aspects of that work.
A milestone is a meaningful point in time (such as an approval, decision, or phase end) used to monitor progress; it is commonly represented in a schedule with zero duration because it is not work. An activity is work that must be performed to produce a deliverable, so it has effort and a duration. A task duration is the length of time an activity is planned to take (for example, 5 days). A due date is a calendar deadline by which an activity or deliverable must be finished, regardless of its duration. Here, “Design sign-off” is explicitly a formal approval checkpoint with 0 days, so it is a milestone, not work or a time attribute.
It is a zero-duration checkpoint that marks a significant event (approval) rather than work.
Topic: Project Management Fundamentals and Core Concepts
A predictive project team reports that all work packages are complete and the solution has been deployed. However, the sponsor refuses to authorize project closure and the operations manager will not take ownership, stating there is no training, support documentation, or agreed go-live acceptance sign-off. The project manager cannot find any documented acceptance criteria or transition/handover plan in the project files.
What is the most likely underlying cause of this situation?
Best answer: B
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The core problem is missing project closure planning. If acceptance criteria, formal acceptance steps, and the handover/transition activities are not defined and executed, the sponsor has no basis to sign off and operations has no readiness path to assume ownership. This prevents legitimate closure even if the team believes the work is “done.”
Project closure is more than finishing tasks; it requires confirming acceptance, transferring ownership, and capturing learning. In this scenario, the sponsor is explicitly asking for go-live acceptance sign-off and operations is explicitly rejecting ownership due to missing training and support documentation. Those clues point to an absence of planned closure activities, such as documented acceptance criteria and an agreed transition/handover approach.
In a predictive environment, closure planning typically ensures:
The key takeaway is that “deployed” does not equal “accepted and transitioned,” so the project cannot be properly closed.
Without planned acceptance criteria and a transition/handover approach, stakeholders cannot formally accept or take over the deliverable.
Topic: Project Management Fundamentals and Core Concepts
In a predictive project schedule, which statement best describes a milestone?
Best answer: C
What this tests: Project Management Fundamentals and Core Concepts
Explanation: A milestone represents a key event or decision point in the schedule, such as completing a phase or receiving an approval. It is shown as occurring at a point in time and therefore has zero duration. Activities, durations, and due dates describe work, how long work takes, or when work must be completed.
A milestone is a scheduled point that signifies a significant event, achievement, or decision (for example, “Design approved” or “Phase 1 complete”). Because it represents a point in time rather than work to be performed, it is modeled with zero duration.
By contrast:
The key distinction is that milestones mark progress points, while activities and their durations describe the work and time needed to reach those points.
A milestone marks an important point (e.g., approval or completion) and is not planned with work effort or duration.
Topic: Project Management Fundamentals and Core Concepts
A project manager is asked how the team will decide which cost estimating technique to use, what units of measure and level of precision will be applied, how cost performance will be monitored, and what thresholds will trigger corrective action.
Which project artifact best describes this information and guides cost estimating and cost control?
Best answer: D
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The cost management plan explains the rules and procedures for planning and managing project costs. It sets the standards for estimating (such as units, precision, and allowable techniques) and for controlling costs (such as how performance is measured and what thresholds require action). This makes it the key artifact that guides both cost estimating and cost control.
A cost management plan is the component of the project management plan that documents how cost estimates will be created and how cost performance will be managed and controlled. In the scenario, the manager needs a single place that defines the estimating approach (for example, units of measure, level of accuracy/precision, and how estimates are refined) and the control approach (for example, how cost performance is monitored and what variance thresholds trigger corrective action or escalation). This guidance ensures costs are estimated consistently and that the team has an agreed method for measuring and responding to cost deviations throughout the project life cycle.
It defines how costs will be estimated, budgeted, managed, monitored, and controlled, including units, precision, reporting, and control thresholds.
Topic: Project Management Fundamentals and Core Concepts
On a software enhancement project, two senior developers repeatedly clash in planning meetings about the best design approach. The project manager ends each discussion by saying, “Let’s stay positive and move on—we can revisit this later,” and assigns both developers separate tasks without requiring a design decision. Over the next two iterations, rework increases and the team stops raising concerns in meetings. There is no immediate deadline pressure from the sponsor.
What is the most likely underlying cause of the team’s worsening conflict?
Best answer: D
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The key clue is the project manager repeatedly defers the discussion (“move on” and “revisit later”) and assigns work without resolving the disagreement. That behavior is avoidance (often paired with superficial smoothing), which prevents the team from addressing the real issues and leads to rework and reduced psychological safety. With no urgent deadline pressure, a collaborative approach is the appropriate way to resolve the conflict.
Conflict resolution techniques should be chosen based on context, and the project manager’s behavior is a strong indicator of which technique is being used. In the scenario, the project manager repeatedly shuts down the discussion, postpones decisions, and splits work to bypass the disagreement. This is avoidance (and a form of smoothing), which may reduce tension temporarily but does not resolve the underlying problem, so it often resurfaces as rework, frustration, and silence in meetings.
With no immediate sponsor deadline pressure, the better approach would be to facilitate collaboration (problem-solving) so the developers can evaluate options, agree on criteria, and make a decision the team can support. The root cause here is not the mere existence of disagreement, but the failure to address it directly and constructively.
Deferring the decision and moving on is avoidance, which leaves root issues unresolved and drives rework and disengagement.
Topic: Project Management Fundamentals and Core Concepts
You are developing the schedule management plan for a predictive project with fixed reporting dates to the sponsor. The team asks what this plan is used for before building the detailed project schedule.
Which TWO statements best describe the purpose of the schedule management plan and how it guides schedule development and control? (Select TWO)
Correct answers: C, F
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The schedule management plan is a component of the project management plan that defines how the schedule will be developed, monitored, and controlled. It provides the rules, standards, and processes (such as methodology, reporting, thresholds, and change control) that guide building the schedule and managing variance against the schedule baseline.
The schedule management plan sets expectations and decision rules for schedule work across the project. Before the team creates the detailed schedule, this plan defines the scheduling approach (for example, scheduling method and tool, units of measure, level of accuracy, and reporting formats) so the schedule is built consistently. It also defines how schedule performance will be controlled (for example, variance thresholds, status and forecasting cadence, and how changes to the schedule baseline are reviewed and approved via integrated change control).
Key takeaway: the plan describes the “how” of scheduling and control; the detailed schedule contains the specific activities and dates.
A schedule management plan establishes the standards and approach the team will use to create and communicate the schedule.
It explains how schedule performance is monitored and how the schedule baseline will be controlled through change control.
Topic: Project Management Fundamentals and Core Concepts
A project coordinator is asked to update stakeholder information after a kickoff meeting. The sponsor says a local operations manager is “highly influential” and is worried about business disruption, but the manager has not been listed in any project documents yet. The project manager wants a reliable way to capture the manager’s influence, interests, and preferred engagement approach before planning communications.
What is the best next step?
Best answer: D
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The immediate need is to formally identify and analyze the newly surfaced stakeholder so the team can plan appropriate engagement. The stakeholder register is used to document key stakeholders, their influence and interests, and any engagement or communication requirements that will drive later planning. Capturing this information first prevents premature communication actions based on incomplete analysis.
When a previously unlisted stakeholder is identified—especially one described as highly influential with clear concerns—the next step is to update the stakeholder register. This register captures who the stakeholder is and the analysis needed to manage them effectively, such as their level of influence/power, interests (e.g., disruption concerns), and engagement needs or preferences. That information becomes an input to subsequent plans (like the communications management plan) and helps the project team choose appropriate engagement strategies early, before misunderstandings or resistance grow. Escalation and issue logging can be useful later, but they do not replace the foundational step of documenting the stakeholder and their engagement requirements.
Key takeaway: document first in the stakeholder register, then plan and execute communications/engagement.
The stakeholder register is the primary place to document stakeholders along with influence, interests, and engagement requirements.
Topic: Project Management Fundamentals and Core Concepts
You are managing a predictive project to roll out new point-of-sale software to 40 stores. Midway through execution, the Operations director emails you asking to add an offline mode, saying it is “mandatory,” while the Finance manager replies that no additional funding will be approved. Before you decide whether to proceed, what should you clarify first?
Best answer: D
What this tests: Project Management Fundamentals and Core Concepts
Explanation: The situation contains conflicting direction, so the first step is to determine which stakeholder role has legitimate decision authority over scope and funding. Stakeholder influence depends on their power and accountability (for example, sponsor or designated change approval body). Once authority is clear, you can evaluate impacts and route the request appropriately.
When stakeholders give competing instructions, the project manager should not treat the loudest voice as the decision-maker. First, clarify stakeholder roles and influence: who is accountable for project funding and who is authorized to approve changes to scope, schedule, and cost (often the project sponsor and/or a defined change control authority). In this scenario, Operations is asserting a requirement while Finance is constraining funding; the correct next move is to confirm who has final approval rights and the escalation path. After that, you can gather estimates, document the change request, and facilitate a decision consistent with governance and stakeholder influence. The key takeaway is to verify decision authority before analyzing or committing to change work.
You must confirm the key stakeholder decision authority (typically the sponsor/change control authority) before acting on conflicting requests.
Use the CAPM Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Read the CAPM guide on PMExams.com, then return to PM Mastery for timed practice.