EX294 Manage task execution and roles Practice Question
This EX294 practice question tests your understanding of manage task execution and roles. 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
Refer to the exhibit. The administrator runs the playbook with the 'deploy' tag, but all tasks are skipped. What is the most likely reason?
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.
The --tags option filters tasks; only tasks with the 'deploy' tag run, but none of the role tasks have that tag.
The play-level tag does not propagate to role tasks unless inherited via include_role or import_role.
B
The role 'database' is not found in the roles_path.
Why wrong: If the role were missing, the playbook would fail with an error, not skip tasks.
C
The inventory host db1.example.com is not in the dbservers group.
Why wrong: The exhibit does not show inventory, but the play targets dbservers; if db1 were not in the group, it would be skipped with 'no hosts matched'.
D
The tags in the role tasks conflict with the play tags, causing a syntax error.
Why wrong: There is no conflict; tags can be different without errors.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The --tags option filters tasks; only tasks with the 'deploy' tag run, but none of the role tasks have that tag.
The playbook site.yml sets tags: ['deploy'] at the play level. When running with --tags 'deploy', only tasks that have the 'deploy' tag (or no tags) would run. However, all tasks in the role have specific tags (packages, service, database), and none have the 'deploy' tag. Tasks with tags that do not match the specified tag are skipped. To fix, either remove tags from the play or add the 'deploy' tag to the roles tasks.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
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 --tags option filters tasks; only tasks with the 'deploy' tag run, but none of the role tasks have that tag.
Why this is correct
The play-level tag does not propagate to role tasks unless inherited via include_role or import_role.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Static NAT maps one inside address to one outside address.
✗
The role 'database' is not found in the roles_path.
Why it's wrong here
If the role were missing, the playbook would fail with an error, not skip tasks.
✗
The inventory host db1.example.com is not in the dbservers group.
Why it's wrong here
The exhibit does not show inventory, but the play targets dbservers; if db1 were not in the group, it would be skipped with 'no hosts matched'.
✗
The tags in the role tasks conflict with the play tags, causing a syntax error.
Why it's wrong here
There is no conflict; tags can be different without errors.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Trap categories for this question
Command / output trap
The exhibit does not show inventory, but the play targets dbservers; if db1 were not in the group, it would be skipped with 'no hosts matched'.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
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.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related EX294 NAT questions on configuration and troubleshooting.
Manage task execution and roles — This question tests Manage task execution and roles — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: The --tags option filters tasks; only tasks with the 'deploy' tag run, but none of the role tasks have that tag. — The playbook site.yml sets tags: ['deploy'] at the play level. When running with --tags 'deploy', only tasks that have the 'deploy' tag (or no tags) would run. However, all tasks in the role have specific tags (packages, service, database), and none have the 'deploy' tag. Tasks with tags that do not match the specified tag are skipped. To fix, either remove tags from the play or add the 'deploy' tag to the roles tasks.
What should I do if I get this EX294 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related EX294 NAT questions on configuration and troubleshooting.
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?
Static NAT maps one inside address to one outside address.
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.