Skip to main content
CertRampLearning

IREB · Free practice questions

IREB CPRE Foundation Level Practice Questions

30 original CPRE Foundation Level practice questions across all seven chapters of IREB syllabus 3.3.0, with more questions for the larger chapters 3, 4 and 6. Each one comes with the answer, a short explanation and the reason every other option is wrong.

Written for the syllabus 3.3.0 (1 April 2026) · Updated November 9, 2026 · Übungsfragen auf Deutsch

These are original practice questions written by CertRamp to the official IREB exam outline. They are not real exam questions and do not come from any exam. Try each question first, then open the answer to see the explanation for every option.

Domain 1

Introduction and Overview of Requirements Engineering

EO 1.1.2 Understand the different kinds of requirementsFoundationDomain: Introduction and Overview of Requirements Engineering

Question 1. "The system shall display the search results within two seconds for 95% of all queries." Which kind of requirement is this?

  1. Option A: Quality requirement
  2. Option B: Functional requirement
  3. Option C: Constraint
  4. Option D: Glossary entry
Show answer and explanation

Correct answer: A. Quality requirement

IREB distinguishes functional requirements, quality requirements and constraints. Response times, availability, security and usability are typical quality requirements.

  • A (correct)Correct. The statement describes a quality, here performance, that the system shall have.
  • B (incorrect)A functional requirement describes a result or behaviour the system provides, such as performing the search itself, not how fast it happens.
  • C (incorrect)A constraint restricts the solution space beyond what is needed for functional and quality requirements, for example a mandated technology or law.
  • D (incorrect)A glossary defines terms; this is a requirement.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 1.4.1 Know the major tasks of REFoundationDomain: Introduction and Overview of Requirements Engineering

Question 2. Which list names the major tasks of requirements engineering according to the CPRE syllabus?

  1. Option A: Design, implementation, testing, deployment
  2. Option B: Planning, budgeting, staffing, controlling
  3. Option C: Coding, reviewing, merging, releasing
  4. Option D: Elicitation, documentation, validation, management
Show answer and explanation

Correct answer: D. Elicitation, documentation, validation, management

Elicitation, documentation, validation and management are the major RE tasks. The syllabus stresses that there is no single RE process: it has to be tailored to the context.

  • A (incorrect)These are development activities, not the RE tasks.
  • B (incorrect)These are project management activities.
  • C (incorrect)These are software engineering activities.
  • D (correct)Correct. These are the four major RE tasks; the RE process must be tailored to perform them in a given situation.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 1.2.2 Enumerate symptoms of inadequate REFoundationDomain: Introduction and Overview of Requirements Engineering

Question 3. In a project retrospective, the team lists several observations. Which one is a typical symptom of inadequate requirements engineering, rather than a cause, according to the CPRE syllabus?

  1. Option A: The team started building right away to meet the deadline.
  2. Option B: Nobody on the team had received any RE training.
  3. Option C: After implementation, requirements turned out to be missing, unclear or wrong.
  4. Option D: Everyone assumed the requirements were self-evident.
Show answer and explanation

Correct answer: C. After implementation, requirements turned out to be missing, unclear or wrong.

The syllabus names missing, unclear and incorrect requirements as typical symptoms of inadequate RE. Typical causes are rushing into building, communication problems, assuming the requirements are self-evident, and inadequate RE education and skills.

  • A (incorrect)Rushing into building is named as a cause of inadequate RE, not as its symptom.
  • B (incorrect)Inadequate RE education and skills are a cause of poor RE, not a symptom.
  • C (correct)Correct. Missing, unclear and incorrect requirements are the typical symptoms of inadequate RE.
  • D (incorrect)Assuming that requirements are self-evident is a cause of inadequate RE, not a symptom.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

Domain 2

Fundamental Principles of Requirements Engineering

EO 2.1.1 Enumerate the principles of REFoundationDomain: Fundamental Principles of Requirements Engineering

Question 4. Which of the following is NOT one of the nine principles of requirements engineering in the CPRE syllabus?

  1. Option A: Value-orientation
  2. Option B: Shared understanding
  3. Option C: Completeness before implementation
  4. Option D: Systematic and disciplined work
Show answer and explanation

Correct answer: C. Completeness before implementation

The nine principles are value-orientation, stakeholders, shared understanding, context, problem, requirement, solution, validation, evolution, innovation, and systematic and disciplined work.

  • A (incorrect)This is principle 1: requirements are a means to an end, not an end in themselves.
  • B (incorrect)This is principle 3.
  • C (correct)Correct. This is not a principle. Requirements evolve (principle 7), and complete up-front specification is not required.
  • D (incorrect)This is principle 9.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 4.1.1 Determine the boundaries of the system to focus on the relevant requirementsIntermediateDomain: Fundamental Principles of Requirements Engineering

Question 5. In a project for an online shop, the payment provider's system will not be changed but provides an interface the shop uses. How is the payment provider's system classified?

  1. Option A: Inside the system boundary
  2. Option B: Part of the system context, between the system boundary and the context boundary
  3. Option C: Outside the context boundary (irrelevant environment)
  4. Option D: A stakeholder
Show answer and explanation

Correct answer: B. Part of the system context, between the system boundary and the context boundary

The system boundary separates the system from its context; the context boundary separates the RE-relevant part of the environment from the rest of the world. External systems the system interacts with lie between the two.

  • A (incorrect)Inside the system boundary are the parts that can be changed within the project; the payment system cannot.
  • B (correct)Correct. It is relevant to the system and interacts with it, but it is outside the system and cannot be changed in the project.
  • C (incorrect)It is relevant because the shop interacts with it, so it belongs to the context.
  • D (incorrect)A stakeholder is a person or organisation who influences the requirements or is impacted by the system. The question asks about the provider's system, which is a context element, not a stakeholder.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 2.2.2 Explain the principles and the reasons why they are importantIntermediateDomain: Fundamental Principles of Requirements Engineering

Question 6. In the first meeting, the head of sales says: "We need a mobile app for our field staff." Following the principle that problem, requirement and solution are intertwined, what should the Requirements Engineer do first?

  1. Option A: Explore which problem the app is meant to solve, for example what field staff cannot do today
  2. Option B: Document "mobile app" as a constraint and start specifying the screens
  3. Option C: Reject the request, because solutions must never be discussed in RE
  4. Option D: Ask the developers which app framework they prefer
Show answer and explanation

Correct answer: A. Explore which problem the app is meant to solve, for example what field staff cannot do today

Principle 5 states that problem, requirement and solution form an inevitably intertwined triple. When a stakeholder names a solution, the Requirements Engineer works back to the problem and the requirements behind it before committing to that solution.

  • A (correct)Correct. Stakeholders often express their wishes as solutions. Uncovering the underlying problem and the actual requirements also leaves room for better solutions.
  • B (incorrect)This takes the proposed solution for granted without understanding the problem behind it.
  • C (incorrect)Solutions are not forbidden in RE. The principle says that problems, requirements and solutions cannot be fully separated.
  • D (incorrect)Choosing a technology is a design decision and does not help to understand the problem.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 2.2.2 Explain the principles and the reasons why they are importantIntermediateDomain: Fundamental Principles of Requirements Engineering

Question 7. A team lead says: "Our job in RE is to write down exactly what the stakeholders ask for, nothing more." Which principle of RE does this attitude neglect most?

  1. Option A: Validation
  2. Option B: Systematic and disciplined work
  3. Option C: Context
  4. Option D: Innovation
Show answer and explanation

Correct answer: D. Innovation

Principle 8 (innovation) reminds you that giving stakeholders only what they ask for rarely creates outstanding systems. RE should also aim for innovative ideas, which is why design and idea-generating techniques belong to the elicitation toolbox.

  • A (incorrect)Validation checks whether requirements meet the stakeholders' needs. The statement does not argue against validating.
  • B (incorrect)This principle concerns using suitable processes and practices. The statement is about the scope of what RE delivers, not about method.
  • C (incorrect)The context principle says requirements cannot be understood in isolation. The statement does not deny the context.
  • D (correct)Correct. The innovation principle says that more of the same is not enough: good RE also looks for new ideas that can delight stakeholders, not only their explicit wishes.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

Domain 3

Work Products and Documentation Practices

EO 3.3.2 Specify an individual requirement and a user story using a phrase templateFoundationDomain: Work Products and Documentation Practices

Question 8. Which statement follows the user story template described by Cohn?

  1. Option A: The system shall export reports as PDF.
  2. Option B: When the user clicks Export, the system shall create a PDF.
  3. Option C: As a sales manager, I want to export reports as PDF so that I can send them to customers.
  4. Option D: Export: PDF, priority high, owner: sales.
Show answer and explanation

Correct answer: C. As a sales manager, I want to export reports as PDF so that I can send them to customers.

Phrase templates in the syllabus include EARS and the template by Rupp for individual requirements, and Cohn's template for user stories. Form templates are used for use cases.

  • A (incorrect)This is a classic 'shall' requirement, not a user story.
  • B (incorrect)This follows an EARS-like event-driven pattern, not the user story template.
  • C (correct)Correct. Role, goal and benefit: As a <role>, I want <requirement> so that <benefit>.
  • D (incorrect)These are attributes, not a user story.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 3.8.1 Know quality criteria for single requirementsIntermediateDomain: Work Products and Documentation Practices

Question 9. "The app shall be fast and user-friendly." Which quality criterion for single requirements is most clearly violated?

  1. Option A: Verifiable (and unambiguous)
  2. Option B: Traceable
  3. Option C: Non-redundant
  4. Option D: Conformant
Show answer and explanation

Correct answer: A. Verifiable (and unambiguous)

Quality criteria for single requirements: adequate, necessary, unambiguous, complete (self-contained), understandable, verifiable. Criteria for work products: consistent, non-redundant, complete (no known relevant requirements missing), modifiable, traceable, conformant.

  • A (correct)Correct. 'Fast' and 'user-friendly' cannot be checked objectively and can be understood differently by different readers.
  • B (incorrect)Traceability is a quality criterion for work products as a whole, not the main problem of this single sentence.
  • C (incorrect)Redundancy concerns repeated content across a work product; nothing is repeated here.
  • D (incorrect)Conformance to a structure or template is a work product criterion; the main issue here is vague wording.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 3.4.4 Understand how to select an appropriate model type for specifying requirements in a given situationIntermediateDomain: Work Products and Documentation Practices

Question 10. You want to specify the steps of a business process, including decisions and steps that run in parallel. Which model type is most suitable?

  1. Option A: UML class diagram
  2. Option B: Context diagram
  3. Option C: Glossary
  4. Option D: UML activity diagram
Show answer and explanation

Correct answer: D. UML activity diagram

Match the model to the aspect: structure and data → class diagram; function and flow → activity or process model; state and behaviour → state machine; context → context diagram.

  • A (incorrect)Class diagrams specify data and the objects in a domain with their relationships, not process steps.
  • B (incorrect)A context diagram shows the system in its environment and the interfaces, not the internal process flow.
  • C (incorrect)A glossary defines terms; it is not a model of a process.
  • D (correct)Correct. Activity diagrams model functions and business processes with actions, decisions and parallel flows.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 3.2.2 Explain the rules for writing good natural-language-based requirementsIntermediateDomain: Work Products and Documentation Practices

Question 11. "The order is checked and released." Which rule for writing natural-language requirements does this statement mainly break?

  1. Option A: Use universal quantifiers such as "all" or "never" with care
  2. Option B: Use passive voice with care
  3. Option C: Write short sentences
  4. Option D: Use nominalisations with care
Show answer and explanation

Correct answer: B. Use passive voice with care

The syllabus asks for short, well-structured sentences and defined terms, avoiding vague wording and incomplete descriptions, and using passive voice, universal quantifiers and nominalisations with care. Rewriting in active voice, for example "The system shall check…", makes the actor explicit.

  • A (incorrect)The statement contains no universal quantifier.
  • B (correct)Correct. The passive voice hides who performs the action: it is unclear whether the system, a clerk or a supervisor checks and releases the order.
  • C (incorrect)The sentence is already short.
  • D (incorrect)The sentence uses verbs, not nominalisations such as "the checking". Its main problem is the missing actor.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 3.5.1 Explain the purpose of glossaries and how to create oneIntermediateDomain: Work Products and Documentation Practices

Question 12. In a project, "customer" means a contract partner for the sales team but any registered app user for the IT team. How should this be handled?

  1. Option A: Leave the term out of the glossary, because everyone knows the word
  2. Option B: Let each team keep its own glossary with its own definition
  3. Option C: Agree on definitions with the stakeholders, resolve the homonym, for example with separate terms, and make the glossary binding
  4. Option D: Define the term only in comments in the source code
Show answer and explanation

Correct answer: C. Agree on definitions with the stakeholders, resolve the homonym, for example with separate terms, and make the glossary binding

A glossary defines the terms of the domain so that all stakeholders understand them the same way. Manage it centrally with a clear owner, agree on terms with the stakeholders, make it accessible and mandatory, mark synonyms and avoid or mark homonyms.

  • A (incorrect)Everyday words with context-specific meanings are exactly what a glossary needs to clarify.
  • B (incorrect)Separate glossaries keep the misunderstanding alive. A glossary should be managed centrally for the whole project.
  • C (correct)Correct. The glossary creates shared understanding when terms are agreed with stakeholders, homonyms are avoided or marked, and its use is mandatory.
  • D (incorrect)Code comments are not accessible to all stakeholders and are not a glossary.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 3.7.1 Know different kinds of prototypes and what they are used forFoundationDomain: Work Products and Documentation Practices

Question 13. Early in a project, you want to discuss the rough screen layout of a new app with users in a workshop, using quick sketches that are thrown away afterwards. Which kind of prototype fits best?

  1. Option A: Wireframe (low-fidelity exploratory prototype)
  2. Option B: Native prototype
  3. Option C: Evolutionary prototype
  4. Option D: Pilot system
Show answer and explanation

Correct answer: A. Wireframe (low-fidelity exploratory prototype)

Exploratory prototypes are discarded after use and come as wireframes (low fidelity), mock-ups (medium fidelity) or native prototypes (high fidelity). Evolutionary prototypes, or pilot systems, grow into the final system.

  • A (correct)Correct. Wireframes are quick, low-fidelity sketches used to explore and discuss ideas, and they are discarded after use.
  • B (incorrect)Native prototypes are high-fidelity prototypes built with the target technology, far too costly for discussing rough layout ideas.
  • C (incorrect)An evolutionary prototype is developed further into the final system; it is not thrown away.
  • D (incorrect)A pilot system is an evolutionary prototype that forms the core of the real system, not a quick sketch.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

Domain 4

Practices for Requirements Elaboration

EO 4.2.1 Understand how the Kano model can help to elicit the right requirementsIntermediateDomain: Practices for Requirements Elaboration

Question 14. Customers of a banking app take it for granted that they can see their account balance. They would never mention it, but would be very dissatisfied without it. In the Kano model, this is a…

  1. Option A: Delighter
  2. Option B: Dissatisfier
  3. Option C: Satisfier
  4. Option D: Constraint
Show answer and explanation

Correct answer: B. Dissatisfier

The Kano model helps you find requirements stakeholders will not mention: gathering techniques help elicit satisfiers and dissatisfiers, while design and idea-generating techniques often lead to delighters.

  • A (incorrect)Delighters are unexpected features that create enthusiasm; their absence does not cause dissatisfaction.
  • B (correct)Correct. Dissatisfiers (subconscious requirements, basic factors) are taken for granted, so stakeholders rarely mention them, but missing them causes strong dissatisfaction.
  • C (incorrect)Satisfiers (conscious requirements, performance factors) are explicitly demanded; the more of them, the higher the satisfaction.
  • D (incorrect)This is a category of requirements, not a Kano category.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 4.2.3 Understand how to choose a proper elicitation technique for a given situationIntermediateDomain: Practices for Requirements Elaboration

Question 15. Warehouse staff have performed their picking process for years. They find it hard to explain the details because many steps have become routine. Which elicitation approach is most suitable?

  1. Option A: A questionnaire sent by email
  2. Option B: Brainstorming new features
  3. Option C: Observation of the staff at work
  4. Option D: Reading the marketing brochure
Show answer and explanation

Correct answer: C. Observation of the staff at work

The syllabus groups gathering techniques into questioning, collaboration, observation and artifact-based techniques. Observation is a good fit when stakeholders cannot easily put routine, implicit knowledge into words.

  • A (incorrect)Questionnaires capture what people can articulate; routine, implicit knowledge is often missed.
  • B (incorrect)Brainstorming generates new ideas; it does not reveal how the current process actually works.
  • C (correct)Correct. Observation techniques reveal implicit, routine knowledge that people cannot easily put into words.
  • D (incorrect)Brochures rarely describe the real operational process.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 4.4.2 Remember the four important aspects for requirements validationAdvancedDomain: Practices for Requirements Elaboration

Question 16. Which of the following is one of the four important aspects of requirements validation in the CPRE syllabus?

  1. Option A: Separating the identification of defects from their correction
  2. Option B: Validating only once, at the end of the project
  3. Option C: Letting the author validate their own requirements alone
  4. Option D: Validating only from the developer's point of view
Show answer and explanation

Correct answer: A. Separating the identification of defects from their correction

The four aspects are: involving the right stakeholders, separating the identification and correction of defects, validating from different views, and repeated validation.

  • A (correct)Correct. Finding defects and fixing them are separate activities, so validation stays focused and thorough.
  • B (incorrect)The syllabus calls for repeated validation, not a single check at the end.
  • C (incorrect)Validation should involve the right stakeholders and different views, not only the author.
  • D (incorrect)Validation should take different views into account.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 4.1.2 Remember the relevant sources for the system to be createdFoundationDomain: Practices for Requirements Elaboration

Question 17. A team is replacing a legacy claims system. Which approach makes use of all three types of requirements sources named in the CPRE syllabus?

  1. Option A: Interviewing as many claims handlers as possible
  2. Option B: Reading the relevant regulations and process descriptions
  3. Option C: Analysing the screens and functions of the legacy system
  4. Option D: Combining stakeholders, documents such as regulations, and existing systems such as the legacy system
Show answer and explanation

Correct answer: D. Combining stakeholders, documents such as regulations, and existing systems such as the legacy system

The syllabus names three types of requirements sources: stakeholders, documents and systems. Laws, standards and process documents as well as existing or legacy systems often reveal requirements that stakeholders forget to mention.

  • A (incorrect)This uses only one type of source: stakeholders.
  • B (incorrect)This uses only documents as a source.
  • C (incorrect)This uses only systems as a source.
  • D (correct)Correct. Stakeholders, documents and systems are the three types of requirements sources.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 4.2.2 Understand the difference between gathering techniques, and design and idea-generating techniquesIntermediateDomain: Practices for Requirements Elaboration

Question 18. A product team wants new feature ideas that could delight the users of a fitness app. Which of these is a design and idea-generating technique rather than a gathering technique?

  1. Option A: A structured interview with existing users
  2. Option B: The analogy technique, transferring ideas from another domain such as gaming
  3. Option C: Field observation of users at the gym
  4. Option D: Analysis of existing app store reviews
Show answer and explanation

Correct answer: B. The analogy technique, transferring ideas from another domain such as gaming

Gathering techniques (questioning, collaboration, observation and artifact-based techniques) collect what stakeholders know or do. Design and idea-generating techniques such as brainstorming, analogies, prototyping, scenarios and storyboards create new ideas and often lead to delighters.

  • A (incorrect)Interviews are questioning techniques and belong to the gathering techniques.
  • B (correct)Correct. Analogies create new ideas by transferring concepts from another domain, which is typical of design and idea-generating techniques.
  • C (incorrect)Field observation is an observation technique and belongs to the gathering techniques.
  • D (incorrect)Analysing existing documents is an artifact-based technique and belongs to the gathering techniques.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 4.3.1 Remember the different types of conflictIntermediateDomain: Practices for Requirements Elaboration

Question 19. Two department heads disagree about the required capacity of a new booking system. One cites 2,000 bookings per day from last year's report, the other 5,000 from a market forecast. Which type of conflict is this primarily?

  1. Option A: Value conflict
  2. Option B: Relationship conflict
  3. Option C: Data conflict
  4. Option D: Structural conflict
Show answer and explanation

Correct answer: C. Data conflict

The syllabus distinguishes subject matter, data, interest, value, relationship and structural conflicts. Knowing the type helps you choose a resolution: data conflicts can often be resolved by clarifying the facts and agreeing on a reliable source.

  • A (incorrect)Value conflicts arise from different beliefs or principles, such as privacy versus transparency. Here the disagreement is about figures.
  • B (incorrect)Relationship conflicts stem from personal tensions or negative experiences between people, which are not described here.
  • C (correct)Correct. The parties rely on different information and sources, which is typical of a data conflict.
  • D (incorrect)Structural conflicts are caused by structures such as hierarchies, responsibilities or the distribution of resources and power.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 4.3.3 Understand how to apply appropriate conflict resolution techniquesAdvancedDomain: Practices for Requirements Elaboration

Question 20. Accountants want the invoice screen to show all details, while field staff want a minimal view on their phones. Both needs are legitimate, and the budget allows building both. Which conflict resolution technique fits best?

  1. Option A: Definition of variants
  2. Option B: Overruling
  3. Option C: Voting
  4. Option D: Compromise
Show answer and explanation

Correct answer: A. Definition of variants

The main conflict resolution techniques are agreement, compromise, voting, overruling and definition of variants, supported by consider-all-facts, plus-minus-interesting and the decision matrix. Variants suit situations where different needs can coexist at acceptable cost.

  • A (correct)Correct. Both needs can coexist, for example as role-specific views, and the effort is acceptable.
  • B (incorrect)Letting a higher authority decide is unnecessary here and would leave one group dissatisfied.
  • C (incorrect)A vote leaves the minority dissatisfied, although both needs could be served.
  • D (incorrect)A middle-ground screen would satisfy neither group fully, although both can be satisfied completely.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

Domain 5

Process and Working Structure

EO 5.3.3 For simple settings, select and apply an appropriate RE process configurationAdvancedDomain: Process and Working Structure

Question 21. A company develops a product for an anonymous mass market, works iteratively and explores the requirements step by step. Which RE process configuration fits best?

  1. Option A: Contractual RE process
  2. Option B: Participatory RE process
  3. Option C: No RE process is needed
  4. Option D: Product-oriented RE process
Show answer and explanation

Correct answer: D. Product-oriented RE process

The facets time (linear/iterative), purpose (prescriptive/explorative) and target (customer-specific/market-oriented) lead to typical configurations: participatory, contractual and product-oriented.

  • A (incorrect)Contractual configurations suit customer-specific development where a specification forms the basis of a contract.
  • B (incorrect)Participatory configurations suit customer-specific development with close, continuous collaboration with known stakeholders.
  • C (incorrect)Every development needs RE; only its configuration differs.
  • D (correct)Correct. A market-oriented, iterative and explorative setting points to a product-oriented configuration.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 5.1.2 Understand how and why these factors are influencingIntermediateDomain: Process and Working Structure

Question 22. A team specifies the software for an infusion pump, a safety-critical medical device that must be approved by an authority. How do these influencing factors most likely affect the RE process?

  1. Option A: RE can be skipped because the authority defines all requirements
  2. Option B: Requirements should only be discussed verbally to stay flexible
  3. Option C: Criticality has no influence; only time and budget matter
  4. Option D: Requirements need to be more explicit and thoroughly documented and validated
Show answer and explanation

Correct answer: D. Requirements need to be more explicit and thoroughly documented and validated

Factors that influence an RE process include the overall development process, the development context, stakeholder capability and availability, shared understanding, complexity and criticality, constraints, time and budget, volatility and experience. Safety-critical, regulated systems push the process towards explicit, prescriptive documentation.

  • A (incorrect)Regulations add constraints, but they do not define all requirements of the system.
  • B (incorrect)High criticality and approval demand documented, verifiable requirements, not only conversations.
  • C (incorrect)System criticality and constraints are among the important factors that influence an RE process.
  • D (correct)Correct. High criticality and regulatory constraints call for a more prescriptive process with carefully documented and validated requirements.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 5.3.2 Understand the steps for configuring an RE processFoundationDomain: Process and Working Structure

Question 23. You are configuring the RE process for a new project. According to the CPRE syllabus, what is the first step?

  1. Option A: Select the appropriate practices
  2. Option B: Analyse the influencing factors
  3. Option C: Determine the work products
  4. Option D: Assess the facet criteria
Show answer and explanation

Correct answer: B. Analyse the influencing factors

The steps are: analyse the influencing factors, assess the facet criteria (time, purpose, target), configure the process, determine the work products and select appropriate practices.

  • A (incorrect)Selecting practices is the last step, once the configuration and the work products are clear.
  • B (correct)Correct. The influencing factors come first, because they determine how the facets are assessed.
  • C (incorrect)The work products are determined after the process has been configured.
  • D (incorrect)Assessing the facets is the second step and is based on the influencing factors.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

Domain 6

Management Practices for Requirements

EO 6.6.1 Name reasons for requirements traceabilityFoundationDomain: Management Practices for Requirements

Question 24. A law changes, and the team must quickly find out which requirements, design elements and test cases are affected. Which practice makes this possible?

  1. Option A: Prioritisation
  2. Option B: Traceability
  3. Option C: Versioning only
  4. Option D: A glossary
Show answer and explanation

Correct answer: B. Traceability

Backward traceability to the origin (here the law) and forward traceability to design and tests let you assess the impact of a change. Explicit traces can be documented as links, matrices, tables or graphs.

  • A (incorrect)Prioritisation ranks requirements; it does not show what is affected by a change.
  • B (correct)Correct. Traceability links requirements to their origin and to later work products, which enables impact analysis.
  • C (incorrect)Versions show how a requirement changed, but not which other work products depend on it.
  • D (incorrect)A glossary defines terms, not dependencies between work products.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 6.4.1 Know the use of requirements configurations and baselinesIntermediateDomain: Management Practices for Requirements

Question 25. Before a release, the team freezes a stable, approved set of requirements in specific versions as the basis for planning and contracts. What is this called?

  1. Option A: A view
  2. Option B: A baseline
  3. Option C: An attribute
  4. Option D: A persona
Show answer and explanation

Correct answer: B. A baseline

A requirements configuration is a consistent set of work products that contain requirements; a baseline is a stable, change-controlled configuration that serves as a reference, for example for release planning.

  • A (incorrect)Views show selected or aggregated parts of the requirements; they do not freeze an approved state.
  • B (correct)Correct. A baseline is a stable, change-controlled configuration of work products, used for example for release planning or other delivery milestones.
  • C (incorrect)Attributes describe properties of individual requirements, such as status or priority.
  • D (incorrect)Personas describe fictional stakeholder types.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 6.7.1 Know how to handle changes in linear and agile approachesIntermediateDomain: Management Practices for Requirements

Question 26. In an agile project, who typically decides how a requested change to the requirements is handled?

  1. Option A: A Change Control Board that meets monthly
  2. Option B: Each developer individually
  3. Option C: Nobody: requirements cannot change in agile projects
  4. Option D: The product owner, by updating and reprioritising the backlog
Show answer and explanation

Correct answer: D. The product owner, by updating and reprioritising the backlog

The syllabus contrasts change handling: Change Control Boards with defined procedures in linear approaches, and backlog management by the product owner in agile approaches.

  • A (incorrect)A formal Change Control Board is typical of linear, plan-driven approaches.
  • B (incorrect)Uncoordinated changes by individual developers are not a change management approach.
  • C (incorrect)Agile approaches explicitly embrace change.
  • D (correct)Correct. In agile approaches, changes are handled through the backlog, which the product owner maintains and prioritises.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 6.8.2 Name steps to prioritize requirementsIntermediateDomain: Management Practices for Requirements

Question 27. A product owner wants to rank 60 backlog items for the next release and immediately asks the team to vote on them. Which step of prioritisation has been skipped?

  1. Option A: Archiving all low-priority requirements
  2. Option B: Creating a baseline of all 60 items
  3. Option C: Defining the assessment criteria, such as business value, urgency, effort or dependencies
  4. Option D: Writing test cases for all items
Show answer and explanation

Correct answer: C. Defining the assessment criteria, such as business value, urgency, effort or dependencies

The steps are: define the goals and constraints, define the assessment criteria, identify the stakeholders and the requirements to be prioritised, select a technique and perform the prioritisation. Prioritisation techniques fall into ad-hoc and analytical categories.

  • A (incorrect)Archiving is not a step of prioritisation.
  • B (incorrect)A baseline is a stable configuration for planning, not a step of prioritisation.
  • C (correct)Correct. Without agreed criteria, the ranking reflects personal preferences instead of the project's goals.
  • D (incorrect)Writing test cases is not part of prioritisation.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 6.5.3 Explain the purpose of views and name the different views of requirementsIntermediateDomain: Management Practices for Requirements

Question 28. A tester wants to see only the requirements that are assigned to release 2.1 and have the status "approved". All attributes may remain visible. Which kind of view is this?

  1. Option A: Selective view
  2. Option B: Projective view
  3. Option C: Aggregating view
  4. Option D: Baseline
Show answer and explanation

Correct answer: A. Selective view

Views show the parts of the requirements a specific reader needs. Selective views filter requirements, projective views show only selected attributes, and aggregating views summarise; most reports combine these kinds.

  • A (correct)Correct. A selective view shows only the requirements that meet given criteria, here release and status.
  • B (incorrect)A projective view shows only certain attributes or information of the requirements; here all attributes stay visible.
  • C (incorrect)An aggregating view condenses information, for example the number of requirements per status.
  • D (incorrect)A baseline is a stable, change-controlled configuration, not a view.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

Domain 7

Tool Support

EO 7.2.1 Explain what to consider when introducing RE toolsFoundationDomain: Tool Support

Question 29. Which approach is most advisable when introducing a new requirements management tool in an organisation?

  1. Option A: Clarify the RE process and needs first, consider all costs and try the tool in a pilot before broad rollout
  2. Option B: Buy the tool with the most features and roll it out to everyone at once
  3. Option C: Let each team choose its own tool without coordination
  4. Option D: Introduce the tool first and define the process later
Show answer and explanation

Correct answer: A. Clarify the RE process and needs first, consider all costs and try the tool in a pilot before broad rollout

When introducing RE tools, think about the process the tool should support, the full costs, training, a step-by-step introduction and evaluating the tool in practice.

  • A (correct)Correct. A tool should support a defined process; costs beyond licences (training, administration) and a pilot reduce the risk of a bad fit.
  • B (incorrect)Feature count does not guarantee fit, and a big-bang rollout without preparation is risky.
  • C (incorrect)This undermines shared work products, traceability and reporting.
  • D (incorrect)A tool cannot fix an undefined process; the process should come first.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

EO 7.1.1 Know the different types of RE toolsFoundationDomain: Tool Support

Question 30. A team needs a tool to manage requirement attributes, versions and configurations, trace links and change requests. Which type of RE tool covers these tasks?

  1. Option A: A tool for managing the RE process, such as measuring and reporting on process quality
  2. Option B: A requirements management tool
  3. Option C: A test automation framework
  4. Option D: A tool for documenting requirements knowledge, such as a modelling or collaboration tool
Show answer and explanation

Correct answer: B. A requirements management tool

The syllabus distinguishes tools for managing requirements, tools for managing the RE process and tools for documenting knowledge about requirements. Tools support RE work but do not replace a defined process.

  • A (incorrect)RE process management tools support workflows and measurement of the process, not the requirements themselves.
  • B (correct)Correct. Requirements management tools support attributes, prioritisation, versions and configurations, traceability and change management.
  • C (incorrect)Test automation supports testing, not the management of requirements.
  • D (incorrect)These tools support documenting requirements and building shared understanding, not managing attributes, versions and trace links.

Reference: IREB: CPRE Foundation Level syllabus 3.3.0 (opens in a new tab)

Want more practice?

30 questions are a sample. The exam is Approx. 45 items.

The full CertRamp IREB CPRE Foundation Level practice exams have 270 questions in 6 tests that grow with you, from a diagnostic start to an exam-level Test 4 and a challenge set beyond the exam, with an explanation for every option.

Who writes the exams

Written by a practitioner, not a question mill

Joshua Ravnjak, founder of CertRamp Learning

Joshua Ravnjak

Senior Consultant, digital transformation and AI

Founder, CertRamp Learning

921 learners and 61 reviews on Udemy (as of November 3, 2026)

I have more than 12 years of professional experience and work as a senior consultant in an IT management consultancy, focusing on digital transformation, AI and requirements engineering in the insurance industry. I have earned many certifications myself, so I know what exam preparation feels like. That is why every CertRamp practice exam follows the same progression: an easy start to see where you stand, then real exam level, then beyond it. You walk into the exam with a buffer and a good feeling.

Selected certifications

  • IREB® CPRE Foundation Level
  • ITIL® 4 Foundation
  • Professional Scrum Master I (PSM I)
  • Professional Scrum Product Owner I (PSPO I)
  • Certified SAFe® 6 Scrum Master
  • Certified AI-Empowered SAFe® 6 Product Owner/Product Manager

Plus further certifications from Microsoft and Anthropic (Claude).

ITIL® is a registered trademark of PeopleCert. IREB® is a registered trademark of IREB e.V. SAFe® is a registered trademark of Scaled Agile, Inc. PSM and PSPO are trademarks of Scrum.org.

Also in print

Cover: CPRE Foundation Level Prüfungsvorbereitung 2026 by Joshua Ravnjak

CPRE Foundation Level Prüfungsvorbereitung 2026

6 Übungsprüfungen mit 270 Fragen und ausführlichen Erklärungen

Paperback, German, October 2026

Prefer paper? The same progressive approach is available as a book (in German) with six practice exams and 270 questions.

View on Amazon (opens in a new tab)