EX294 Practice Question: Create content collections and execution environments

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  ansible-galaxy collection build

  Why it's wrong here

  `ansible-galaxy collection build` is used to package an Ansible collection into a tarball for distribution, not to build an execution environment container image. It operates on a collection's `galaxy.yml` and produces a `.tar.gz` artifact. This command does not create container images or handle Python dependencies for execution environments.

• ✗

  ansible-navigator build execution-environment.yml

  Why it's wrong here

  `ansible-navigator` is a tool for running and developing Ansible content, not for building execution environments. It can run playbooks inside an execution environment, but it does not have a `build` subcommand. Building an execution environment is specifically the domain of `ansible-builder`.

• ✗

  podman build -t my-ee:latest .

  Why it's wrong here

  While `podman build` can build container images from a Containerfile, it does not interpret the `execution-environment.yml` file or automatically install collections and Python dependencies. Using it directly would require manually writing a Containerfile with all necessary steps. The `ansible-builder` tool is designed to generate that Containerfile and orchestrate the build.

• ✓

  ansible-builder build --file execution-environment.yml

  Why this is correct

  The `ansible-builder build` command reads the execution environment definition file (by default `execution-environment.yml` in the current directory) and builds a container image. The `--file` flag can explicitly specify the definition file, though it is optional when the file has the default name. This command is the standard way to create an execution environment image from a definition.

Go deeper

Related to this question