200-901 Infrastructure and Automation Practice Question
A DevOps engineer is implementing Infrastructure as Code (IaC) for network devices. Which of the following practices is most critical to ensure that the environment state matches the desired configuration defined in code?
⚠ Common exam trap
Cisco often tests the concept that idempotency is the core principle of IaC for state convergence, tempting candidates to choose version control or rollback procedures because they are familiar best practices, but they do not directly ensure the environment state matches the 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
✓
Ensuring that the automation tool is idempotent.
Idempotency ensures that applying the same configuration multiple times always results in the same desired state, regardless of the current state of the device. This is the most critical practice for IaC because it prevents configuration drift and guarantees that the environment state matches the code-defined configuration. Without idempotency, repeated runs of the automation tool could introduce unintended changes or fail to correct deviations.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Using Jinja2 templates to generate device configurations.
Why it's wrong here
Jinja2 templates generate configuration text but do not compare running state against the declared intent, so drift goes undetected. Templating is tempting because it standardises device configuration, and it would be correct where the goal is consistent generation rather than state reconciliation.
- ✓
Ensuring that the automation tool is idempotent.
Why this is correct
Idempotent automation reapplies the declared configuration without duplicating or compounding changes, so repeated runs converge the device state onto the desired configuration. This directly satisfies the stem's requirement that environment state match the code-defined desired state, rather than drifting after each execution.
- ✗
Using version control for all configuration files.
Why it's wrong here
Version control tracks and audits changes to configuration files, but it does not compare the live device state against the committed definitions, so drift goes unnoticed. It is tempting because version control underpins every IaC workflow, yet the practice that actually reconciles running state with desired state is continuous drift detection and remediation.
- ✗
Implementing rollback procedures for failed deployments.
Why it's wrong here
Rollback restores a previous state after a failed deployment; it does not continuously reconcile drift between the running configuration and the code-defined intent. It is tempting because rollback is genuinely valuable for recovering from faulty changes, but the requirement here is ongoing convergence, which is drift detection and remediation.
Go deeper
Related to this question
About these practice questions
One of 975 original 200-901 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.