200-901 Infrastructure and Automation Practice Question
In a CI/CD pipeline for network automation, a change is rolled back using a Git revert commit that triggers a new pipeline. The rollback playbook fails because the 'previous' configuration snapshot is missing. What should be implemented to prevent this?
⚠ Common exam trap
The trap is assuming that a Git revert of the playbook code is sufficient for rollback; candidates often overlook that the actual device configuration state must also be versioned and retrievable, not just the automation code.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Store configuration backups in a version-controlled repository before each change
Storing configuration backups in a version-controlled repository before each change ensures that a known-good 'previous' snapshot is always available for rollback, even if the Git revert commit only reverts the playbook code and not the device configuration. In CI/CD for network automation, the pipeline must have access to the exact prior state to restore it; version-controlled backups provide an immutable, auditable history that can be checked out by commit hash. This directly prevents the failure described, where the rollback playbook cannot find the previous configuration snapshot.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a single source of truth like NetBox
Why it's wrong here
NetBox inventories intended device state, not historical configuration snapshots, so a revert still finds nothing to restore. It is tempting because a source of truth prevents configuration drift, and it would be correct for reconciling desired state against live devices — but the stem needs versioned snapshots retained per pipeline run.
- ✓
Store configuration backups in a version-controlled repository before each change
Why this is correct
A revert commit restores the previous configuration, but only if that snapshot was captured beforehand. Committing configuration backups to a version-controlled repository before each change guarantees the prior state exists and can be reapplied by the rollback pipeline.
- ✗
Use the 'check mode' only
Why it's wrong here
Check mode only simulates changes and reports what would happen; it neither stores nor restores configuration snapshots. It is tempting because it validates playbooks safely, but preventing rollback failure requires versioned configuration backups retrievable by commit, not a dry-run flag.
- ✗
Disable rollback pipelines
Why it's wrong here
Disabling rollback pipelines removes the recovery path entirely, so a failed change can never be reversed and the missing snapshot problem is hidden rather than solved. It appeals as a way to stop repeated pipeline failures, and would suit environments where changes are immutable and forward-fixed only.
Go deeper
Related to this question
About these practice questions
Courseiva writes every 200-901 question from scratch — 975 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Cisco exam blueprint
This 200-901 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-901 exam.