Skip to content

Exam Tips (Syllabus v3.3.0)

Official References

About the Exam

DetailValue
Duration75 minutes (90 minutes for non-native speakers)
Questions45
Total points70
Passing score70% (49 of 70 points)
Question typesA-type (single-select), P-type (pick-two), K-type (true/false matrix)
Allowed aidsNone (closed book)
Languages12+ (English, German, French, Chinese, Spanish, etc.)

Question Types

A-type (Single-Select)

Pick 1 correct answer from 4 options. Worth 1 point.

P-type (Pick-Two)

Pick exactly 2 correct answers from 5 options. Worth 1-2 points. The number of correct answers is always stated in the question.

K-type (True/False Matrix)

Decide whether each of 4 statements is true or false. Worth 2 points. All 4 must be correct to earn any points — there is no partial credit.

Question Weighting by Educational Unit

Educational UnitQuestionsPointsWeight
EU 1 — Introduction and Overview345.7%
EU 2 — Fundamental Principles468.6%
EU 3 — Work Products and Documentation183042.9%
EU 4 — Practices for Elaboration101420.0%
EU 5 — Process and Working Structure234.3%
EU 6 — Management Practices61014.3%
EU 7 — Tool Support234.3%

EU 3 (Work Products and Documentation) carries the most weight — focus your study there.

Key Strategies

Read the Question Carefully

  • Watch for qualifiers like "always", "never", "can", "must", "NOT" — they change the meaning
  • For P-type questions, the number of correct answers is stated (e.g., "select two")
  • For K-type questions, read each statement independently

Know the IREB Definitions

The exam uses the syllabus definitions, which may differ from informal usage:

  • Requirement = a condition or capability needed by a stakeholder, that must be met by a system
  • Stakeholder = a person or organization that influences or is impacted by the system's requirements
  • Work product = a recorded intermediate or final result generated in a work process

Distinguish Similar Concepts

Common traps:

  • Validation vs. verification — validation checks against stakeholder intentions; verification checks against specification
  • System context vs. system boundary — context is the relevant environment; boundary separates system from context
  • Linear vs. iterative — process facets, not lifecycle models
  • Gathering vs. design techniques — gathering elicits known requirements; design techniques generate innovative ideas

K-type Strategy

K-type questions are all-or-nothing (2 points). If you are unsure about one statement, you risk losing 2 points. Focus on the statements you are most confident about first, then reason through the uncertain ones.

Time Management

  • 45 questions in 75 minutes = ~1 minute 40 seconds per question
  • Flag difficult questions and return to them — do not get stuck
  • K-type questions may take longer (4 sub-decisions each)
  • A-type questions should be the fastest

The Nine Principles — Quick Reference

These are examined in EU 2 and often appear as context for questions in other EUs:

  1. Value orientation — requirements are a means to an end
  2. Stakeholders — RE is about satisfying their desires and needs
  3. Shared understanding — explicit and implicit forms
  4. Context — systems cannot be understood in isolation
  5. Problem – Requirement – Solution — an intertwined triple
  6. Validation — non-validated requirements are useless
  7. Evolution — changing requirements are normal
  8. Innovation — more of the same is not enough
  9. Systematic and disciplined work — adapt to the situation

Study guide for IREB CPRE Foundation Level exam preparation.