Correct YAML Syntax for Tasks in ansible-navigator
This EX294 practice question tests your understanding of deploy ansible automation platform. 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.
Network Topology
A junior admin runs the command shown in the exhibit. What is the most likely cause of the error?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Network Topology
A
The 'ansible.builtin' collection is not installed in the execution environment.
Why wrong: The builtin collection is always present.
B
The shell module requires a command argument that is missing.
Why wrong: The command argument is present under 'cmd'.
C
The playbook file path is incorrect; ansible-navigator cannot find the file.
Why wrong: The error message shows the file is read, so path is correct.
D
The playbook uses incorrect YAML syntax; the task should use the 'module' keyword.
The correct syntax is 'module: ansible.builtin.shell' or simply 'ansible.builtin.shell:' as a mapping key.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The playbook uses incorrect YAML syntax; the task should use the 'module' keyword.
Option D is correct because the error shown in the exhibit is a YAML syntax error: the task uses a module name (e.g., `shell`) directly as a key, but Ansible requires the `module` keyword to specify the module when using `ansible-navigator` or `ansible-playbook` with strict YAML parsing. The correct syntax is `module: shell` or using the module name as a top-level key only in older playbook formats, which `ansible-navigator` rejects.
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 'ansible.builtin' collection is not installed in the execution environment.
Why it's wrong here
The builtin collection is always present.
✗
The shell module requires a command argument that is missing.
Why it's wrong here
The command argument is present under 'cmd'.
✗
The playbook file path is incorrect; ansible-navigator cannot find the file.
Why it's wrong here
The error message shows the file is read, so path is correct.
✓
The playbook uses incorrect YAML syntax; the task should use the 'module' keyword.
Why this is correct
The correct syntax is 'module: ansible.builtin.shell' or simply 'ansible.builtin.shell:' as a mapping key.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
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 assume the error is about missing collections or arguments, but Red Hat often tests the subtle YAML syntax differences between `ansible-playbook` and `ansible-navigator` to catch those who rely on older playbook formats.
Trap categories for this question
Command / output trap
The command argument is present under 'cmd'.
Detailed technical explanation
How to think about this question
In Ansible, the `ansible-navigator` tool uses a stricter YAML parser that enforces the use of the `module` keyword for tasks, unlike `ansible-playbook` which allows the module name as a key directly. This difference arises because `ansible-navigator` is designed for automation controller and execution environments, where playbook syntax must be unambiguous. A real-world scenario is migrating playbooks from `ansible-playbook` to `ansible-navigator`, where old-style tasks without `module:` cause unexpected failures.
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.
Deploy Ansible Automation Platform — This question tests Deploy Ansible Automation Platform — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The playbook uses incorrect YAML syntax; the task should use the 'module' keyword. — Option D is correct because the error shown in the exhibit is a YAML syntax error: the task uses a module name (e.g., `shell`) directly as a key, but Ansible requires the `module` keyword to specify the module when using `ansible-navigator` or `ansible-playbook` with strict YAML parsing. The correct syntax is `module: shell` or using the module name as a top-level key only in older playbook formats, which `ansible-navigator` rejects.
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: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
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.
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.