Close versioned requirement change impacts with feasible revalidation

A hands-on CBAP lab. You produce the real artefact and 10 automated checks verify it behaves the way the exam expects.

Try this labAll CBAP practice

Certification
CBAP
Format
Structured configuration
Difficulty
hard
Estimated time
50 min
Automated checks
10

The brief

Repair change-impact-closure.json. decisions:[{change,status,reason,authorityRef}] covers every proposal and respects mandatory/permitted/pending source facts. baseline:[{node,version,value}] retains all nine nodes, applies only permitted accepted direct values and increments the union-affected context versions once. impact:[{change,affected:[nodes],reviewUnits}] reports complete potential closure for all three proposals, including deferrals. work:[{id,method,start,duration,units,versions:[{node,version}]}] chooses unique source methods, preserves complete current coverage and actual method demand. Schedule after day1 within source half-open people calendars, without overlaps, and finish affected prerequisite reviews before dependent core/channel methods. Choose targeted earlier reviews, a longer lower-effort integrated suite or another feasible arrangement; accepted eligible scope changes coverage and shared version context. Deferred export never silently becomes full. report:{accepted:[change IDs],affected:[nodes],reviewed:[nodes],unreviewed:[nodes],finishDay,workUnits,potentialReviewUnits} must match actual source-derived closure; finish is null while incomplete. Fully close all affected current nodes before submission. boundary:{claim:conditional-change-impact-plan,approval:no-new-approval-asserted}. Independent row order may vary. Preserve partial progress, inspect consequences and repair a stale review or omitted dependant without Reset. This conditional plan creates no actual approval or execution evidence.

What the checks verify

Your work is graded on 10 independent properties, not on matching one reference answer.

  • Unique bounded change, baseline, impact and review records.
  • Every proposal respects current permission, mandatory scope and justified deferral.
  • Only current permitted accepted changes alter source scope values.
  • All proposed changes retain complete transitive source-dependent impacts.
  • Each union-affected node advances exactly once and unaffected versions are preserved.
  • Each method reviews its full supplied coverage at the actual current versions.
  • Actual source-method duration, effort and funded budget are retained.
  • Work follows baseline application, source availability, nonoverlap and prior revalidation.
  • Actual reviewed versions, remaining closure, finish and optimized effort reconcile.
  • A conditional source exercise creates no real approval or review execution.

Where this sits in the CBAP blueprint

Domain
Requirements Life Cycle Management
Objective
Assess Requirements Changes
Skill
Impact and Revalidation Closure

Part of CBAP preparation

Labs are written by ExamNova to teach the decisions the exam tests. They are not reproductions of vendor lab content.