Gather Facts Disabled in Ansible — Variable Unavailable Error | Red Hat Certified Engineer Explained
This EX294 practice question tests your understanding of manage task execution and roles. 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.
Exhibit
---
- hosts: webservers
vars:
http_port: 80
tasks:
- name: Ensure Apache is running
service:
name: httpd
state: started
- name: Check if port is open
wait_for:
host: "{{ ansible_facts['default_ipv4']['address'] }}"
port: "{{ http_port }}"
state: started
delegate_to: localhost
Refer to the exhibit. An administrator runs the playbook but the wait_for task fails. What is the most likely cause?
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.
Exhibit
---
- hosts: webservers
vars:
http_port: 80
tasks:
- name: Ensure Apache is running
service:
name: httpd
state: started
- name: Check if port is open
wait_for:
host: "{{ ansible_facts['default_ipv4']['address'] }}"
port: "{{ http_port }}"
state: started
delegate_to: localhost
A
The ansible_facts variable may not be available because fact gathering is disabled.
Correct: without gather_facts: yes, ansible_facts is empty.
B
The http_port variable is misspelled.
Why wrong: Incorrect: http_port is defined correctly.
C
The wait_for module requires the 'port' parameter to be an integer.
Why wrong: Incorrect: wait_for accepts strings for port.
D
The delegate_to should be set to the remote host.
Why wrong: Incorrect: delegate_to to localhost is valid for checking port connectivity.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The ansible_facts variable may not be available because fact gathering is disabled.
Option A is correct because the playbook uses `ansible_facts['ansible_tcpip_socket']['port']` to supply the port number to the `wait_for` module. If fact gathering is disabled (e.g., via `gather_facts: no` at the play level or `ANSIBLE_GATHERING=explicit`), the `ansible_facts` dictionary is empty, so the variable resolves to `None` or an undefined value, causing the task to fail. The error is not a syntax or type issue but a missing fact dependency.
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_facts variable may not be available because fact gathering is disabled.
Why this is correct
Correct: without gather_facts: yes, ansible_facts is empty.
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.
✗
The http_port variable is misspelled.
Why it's wrong here
Incorrect: http_port is defined correctly.
✗
The wait_for module requires the 'port' parameter to be an integer.
Why it's wrong here
Incorrect: wait_for accepts strings for port.
✗
The delegate_to should be set to the remote host.
Why it's wrong here
Incorrect: delegate_to to localhost is valid for checking port connectivity.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the dependency between fact gathering and fact-based variables, trapping candidates who assume the error is a simple type mismatch or misspelling rather than a missing fact collection step.
Detailed technical explanation
How to think about this question
Ansible facts are gathered by the `setup` module, which populates `ansible_facts` with system information like network interfaces, IP addresses, and TCP socket details. When `gather_facts: no` is set, the `setup` module is skipped, leaving `ansible_facts` empty. The `wait_for` module then tries to evaluate `ansible_facts['ansible_tcpip_socket']['port']`, which fails because the key does not exist. In real-world scenarios, this often happens when playbooks are optimized to skip fact gathering for speed, but tasks inadvertently depend on fact data.
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.
Visual reference
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.
Manage task execution and roles — This question tests Manage task execution and roles — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The ansible_facts variable may not be available because fact gathering is disabled. — Option A is correct because the playbook uses `ansible_facts['ansible_tcpip_socket']['port']` to supply the port number to the `wait_for` module. If fact gathering is disabled (e.g., via `gather_facts: no` at the play level or `ANSIBLE_GATHERING=explicit`), the `ansible_facts` dictionary is empty, so the variable resolves to `None` or an undefined value, causing the task to fail. The error is not a syntax or type issue but a missing fact dependency.
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.