- A
Set `max_fail_percentage` in the play to 0 and use `ignore_errors: yes` with a rescue block.
Why wrong: `max_fail_percentage` controls play failure, not retries; `ignore_errors` prevents failure but doesn't retry.
- B
Use the `throttle` keyword to limit concurrent tasks and rely on idempotency.
Why wrong: `throttle` limits concurrency but does not retry failed tasks.
- C
Set `serial: 1` on the play to ensure only one host is processed at a time and rely on idempotency.
Why wrong: `serial` controls batch size, not retries; it doesn't handle transient failures.
- D
Use the `until` loop with `retries` and `delay` parameters on the task.
The `until` loop with `retries` and `delay` retries the task until a condition is met or retries are exhausted, ideal for transient failures.
EX294 Implement advanced Ansible automation Practice Question
This EX294 practice question tests your understanding of implement advanced ansible automation. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 Ansible automation team is designing a playbook to manage network devices. They need to ensure that the playbook can handle transient network failures by retrying failed tasks a specific number of times with a delay between retries. Which approach should they use?
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 the `until` loop with `retries` and `delay` parameters on the task.
The `until` loop with `retries` and `delay` parameters is the correct approach because it allows a task to be retried a specified number of times with a configurable pause between attempts, directly addressing transient network failures. This is a built-in Ansible feature for handling intermittent issues without additional error-handling constructs.
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.
- ✗
Set `max_fail_percentage` in the play to 0 and use `ignore_errors: yes` with a rescue block.
Why it's wrong here
`max_fail_percentage` controls play failure, not retries; `ignore_errors` prevents failure but doesn't retry.
- ✗
Use the `throttle` keyword to limit concurrent tasks and rely on idempotency.
Why it's wrong here
`throttle` limits concurrency but does not retry failed tasks.
- ✗
Set `serial: 1` on the play to ensure only one host is processed at a time and rely on idempotency.
Why it's wrong here
`serial` controls batch size, not retries; it doesn't handle transient failures.
- ✓
Use the `until` loop with `retries` and `delay` parameters on the task.
Why this is correct
The `until` loop with `retries` and `delay` retries the task until a condition is met or retries are exhausted, ideal for transient failures.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse concurrency controls (`serial`, `throttle`) or error-handling directives (`ignore_errors`, `max_fail_percentage`) with the retry mechanism, which is specifically implemented via the `until` loop with `retries` and `delay` parameters.
Detailed technical explanation
How to think about this question
The `until` loop evaluates a condition (often a registered variable) after each attempt; if the condition is not met, the task retries up to the `retries` count with a `delay` in seconds between attempts. This is particularly useful for network modules like `ios_command` or `uri` where transient failures (e.g., SSH timeouts or API rate limits) are common, and the loop ensures idempotency by retrying until a successful response or exhaustion of retries.
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.
- →
Implement advanced Ansible automation — study guide chapter
Learn the concepts, then practise the questions
- →
Implement advanced Ansible automation 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?
Implement advanced Ansible automation — This question tests Implement advanced Ansible automation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use the `until` loop with `retries` and `delay` parameters on the task. — The `until` loop with `retries` and `delay` parameters is the correct approach because it allows a task to be retried a specified number of times with a configurable pause between attempts, directly addressing transient network failures. This is a built-in Ansible feature for handling intermittent issues without additional error-handling constructs.
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.
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 →
Keep practising
More EX294 practice questions
- Drag and drop the steps to configure an Ansible control node for managing remote hosts into the correct order.
- Drag and drop the steps to configure a logical volume (LV) using LVM on a new disk in the correct order.
- Drag and drop the steps to configure a network bond (bond0) using nmcli in the correct order.
- Drag and drop the steps to configure a container using Podman with a custom Dockerfile in the correct order.
- Drag and drop the steps to configure a basic NFS server to export a directory in the correct order.
- Drag and drop the steps to configure a systemd service to start automatically at boot in the correct order.
Last reviewed: Jun 11, 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.