- A
The failure count in a batch exceeds max_fail_percentage.
Correct. The playbook aborts when batch failure percentage is exceeded.
- B
A task returns 'changed' when 'changed_when: false' is used.
Why wrong: changed_when affects reporting, not abort.
- C
A task fails on a host, and 'any_errors_fatal' is set to yes.
Correct. any_errors_fatal stops the play on first failure.
- D
The playbook runs with the --check flag.
Why wrong: --check does not abort; it shows changes without applying.
- E
A host is unreachable due to network issues.
Why wrong: Unreachable hosts are skipped by default; play continues.
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.
Which TWO conditions cause an Ansible rolling update playbook to abort immediately? (Choose exactly two.)
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"immediately / without restart"Why it matters: Time or reboot constraint — the correct answer must take effect right away without requiring a reboot or reload.
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
The failure count in a batch exceeds max_fail_percentage.
Option A is correct because Ansible's rolling update logic uses `max_fail_percentage` to control batch failure tolerance. If the number of failed hosts in a batch exceeds this percentage, the playbook aborts immediately to prevent cascading failures. Option C is correct because setting `any_errors_fatal: yes` causes the entire playbook to abort as soon as any task fails on any host, regardless of batch boundaries.
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.
- ✓
The failure count in a batch exceeds max_fail_percentage.
Why this is correct
Correct. The playbook aborts when batch failure percentage is exceeded.
Clue confirmation
The clue word "immediately / without restart" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
A task returns 'changed' when 'changed_when: false' is used.
Why it's wrong here
changed_when affects reporting, not abort.
- ✓
A task fails on a host, and 'any_errors_fatal' is set to yes.
Why this is correct
Correct. any_errors_fatal stops the play on first failure.
Clue confirmation
The clue word "immediately / without restart" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The playbook runs with the --check flag.
Why it's wrong here
--check does not abort; it shows changes without applying.
- ✗
A host is unreachable due to network issues.
Why it's wrong here
Unreachable hosts are skipped by default; play continues.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse 'unreachable' (Option E) with a fatal error, but Ansible treats unreachable hosts as failed hosts that are skipped, not as an immediate abort condition unless explicitly configured with `any_errors_fatal` or `max_fail_percentage`.
Trap categories for this question
Command / output trap
--check does not abort; it shows changes without applying.
Detailed technical explanation
How to think about this question
Under the hood, Ansible's rolling update batches are controlled by the `serial` keyword, and `max_fail_percentage` is evaluated per batch after all tasks in that batch complete. The abort is immediate only if the failure count exceeds the threshold; otherwise, failed hosts are removed from the batch and the play continues. In real-world scenarios, setting `max_fail_percentage: 0` ensures zero tolerance for failures in any batch, which is common for critical infrastructure updates.
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 practitioner preparing for the EX294 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
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: The failure count in a batch exceeds max_fail_percentage. — Option A is correct because Ansible's rolling update logic uses `max_fail_percentage` to control batch failure tolerance. If the number of failed hosts in a batch exceeds this percentage, the playbook aborts immediately to prevent cascading failures. Option C is correct because setting `any_errors_fatal: yes` causes the entire playbook to abort as soon as any task fails on any host, regardless of batch boundaries.
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: "immediately / without restart". Time or reboot constraint — the correct answer must take effect right away without requiring a reboot or reload.
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.