Foundations and Core Concepts
What foundational items actually test
Foundations questions rarely ask you to recite a definition. They ask you to recognise which concept a scenario illustrates and to separate concepts that sound alike. Build a personal glossary around four clusters: the core vocabulary of the discipline (inputs, processes, outputs, outcomes, impacts); the lifecycle model that organises work from initiation through closure; the division of roles between the practitioner, the client or sponsor, and oversight functions; and the governing principles - evidence-based practice, systems thinking, and continuous improvement - that resurface in every later domain.
Know why each model exists
A lifecycle model, a maturity model, and a process framework are not interchangeable. The first sequences work, the second describes capability levels, the third prescribes activities. Distractor options frequently borrow a plausible term from the wrong category, so ask yourself which question the term answers: when, how capable, or what to do?
Traps
- Absolutist wording ("always", "never", "only") attached to an otherwise attractive option.
- Options describing a late-stage activity when the stem is asking about foundations.
- "Common practice" answers that quietly contradict a stated principle.
- Two defensible options - prefer the one naming the concept the stem describes, not the one that merely sounds sophisticated.
Rule of thumb
Name it before you answer it: silently label the concept in the stem ("this is a roles question", "this is a lifecycle question"), then eliminate any option that would be correct under a different label.
Worked example
A stem describes a team that has finished building a deliverable and is now confirming it meets agreed criteria. The tempting answer is "design", because something was built. But the stem's operative verb is confirm, not create, so the activity is verification against requirements - an acceptance/closure activity.