EX294 Deploy Ansible Automation Platform Practice Question
A team uses execution environments (EE) for job templates. The admin builds a custom EE using `ansible-builder` with a `execution-environment.yml` file that includes a `base_image: registry.redhat.io/ansible-automation-platform-21/ee-minimal-rhel8:latest` and a custom Python requirement. However, the controller reports that the EE is not found when launching a job. What is the most likely issue?
⚠ Common exam trap
Watch out — candidates often assume building the image locally is sufficient, but the controller requires the image to be accessible via a registry pull, not from the local build cache.
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
✓
The built EE image was not pushed to the container registry specified in the controller's execution environment configuration.
After building a custom execution environment with `ansible-builder`, the resulting container image must be pushed to a container registry that the Automation Controller is configured to access. The controller does not automatically pull images from the local build cache; it references the image by its registry path. If the image is not present in the specified registry, the controller will report that the EE is not found when launching a job.
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 built EE image was not pushed to the container registry specified in the controller's execution environment configuration.
Why this is correct
Ansible-builder produces the EE image locally, but the controller resolves EEs from a configured container registry. Unless the image is pushed there, the controller cannot pull it, producing the 'not found' error despite a successful build.
- ✗
The base image is pointing to an incorrect registry path.
Why it's wrong here
The registry path given is a valid Red Hat base image reference, so it would not cause a 'not found' error for the EE itself. It is tempting because base image errors are common build failures, but a bad base image breaks the build, whereas this error occurs at job launch when the controller cannot locate the EE.
- ✗
The custom Python requirement needs to be added to `requirements.txt` in the project.
Why it's wrong here
Python requirements belong in the EE definition, not the project; adding them to requirements.txt changes the playbook's runtime dependencies, not the built image. It is tempting because requirements.txt is the familiar Ansible dependency file, but the controller's 'not found' error concerns image availability, not Python packages.
- ✗
The execution environment does not include a `Containerfile` for the build process.
Why it's wrong here
ansible-builder generates the Containerfile automatically from execution-environment.yml, so its absence is not the issue. It is tempting because Containerfiles are central to image builds, but the controller's 'not found' error indicates the built image was never pushed to a registry the controller can reach.
Go deeper
Related to this question
About these practice questions
One of 392 original EX294 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.