Unverified Domain 1: Foundations and Core Concepts
What this domain tests
This domain checks whether you understand the vocabulary and framing ideas that the rest of the exam builds on. Questions tend to be conceptual rather than computational: recognizing definitions, distinguishing closely related terms, and applying a principle to a short scenario. Begin by mastering the distinction between process and outcome, between inputs and constraints, and between symptoms and root causes. Most items reward careful reading more than memorization.
Concepts to know cold
- Definitions in context. Learn each term with its purpose, not just its wording.
- Sequences. Many processes have a required order; knowing which step must precede another answers many items.
- Trade-offs. Recognize that most choices balance cost, speed, quality, and risk.
- Boundaries. Know what a given concept does not cover.
Traps to expect
- Absolute wording. Options using "always," "never," or "only" are often wrong unless the rule is genuinely unconditional.
- Near-synonyms. Two options may sound alike; one is the precise technical term and the other is colloquial.
- Right answer, wrong question. A true statement that does not respond to the stem is a distractor.
- Reversed relationships. Watch for cause and effect swapped, or a prerequisite stated backwards.
Worked example
A question asks which action should come first when a process is failing. Option A fixes the visible defect; Option B confirms the underlying cause; Option C documents the fix; Option D notifies stakeholders. The rule of thumb: diagnose before you act. B is correct because the others depend on knowing the cause. A treats a symptom, and C and D make sense only after the cause is known.
Rule of thumb
When two options both seem defensible, choose the one that is necessary rather than merely helpful, and the one that is specific to the stem rather than generically true.