CPRE FL · IREB · Process and Working Structure · Bank updated 2026-07-03
CPRE FL practice questions: Process and Working Structure
5 free questions from 12 on this area · answer and explanation for each · no sign-up
These 5 questions come from the Process and Working Structure section of our CPRE FL bank (12 questions on this area, which carries 7% of the real exam). Every question is original, with the correct answer explained and linked to the source it is drawn from.
1/5 · Process and Working Structure
A supplier organization performs requirements engineering twice for the same customer initiative: first to produce a coarse-grained specification for a fixed-price tender offer, and later—after the contract is awarded—to elaborate detailed requirements that directly guide the development team. Which facet of the RE process best explains why two distinct RE efforts, aimed at different addressees and levels of detail, are appropriate here?
AThe degree of iteration, because the post-contract RE effort is inherently more iterative than the pre-contract one.
BThe purpose facet, because the two RE efforts serve different purposes: negotiating a contract versus directly steering implementation.
CThe time facet, because the project has switched from continuous to one-time requirements engineering.
DThe target facet, because the kind of system being built has changed between the offer phase and the contract phase.
Show answer & explanation
2/5 · Process and Working Structure
A team develops safety-relevant embedded control software for a medical device under strict regulatory approval, where requirements must be fully specified, reviewed, and formally signed off before design work may begin, and late requirements changes are extremely costly to accommodate. Which working structure does this scenario most strongly favor, and why?
AAn iterative working structure, because frequent releases eliminate the need for requirements documentation.
BA linear (sequential) working structure, because regulatory sign-off and low tolerance for late change favor completing and baselining requirements before subsequent phases start.
CA linear working structure, because linear processes never produce formal requirements documentation.
DAn iterative working structure, because agile methods are always the preferred choice for safety-critical systems.
Show answer & explanation
3/5 · Process and Working Structure · hard
A Product Owner insists that a user story may only enter a sprint once it has a clear description, agreed acceptance criteria, and an estimate. Which foundation-level concept does this practice primarily represent, and how does it relate to the 'time' facet of the RE process?
AIt represents a Definition of Done acting as an acceptance gate; it reflects the time facet's one-time mode, since all requirements must be finalized before the project starts.
BIt represents a change-request process; it reflects the target facet, since it addresses which system components may change.
CIt represents a Definition of Ready acting as an entry gate; it reflects the time facet's continuous mode, since requirement detail is elaborated incrementally throughout the product's lifecycle rather than fixed once upfront.
DIt represents baselining, a purely linear-process concept that has no relation to the time facet.
Show answer & explanation
4/5 · Process and Working Structure · easy
The IREB CPRE Foundation Level syllabus describes requirements engineering as consisting of four core activities: elicitation, documentation, negotiation/validation and agreement, and management of requirements. Which statement correctly characterizes how these four activities relate to one another during a project?
AThey are performed iteratively and interleaved throughout the project; requirements engineers regularly return to earlier activities as new information or changes emerge.
BThey are executed exactly once, in a fixed order, and once negotiation is complete the team must never return to elicitation.
CEach of the four activities must be assigned to a different person to guarantee separation of duties.
DOnly documentation is mandatory; elicitation, negotiation, and management are optional refinements that can be skipped in most projects.
Show answer & explanation
A is correct. The IREB CPRE FL syllabus frames elicitation, documentation, negotiation/validation & agreement, and management as core RE activities that are performed iteratively and interleaved rather than as a single linear pass. As new stakeholder input, changes, or conflicts surface, requirements engineers routinely cycle back to earlier activities. Treating them as a rigid, one-time sequence or as separable optional tasks misrepresents the process model the syllabus teaches.
↗ the IREB CPRE Foundation Level Syllabus v3.3.0 — Process and Working Structure
5/5 · Process and Working Structure · hard
A requirements engineer is asked to justify why a project developing embedded software for an implantable medical device applies a far more formal, document-heavy RE process than a three-person startup building a mobile game. Which factor, as described in the IREB CPRE Foundation Level syllabus, most directly explains this difference?
AThe number of lines of code planned for the final system, since larger codebases always require more formal requirements documentation regardless of domain.
BThe personal preference of the requirements engineer, since the syllabus states that process formality is primarily a matter of individual working style rather than project context.
CThe degree of criticality of the system (e.g., safety, regulatory, or economic risk), which influences how rigorously requirements must be elicited, documented, and validated.
DThe programming language chosen for implementation, since languages with static typing inherently demand more detailed requirements specifications.
Show answer & explanation
C is correct. The IREB CPRE FL syllabus identifies context factors — such as the degree of criticality (safety, regulatory, or economic risk), applicable standards, and project characteristics — that determine how formally the RE process must be carried out. A safety-relevant medical device naturally demands stricter elicitation, documentation, and validation rigor than a low-risk mobile game. Attributing this difference to code size, programming language, or personal taste misrepresents the context-driven tailoring the syllabus teaches.
↗ the IREB CPRE Foundation Level Syllabus v3.3.0 — Process and Working Structure
Other CPRE FL areas
The same kind of free sample for every other section of the CPRE FL bank:
Study Process and Working Structure with instant feedback
6 free questions · filter study mode by area and difficulty · error log with spaced repetition · no card, no dumps, no ads.
Create your free account →
Read next
ECBA vs CCBA vs CBAP: Which IIBA Certification Fits Your Experience Level? (2026)
ECBA, CCBA or CBAP? The eligibility gate that picks for you, what the 2026 ECBA rewrite changed, and each credential's three-year cost, verified against IIBA.
PMI-PBA vs CBAP: The Business Analysis Certification Decision, Settled with Data
PMI-PBA ($405-555, 36 months of experience) vs CBAP ($495-650 all-in, 7,500 hours plus references): eligibility, exam mechanics, three-year cost, salary data.
ExamDeck is an independent study tool, not affiliated with, endorsed by, or sponsored by IREB. CPRE FL and related marks are trademarks of their respective owners, used for identification only. Exam facts checked against official IREB materials (as of August 2026); always confirm current details with the vendor before booking.