- A
Use 'ansible-playbook playbook.yml --forks 1' to slow down the update.
Why wrong: Setting forks does not exclude hosts; it only reduces parallelism.
- B
Use 'ansible-playbook playbook.yml --limit all:!hostname' to exclude the unreachable host.
Correct. --limit can exclude the failed host using the '!' operator.
- C
Add 'any_errors_fatal: false' to the playbook and rerun.
Why wrong: any_errors_fatal does not skip hosts; it controls whether all hosts stop on error.
- D
Rerun the playbook with the same command; it will skip the unreachable host automatically.
Why wrong: Ansible does not automatically skip previously failed hosts unless 'any_errors_fatal' is set.
EX294 Coordinate rolling updates Practice Question
This EX294 practice question tests your understanding of coordinate rolling updates. 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.
During a rolling update using an Ansible playbook with serial: 2, one host in the first batch becomes unreachable. The playbook fails with an unreachable host error. How should the administrator proceed to complete the update on the remaining hosts while excluding the problematic host?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"first"Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
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
Use 'ansible-playbook playbook.yml --limit all:!hostname' to exclude the unreachable host.
Option B is correct because the `--limit` flag with the pattern `all:!hostname` uses Ansible's inventory host pattern syntax to exclude a specific host from the playbook run. This allows the administrator to rerun the playbook against all hosts except the unreachable one, completing the rolling update without re-attempting the failed host. The `serial: 2` setting is irrelevant once the host is excluded, as the playbook will only target the remaining reachable hosts.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 'ansible-playbook playbook.yml --forks 1' to slow down the update.
Why it's wrong here
Setting forks does not exclude hosts; it only reduces parallelism.
- ✓
Use 'ansible-playbook playbook.yml --limit all:!hostname' to exclude the unreachable host.
Why this is correct
Correct. --limit can exclude the failed host using the '!' operator.
Clue confirmation
The clue word "first" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Add 'any_errors_fatal: false' to the playbook and rerun.
Why it's wrong here
any_errors_fatal does not skip hosts; it controls whether all hosts stop on error.
- ✗
Rerun the playbook with the same command; it will skip the unreachable host automatically.
Why it's wrong here
Ansible does not automatically skip previously failed hosts unless 'any_errors_fatal' is set.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume Ansible automatically retries or skips unreachable hosts on subsequent runs, when in fact it will fail again unless the host is explicitly excluded using `--limit` or the connectivity issue is resolved.
Detailed technical explanation
How to think about this question
Under the hood, Ansible's `--limit` flag applies a host pattern filter at the inventory level, effectively removing the excluded host from the list of targets before task execution begins. The `serial` keyword controls batch size but does not affect host selection; without `--limit`, the unreachable host remains in the batch and causes a fatal error that halts the entire playbook. In real-world rolling updates, administrators often combine `--limit` with dynamic inventory scripts to surgically remove problematic nodes without modifying the inventory file.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Coordinate rolling updates — study guide chapter
Learn the concepts, then practise the questions
- →
Coordinate rolling updates practice questions
Targeted practice on this topic area only
- →
All EX294 questions
518 questions across all exam domains
- →
Red Hat Certified Engineer EX294 study guide
Full concept coverage aligned to exam objectives
- →
EX294 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related EX294 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Deploy Ansible Automation Platform practice questions
Practise EX294 questions linked to Deploy Ansible Automation Platform.
Manage inventories and credentials practice questions
Practise EX294 questions linked to Manage inventories and credentials.
Manage task execution and roles practice questions
Practise EX294 questions linked to Manage task execution and roles.
Coordinate rolling updates practice questions
Practise EX294 questions linked to Coordinate rolling updates.
Transform data with filters and plugins practice questions
Practise EX294 questions linked to Transform data with filters and plugins.
Create content collections and execution environments practice questions
Practise EX294 questions linked to Create content collections and execution environments.
Implement advanced Ansible automation practice questions
Practise EX294 questions linked to Implement advanced Ansible automation.
Manage automation security and operations practice questions
Practise EX294 questions linked to Manage automation security and operations.
EX294 fundamentals practice questions
Practise EX294 questions linked to EX294 fundamentals.
EX294 scenario practice questions
Practise EX294 questions linked to EX294 scenario.
EX294 troubleshooting practice questions
Practise EX294 questions linked to EX294 troubleshooting.
Practice this exam
Start a free EX294 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this EX294 question test?
Coordinate rolling updates — This question tests Coordinate rolling updates — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use 'ansible-playbook playbook.yml --limit all:!hostname' to exclude the unreachable host. — Option B is correct because the `--limit` flag with the pattern `all:!hostname` uses Ansible's inventory host pattern syntax to exclude a specific host from the playbook run. This allows the administrator to rerun the playbook against all hosts except the unreachable one, completing the rolling update without re-attempting the failed host. The `serial: 2` setting is irrelevant once the host is excluded, as the playbook will only target the remaining reachable hosts.
What should I do if I get this EX294 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "first". Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
What is the key concept behind this question?
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 25, 2026
This EX294 practice question is part of Courseiva's free Red Hat 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 EX294 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.