Fundamentals and Core Concepts
What this domain tests
Fundamentals questions check whether you can define terms precisely, distinguish related but different ideas, and reason from first principles rather than recall trivia. Expect vocabulary around systems, processes, components, interfaces, inputs and outputs, plus the basic lifecycle model that later domains build on.
Concepts to master
Know the difference between a standard, a policy, a procedure, and a guideline: a standard is a mandatory technical rule, a policy states management intent, a procedure is a step sequence, and a guideline is advisory. Understand functional vs non-functional requirements, synchronous vs asynchronous interaction, stateless vs stateful design, and coupling vs cohesion. Be fluent in the idea of a baseline - an approved, version-controlled reference point - and in traceability from requirement to test.
Traps in questions
The commonest trap is the plausible-but-wrong definition: an option that sounds authoritative but swaps two terms. Another is the absolute word - always, never, only - which usually marks a wrong answer unless the rule is genuinely absolute. A third is confusing the purpose of an artifact with its format.
Worked rule of thumb
When two answers both seem true, ask which one the question stem is actually asking about: what it is (definition), why it exists (purpose), or who does it (role). Match the verb in the stem to the verb in the option. If the stem says "best describes the purpose", an option beginning "defines the format of" is wrong even if factually accurate.
Study method
Build a one-page glossary in your own words and force yourself to write a counter-example for each term. Being able to say what a concept is not is the fastest defence against distractor options.