Quick Answer
The answer is to use Ansible’s `--limit` option with the retry file. When a playbook fails on some hosts, Ansible automatically generates a `.retry` file listing those failed hosts; running `ansible-playbook playbook.yml --limit @<retry-file>` re-executes the playbook only against those specific devices, making it the most efficient method because it avoids re-running on the 95 successful switches and requires no manual host listing. On the Cisco DevNet Associate 200-901 exam, this scenario tests your understanding of Ansible’s built-in failure recovery mechanisms, often appearing as a question about minimizing network disruption during bulk configuration changes. A common trap is to assume you must edit the inventory or use a separate host group, but the retry file with `--limit` is the direct, automated solution. Memory tip: think “retry file = re-run only the red hosts” — the `.retry` file is your automatic fail list.
This 200-901 practice question tests your understanding of infrastructure and automation. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
An engineer uses Ansible to push a configuration change to 100 switches. The playbook fails on 5 switches. What is the most efficient way to apply the change only to those 5?
Use Ansible's --limit with the retry file
This targets only the failed hosts.
Use --skip-tags on successful hosts
Why wrong: Not designed for this purpose.
Re-run the playbook on all switches
Why wrong: Wastes time on already successful switches.
Manually configure the 5 switches
Why wrong: Not automated and error-prone.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Use Ansible's --limit with the retry file
Ansible generates a retry file by default when a playbook fails on some hosts. Using `--limit @<retry-file>` re-runs the playbook only against the failed hosts, avoiding unnecessary execution on the 95 successful switches. This is the most efficient method because it targets only the problematic devices without manual intervention or full re-runs.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Use Ansible's --limit with the retry file
Why this is correct
This targets only the failed hosts.
Related concept
Read the scenario before looking for a memorised answer.
Use --skip-tags on successful hosts
Why it's wrong here
Not designed for this purpose.
Re-run the playbook on all switches
Why it's wrong here
Wastes time on already successful switches.
Manually configure the 5 switches
Why it's wrong here
Not automated and error-prone.
Common exam traps
Cisco often tests the distinction between host-level filtering (`--limit`) and task-level filtering (`--tags`/`--skip-tags`), leading candidates to confuse `--skip-tags` as a way to skip hosts instead of tasks.
Detailed technical explanation
Ansible's retry file is automatically created in the current directory with a `.retry` extension (e.g., `playbook.retry`) and contains a list of failed hosts, one per line. The `--limit` flag accepts a filename prefixed with `@` to read host patterns from that file, allowing precise targeting. This mechanism is especially useful in large-scale deployments where partial failures are common, as it avoids the overhead of re-running the entire playbook or writing custom logic to track failures.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A practitioner preparing for the 200-901 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Infrastructure and Automation — study guide chapter
Learn the concepts, then practise the questions
Infrastructure and Automation practice questions
Targeted practice on this topic area only
All 200-901 questions
505 questions across all exam domains
Cisco DevNet Associate 200-901 study guide
Full concept coverage aligned to exam objectives
200-901 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise 200-901 questions linked to Software Development and Design.
Practise 200-901 questions linked to Understanding and Using APIs.
Practise 200-901 questions linked to Cisco Platforms and Development.
Practise 200-901 questions linked to Application Deployment and Security.
Practise 200-901 questions linked to Infrastructure and Automation.
Practise 200-901 questions linked to Network Fundamentals.
Practise 200-901 questions linked to 200-901 fundamentals.
Practise 200-901 questions linked to 200-901 scenario.
Practise 200-901 questions linked to 200-901 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Infrastructure and Automation — This question tests Infrastructure and Automation — Read the scenario before looking for a memorised answer..
The correct answer is: Use Ansible's --limit with the retry file — Ansible generates a retry file by default when a playbook fails on some hosts. Using `--limit @<retry-file>` re-runs the playbook only against the failed hosts, avoiding unnecessary execution on the 95 successful switches. This is the most efficient method because it targets only the problematic devices without manual intervention or full re-runs.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.