Create content collections and execution environments →hardMultiple Choice

EX294 Practice Question: Create content collections and execution environments

Exhibit

Refer to the exhibit.

$ cat execution-environment.yml
---
version: 1
build_arg_defaults:
  EE_BASE_IMAGE: 'registry.redhat.io/ansible-automation-platform-21/ee-minimal-rhel8:latest'
dependencies:
  galaxy: requirements.yml
  python: requirements.txt

$ cat requirements.yml
---
collections:
  - name: redhat.insights
  - name: community.general

$ cat requirements.txt
ansible==2.9.27

An admin attempts to build an execution environment using the exhibited files. The build fails with an error about incompatible Python dependency. What is the most likely cause?

⚠ Common exam trap

A common mix-up: candidates assume the error is due to syntax or invalid base images, but the question specifically mentions 'incompatible Python dependency,' which directly points to a version conflict in the pip requirements.

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 Python requirements.txt tries to install a version of Ansible that conflicts with the version in the base image.

The build fails because the Python `requirements.txt` file attempts to install a version of Ansible that conflicts with the version already present in the base image `ee-minimal-rhel8`. Execution environments are designed to include a specific Ansible version in the base image; adding a different version via pip creates a dependency conflict that breaks the build.

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 Python requirements.txt tries to install a version of Ansible that conflicts with the version in the base image.
Why this is correct
The base execution environment image already ships a pinned ansible-core version; requirements.txt requesting a different version forces pip to resolve an incompatible set, so the build aborts with a dependency conflict rather than installing cleanly.
✗
The execution-environment.yml file uses incorrect syntax for the 'dependencies' section.
Why it's wrong here
The failure concerns Python package resolution, not YAML parsing; the build would abort earlier with a schema or syntax error if the `dependencies` section were malformed. This option tempts because `execution-environment.yml` does define dependencies, so incorrect syntax would genuinely break builds — but the stem already reports an incompatible Python dependency error.
✗
The collections in requirements.yml are not fully qualified.
Why it's wrong here
Fully qualified collection names affect resolution, not Python dependency conflicts. The build error stems from incompatible Python packages, so collection naming is irrelevant here. This option would be correct when collections fail to resolve or download during environment creation, where namespace omission genuinely breaks installation.
✗
The base image 'ee-minimal-rhel8' is not a valid execution environment base image.
Why it's wrong here
The base image name is valid; execution environment build failures citing incompatible Python dependencies stem from conflicting package versions declared in the requirements or bindep files. It is tempting to blame the base image, but the error explicitly names a dependency conflict, not an image resolution problem.

Go deeper

EX294 Practice Question: Create content collections and execution environments

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question