How many Troubleshooting Scenario Questions questions are on this page?

This page has 10 Troubleshooting Scenario Questions scenario questions for the EX294 exam, each with detailed explanations and wrong-answer analysis.

How should I approach EX294 scenario questions?

Read the full scenario before looking at the answer options. Identify the constraint or requirement in the scenario, then eliminate options that are generally true but wrong for this specific case. Scenario questions reward careful reading over pattern matching.

← Back to Red Hat Certified Engineer EX294 questions

Scenario-based practice

Troubleshooting Scenario Questions

Practise Red Hat Certified Engineer EX294 practice questions — original exam-style scenarios covering every exam domain, with detailed explanations, wrong-answer analysis, and common exam traps.

Start full practice test Read exam guide

scenario questions

EX294

exam code

Red Hat

vendor

Scenario guide

How to approach troubleshooting scenario questions

These questions describe a network symptom and ask you to identify the root cause or the correct fix. They appear across all certification exams and reward systematic thinking over memorisation. The best candidates follow a consistent troubleshooting framework even under time pressure.

Quick answer

Troubleshooting Scenario Questions questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Practice scenarios

Question 1hardmultiple choice

Read the full Ansible explanation →

A DevOps engineer is troubleshooting an Ansible Automation Platform deployment where ansible-navigator fails to run a playbook, showing the error 'Error: Unable to pull execution environment image'. The ansible-navigator configuration file is shown in the exhibit. Which change should the engineer make to resolve the issue?

Exhibit

Refer to the exhibit.

[root@controller ~]# cat /etc/ansible-automation-platform/ansible-navigator.yml
---
ansible-navigator:
  execution-environment:
    image: registry.internal.example.com/ee-supported:latest
    pull:
      policy: missing
  playbook-artifact:
    enable: false
  logging:
    level: debug
  mode: stdout
  set-environment:
    ANSIBLE_INVENTORY: /opt/inventory/hosts
    ANSIBLE_ROLES_PATH: /opt/roles

A
Set 'mode' to 'interactive' instead of 'stdout'
Why wrong: Mode affects output format, not image pulling.
B
Change the execution-environment image to 'registry.redhat.io/ansible-automation-platform-24/ee-minimal-rhel8:latest'
Why wrong: The image name is not the cause; the error is about pulling the existing image.
C
Change 'pull policy' from 'missing' to 'always'
Setting policy to 'always' forces a pull attempt each time, which can resolve pull failures due to missing or outdated images.
D
Set 'playbook-artifact enable' to 'true'
Why wrong: Artifact saving does not affect image pulling.

Full breakdown with real-world context →

Question 2easymultiple choice

Full question →

A junior admin is troubleshooting why a job template fails with 'Permission denied' when connecting to a target host. The job template uses a machine credential that appears correct. What is the first thing to check?

A
Verify the inventory contains the correct host IP
Why wrong: Permission denied usually indicates authentication failure, not host unreachable.
B
Check the credential's username and private key / password
The error suggests the credentials are not accepted by the target host.
C
Check the vault credential used in the job template
Why wrong: Vault credentials are not used for SSH authentication.
D
Check the project sync status
Why wrong: Project sync does not affect SSH authentication.

Full breakdown with real-world context →

Question 3hardmulti select

Full question →

A system administrator is troubleshooting an execution environment that fails to build. The error indicates that a required collection cannot be found. Which THREE of the following actions could resolve the issue?

A
Verify that the collection is listed in the 'dependencies' section of the execution-environment.yml under 'galaxy'.
Correct. The builder needs to know which collections to install.
B
Add the collection to the 'additional_build_steps' section with a manual 'ansible-galaxy collection install' command.
Why wrong: Incorrect. This is not a standard practice and may lead to layer issues; the proper way is through dependencies.
C
Include the collection in the 'build_ignore' list to skip it.
Why wrong: Incorrect. Ignoring the collection would result in it being missing from the execution environment.
D
Change the base image to one that includes the collection pre-installed.
Correct. Using a base image with the collection already present avoids the installation step.
E
Ensure that the collection is published to a configured Galaxy server and that authentication is correct.
Correct. If the collection is private, credentials must be provided.

Full breakdown with real-world context →

Question 4easymultiple choice

Full question →

An automation team wants to grant a group of operators the ability to launch job templates in automation controller but prevent them from modifying the job template configuration. They also need to troubleshoot failed jobs by viewing job output. Which predefined role should be assigned to the team for a specific job template?

A
Execute role
Allows launching and viewing output, but not modifying the job template.
B
Read role
Why wrong: Allows viewing configuration but not launching jobs.
C
Admin role
Why wrong: Grants full control, including modification, which is not desired.
D
Update role
Why wrong: Used for updating project contents, not for job template execution.

Full breakdown with real-world context →

Question 5mediummultiple choice

Read the full Ansible explanation →

An execution environment fails to start because the container image is missing the ansible-runner package. Which step in the build process should have included it?

A
The ansible-runner role in the builder definition
Why wrong: There is no standard 'ansible-runner role'; ansible-runner is included in the base image.
B
The base image selection in execution-environment.yml
The base image (e.g., ee-29-rhel8) includes ansible-runner and ansible-core; using a minimal base may omit it.
C
The requirement to install ansible-runner via pip in the containerfile
Why wrong: While possible, best practice is to use a base image that already contains ansible-runner.
D
The additional_dependencies section in execution-environment.yml
Why wrong: additional_dependencies is for Python packages, not runtime components like ansible-runner.

Full breakdown with real-world context →

Question 6hardmultiple choice

Read the full DNS explanation →

The build fails with a DNS resolution error for `registry.redhat.io`. Which troubleshooting step is most likely to resolve the issue?

Network Topology

A
Run `podman login registry.redhat.io` to authenticate.
Why wrong: Authentication is separate from DNS resolution.
B
Restart the container runtime service.
Why wrong: Restarting won't fix DNS configuration.
C
Verify DNS settings in `/etc/resolv.conf` or configure a custom DNS server for the container runtime.
Corrects the underlying DNS issue.
D
Use the `--no-cache` flag to force a fresh build.
Why wrong: Does not address DNS resolution.

Full breakdown with real-world context →

Question 7hardmultiple choice

Read the full Ansible explanation →

An execution environment fails to build because `pip install` fails when installing a Python package from a private repository that requires authentication. The build works when run locally by the developer. Which approach should be taken to securely provide credentials during the `ansible-builder build` process?

A
Store the credentials in the Automation Hub token and reference it.
Why wrong: Automation Hub token is for Ansible Galaxy, not Python package repositories.
B
Add the credentials directly to the `Containerfile` that `ansible-builder` generates.
Why wrong: This would expose credentials in the container image.
C
Include the credentials in the `execution-environment.yml` under `dependencies: python:`.
Why wrong: That file is not for credentials and would leak them.
D
Create a `pip.conf` file that uses environment variables or BuildKit secrets to inject credentials.
Securely injects credentials without exposing them in the definition file.

Full breakdown with real-world context →

Question 8mediummultiple choice

Read the full Ansible explanation →

A company is deploying Ansible Automation Platform (AAP) in a three-node cluster: one automation controller node, one private automation hub node, and one database node (PostgreSQL). The deployment uses an execution environment that pulls from the private automation hub. After a successful installation, all nodes are reachable and services are running. However, when launching a job template that uses the execution environment, the job fails with the error: 'Unable to pull execution environment image from automation-hub.example.com:5000/ee/my-ee:latest - request to registry failed with status 403 Forbidden'. The administrator confirms that the execution environment image exists in the private automation hub and that the automation controller node can reach the registry via curl. What is the most likely cause and solution?

A
The private automation hub is configured to allow unauthenticated access; change the hub configuration to disable authentication.
Why wrong: Disabling authentication is not recommended and defeats security.
B
SELinux on the controller node is blocking container pulls; temporarily set SELinux to permissive.
Why wrong: SELinux would not cause a 403; it would block the connection entirely or show a different error.
C
Create a container registry credential in automation controller that uses the pull token from private automation hub, and associate it with the execution environment.
A valid credential is required to authenticate and pull the image.
D
The execution environment definition in the controller is missing the 'pull' field; add 'pull: always' to the job template.
Why wrong: The pull policy does not affect authentication.

Full breakdown with real-world context →

Question 9easymultiple choice

Read the full Ansible explanation →

You are an Ansible Tower administrator for a company that uses a dynamic inventory script to pull hosts from AWS. The script has been working for months, but after a recent security update, the job template that uses this inventory fails with the error: 'ERROR! Unable to parse /path/to/inventory/script.py as an inventory source'. The script is executable and the path is correct. What is the most likely cause?

A
The required Python modules (e.g., boto3) are missing in the Tower virtual environment.
Security update may have changed the environment.
B
The inventory source type has been changed to 'Manual' instead of 'Scraped from project'.
Why wrong: The error indicates it's trying to parse the script.
C
The script has been deleted from the project directory.
Why wrong: Path is still correct.
D
The script lacks execute permissions for the Tower service user.
Why wrong: Script is executable.

Full breakdown with real-world context →

Question 10mediummultiple choice

Read the full Ansible explanation →

Your organization uses Red Hat Ansible Automation Platform (AAP) to manage job execution. You have created a job template that runs a playbook to configure application servers. The playbook uses a custom credential to access a remote database. Recently, the job started failing with 'Authentication failed' when connecting to the database. You have verified that the database credentials are correct. The credential in AAP is of type 'Machine' and is assigned to the job template. The playbook uses the 'mysql_db' module. Which step should you take to troubleshoot and resolve the issue?

A
Change the credential type to 'Database' and provide the appropriate username and password.
Correct: The mysql_db module needs a database credential type to authenticate.
B
Add the database password as an extra variable in the job template.
Why wrong: Extra variables override inventory variables but do not address the credential type mismatch.
C
Modify the machine credential to include the database password as an SSH key.
Why wrong: Machine credentials are for SSH authentication, not database authentication.
D
Encrypt the database password using Ansible Vault and include it in the playbook.
Why wrong: Vault is for storing secrets, but the credential type in AAP still needs to be correct.

Full breakdown with real-world context →

These EX294 practice questions are part of Courseiva's free Red Hat certification practice question bank. Courseiva provides original exam-style EX294 questions with detailed explanations, topic-based practice, mock exams, readiness tracking, and study analytics.

Troubleshooting Scenario Questions

How to approach troubleshooting scenario questions

Quick answer

Related EX294 topic practice pages

Deploy Ansible Automation Platform practice questions

Manage inventories and credentials practice questions

Manage task execution and roles practice questions

Coordinate rolling updates practice questions

Transform data with filters and plugins practice questions

Create content collections and execution environments practice questions

Implement advanced Ansible automation practice questions

Manage automation security and operations practice questions

EX294 fundamentals practice questions

EX294 scenario practice questions

EX294 troubleshooting practice questions

Practice scenarios

Exhibit

A junior admin is troubleshooting why a job template fails with 'Permission denied' when connecting to a target host. The job template uses a machine credential that appears correct. What is the first thing to check?

A system administrator is troubleshooting an execution environment that fails to build. The error indicates that a required collection cannot be found. Which THREE of the following actions could resolve the issue?

An execution environment fails to start because the container image is missing the ansible-runner package. Which step in the build process should have included it?

The build fails with a DNS resolution error for `registry.redhat.io`. Which troubleshooting step is most likely to resolve the issue?