CAPM domain - 36% of the exam

Project Management Fundamentals and Core Concepts

Project Management Fundamentals and Core Concepts is 36% of the CAPM exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

97
Practice questions
4
Objectives
49
Easy
48
Medium

Where people go wrong

  • Confusing iterative with incremental delivery

    The wrong answers swap the two labels. Where one screen or dashboard is reworked from feedback until it is right, they offer incremental delivery; where login, then payments, then reporting ship as finished features, they offer iterative. Iterative work repeatedly refines a single evolving deliverable until it is correct. Incremental work delivers completed, usable functionality piece by piece, so customers receive working capability early.

    See it in a sample question
  • Labelling a mixed project with one approach

    When one stream is stable and another is uncertain, the wrong answers pick a single label for the whole project: predictive because the hardware is planned up front, adaptive because the software runs in short cycles, or iterative and incremental as a stand-in. Each ignores half of the scenario. A hybrid life cycle deliberately combines a predictive approach for fixed, well-understood work with an adaptive approach for work whose requirements are still evolving.

    See it in a sample question
  • Confusing a programme with a portfolio

    The wrong answers swap programme and portfolio, or collapse the grouping into one large project or into operations. A programme manages related projects together to obtain benefits that separate management would not deliver. A portfolio collects projects, programmes and operations to meet strategic objectives, and its components need not be related. Ongoing, repetitive work with no end date is operations, and a single temporary endeavour producing one unique result is a project.

    See it in a sample question
  • Swapping environmental factors and process assets

    The wrong answers reverse the two kinds of planning input. Regulations, market conditions and labour-market conditions sit outside the team's control and are enterprise environmental factors. Templates, lessons-learned repositories and approved procedures are organisational process assets, which the organisation owns and the team can reuse. Some wrong options file a reusable template as an environmental factor, or an external regulation as a process asset.

    See it in a sample question
  • Recording an assumption in the wrong artifact

    An unconfirmed belief, such as a vendor providing sandbox access or an API being available by a set date, is sent to the risk register, the stakeholder register or the charter. It belongs in the assumption log, which records assumptions and constraints so they can be tracked and validated. The risk register holds analysed uncertain events with probability, impact and responses, and the stakeholder register holds identities, interest and influence. The charter lists only high-level assumptions.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleProject Management Fundamentals and Core Conceptseasy

On the Meridian analytics platform, the team paints a rough version of the whole dashboard first, then repeats the work over several cycles, refining and improving that same product each time based on user feedback until it is polished. Which development approach does this describe?

  • AAn incremental approach, delivering a different finished feature slice at the end of each cycle
  • BAn iterative approach, repeating cycles that successively refine a single evolving product Correct
  • CA predictive approach, executing a single detailed plan produced before the work started
  • DA hybrid approach, running predictive and adaptive elements in parallel on the product
Iterative development repeats cycles to refine and improve one evolving product, unlike incremental delivery of separate finished pieces. Iteration improves the correctness of a single product through repeated passes that incorporate feedback, so the same deliverable becomes more complete and accurate each cycle rather than growing by discrete finished chunks.

Why A is wrong: Incremental delivery adds new completed pieces each cycle, but the scenario repeatedly refines one whole product rather than shipping separate finished slices, so this misreads the pattern.

Why B is correct: Iterative development revisits and improves the same product across repeated cycles to increase its correctness, which matches refining the whole dashboard over successive passes.

Why C is wrong: Predictive work follows one up-front plan through to completion, whereas the team here reworks the product across multiple feedback cycles, so it is not predictive.

Why D is wrong: Hybrid mixes distinct approaches for different parts of the work, but this scenario shows one consistent pattern of repeated refinement, so labelling it hybrid is inaccurate.

Free sampleProject Management Fundamentals and Core Conceptseasy

The Aventine ERP programme has two distinct streams: a hardware rollout with fixed, stable requirements suited to detailed up-front planning, and a customer-facing app whose features are uncertain and expected to evolve with user feedback. The sponsor wants each stream handled in the way that fits it best. Which development approach should the project manager select?

  • AA fully predictive approach applied uniformly to both the hardware and the app streams
  • BA hybrid approach, using predictive planning for the hardware and an adaptive approach for the app Correct
  • CA fully adaptive approach applied uniformly to both the hardware and the app streams
  • DA single incremental approach, releasing both hardware and app features together each cycle
A hybrid approach combines predictive and adaptive methods so each part of the work is delivered in the way that suits it. Hybrid development matches the approach to the nature of the work, applying predictive planning where requirements are stable and adaptive methods where requirements are uncertain, which is why it fits a programme with both kinds of stream.

Why A is wrong: A uniform predictive approach fits the stable hardware stream but forces rigid up-front planning onto the app stream, whose evolving features need room to change.

Why B is correct: A hybrid approach applies predictive methods to the stable hardware stream and adaptive methods to the uncertain app stream, matching each part of the work to the way it is best delivered.

Why C is wrong: A uniform adaptive approach suits the evolving app but adds needless iteration overhead to the hardware rollout, whose requirements are already fixed and well understood.

Why D is wrong: Forcing both streams into one incremental cadence ignores that the hardware requirements are fixed and do not benefit from cyclic release, so it does not fit either stream well.

Free sampleProject Management Fundamentals and Core Conceptseasy

At Meridian Health, three related projects, a patient portal, an online booking system, and a records migration, are being managed together so they deliver coordinated benefits that none of them could achieve on its own. Which term best describes this coordinated grouping?

  • AA portfolio, because it is a collection of projects selected and funded to meet the organisation's strategic goals.
  • BOperations, because the three initiatives will keep Meridian Health running smoothly once they are delivered.
  • CA program, because it groups related projects managed in a coordinated way to gain benefits not available separately. Correct
  • DA single large project, because the three efforts share resources and can be treated as one body of work.
Recognise a program as related projects managed together to deliver benefits unavailable from managing them separately. A program coordinates related projects to achieve benefits that individual projects could not deliver alone; the key signal is relatedness plus coordinated management for a combined benefit, which distinguishes it from a portfolio.

Why A is wrong: This is tempting because a portfolio also groups projects, but portfolio components need not be related; here the projects are deliberately related for shared benefit, which defines a program.

Why B is wrong: This is wrong because operations are ongoing repetitive work; three temporary, related delivery efforts managed together are not operational activity.

Why C is correct: Correct: a program is a group of related projects managed together to obtain benefits and control not available from managing them individually, which is exactly what is described.

Why D is wrong: This is tempting since the work is combined, but each effort is a distinct project with its own objectives; grouping several related projects is a program, not one project.

Free sampleProject Management Fundamentals and Core Conceptseasy

The Solstice Software team must revise its plan because of newly enacted national data-protection regulations and current labour-market conditions that neither the team nor its organisation can control. In project management terms, these external conditions are best described as what?

  • AEnterprise environmental factors, because they are conditions inside or outside the organisation that influence but are not controlled by the team. Correct
  • BOrganisational process assets, because they are inputs the team draws on when shaping the project plan.
  • CProject constraints logged in the scope baseline, because they place firm limits on what the team may deliver.
  • DProject deliverables, because complying with the regulations is one of the outputs the team must hand over.
Identify external regulations and market conditions beyond the team's control as enterprise environmental factors. Enterprise environmental factors are conditions, internal or external, that influence a project but lie outside the team's control, such as laws, regulations, and market conditions; that lack of control is what separates them from organisational process assets.

Why A is correct: Correct: enterprise environmental factors are conditions the project team does not control, such as legislation and market conditions, that nonetheless affect how the project is planned and executed.

Why B is wrong: This is tempting because both influence planning, but organisational process assets are the organisation's own reusable knowledge; regulations and market conditions are external and outside the team's control.

Why C is wrong: This is wrong because the scope baseline is an approved internal artefact; broad external regulations and market conditions are environmental factors, even if they later shape constraints.

Why D is wrong: This is tempting since compliance is required, but deliverables are things the team produces; the regulations themselves are external conditions, not project outputs.

Free sampleProject Management Fundamentals and Core Conceptsmedium

On the Coastal Ferry Booking project, the team assumes that the payment gateway vendor will provide sandbox access within two weeks, but this has not been confirmed. The project manager wants to record this belief so it can be tracked and validated later. In which artifact should it be documented?

  • AThe risk register, because any unconfirmed belief is by definition an identified project risk
  • BThe stakeholder register, because the vendor is an external party whose commitments are logged there
  • CThe project charter, because high-level assumptions and constraints are captured there at initiation
  • DThe assumption log, because it captures assumptions and constraints for later validation and tracking Correct
Identify the assumption log as the artifact for recording and tracking assumptions and constraints across the project. An assumption is a factor considered true without proof; the assumption log exists to hold these so they can be validated later, distinguishing it from the risk register which holds analysed uncertain events.

Why A is wrong: Tempting because an unvalidated assumption can become a risk, but until it is analysed as an uncertain event with a probability and impact it is recorded as an assumption, not entered directly in the risk register.

Why B is wrong: Tempting because the vendor is a stakeholder, but the register records stakeholder identity, interest, and influence, not the project's working assumptions about their behaviour.

Why C is wrong: Tempting because the charter does list high-level assumptions at initiation, but a specific, evolving delivery assumption raised during planning belongs in the assumption log that carries it forward.

Why D is correct: Correct. The assumption log is the artifact created to record assumptions and constraints throughout the project so they can be tracked, revisited, and validated as work progresses.

Other domains in this exam

See also the CAPM cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by PMI. Original, blueprint-aligned practice material only.