EX294 Create content collections and execution environments Practice Test 6 — 15 Questions

Question 1

A developer wants to create a new collection named 'myutils' under namespace 'myorg'. Which command initializes the collection structure?

Accepted Answer

ansible-galaxy collection init myorg.myutils. The correct command to initialize a new Ansible collection structure is `ansible-galaxy collection init <namespace.collection>`. This creates the required directory layout, including `galaxy.yml`, `README.md`, and subdirectories like `roles/`, `playbooks/`, and `plugins/`. Option D matches this syntax exactly.

Answer

ansible-galaxy collection scaffold myorg.myutils

Answer

ansible-galaxy collection create myorg.myutils

Answer

ansible-galaxy collection new myorg.myutils

Question 2

An organization's execution environment must include a custom RPM that is not in the default base image. How should this be added in the execution-environment.yml?

Accepted Answer

Add the RPM to the 'dependencies' section under 'system'.. In an execution-environment.yml file, custom RPM packages that are not part of the default base image must be listed under the 'dependencies' section with the 'system' key. This instructs ansible-builder to install those RPMs using the system package manager (e.g., dnf or yum) during the build process, ensuring the execution environment includes the required system-level libraries or tools.

Answer

Add the RPM to the 'dependencies' section under 'python'.

Answer

Use a 'prepended_base' directive.

Answer

Use a custom base image that includes the RPM.

Question 3

A user wants to build an execution environment from a definition file. Which command is used?

Accepted Answer

ansible-builder build -f execution-environment.yml. The `ansible-builder build` command is the correct tool for building an Ansible execution environment from a a definition file. The `-f` flag specifies the path to the `execution-environment.yml` file, which defines the base image, required collections, and system dependencies for the containerized environment.

Answer

ansible-playbook build -i ee.yml

Answer

ansible-execution-environment build -f ee.yml

Answer

ansible-galaxy build execution-environment.yml

Question 4

During a collection development, a developer wants to include a Python dependency that is not available in the base image of the execution environment. Where should this dependency be declared?

Accepted Answer

In the execution-environment.yml under 'dependencies' -> 'python'. In Ansible execution environments, Python dependencies that are not part of the base image must be declared in the `execution-environment.yml` file under the `dependencies` key, specifically within the `python` subkey. This file is used by `ansible-builder` to build a custom container image that includes those additional Python packages. The base image already contains a standard set of Python libraries, but any extra ones needed by a collection must be explicitly listed here to be installed during the build process.

Answer

In the collection's requirements.yml under 'python'

Answer

In the collection's galaxy.yml under 'dependencies'

Answer

In the collection's meta/runtime.yml under 'python_dependencies'

Question 5

Which TWO actions are required to use a private Automation Hub to share collections?

Accepted Answer

Configure the server in ansible.cfg under [galaxy] server_list.. Option A is correct because to make the ansible-galaxy client talk to a private Automation Hub instead of the default galaxy.ansible.com, you must list that server under the [galaxy] server_list setting in ansible.cfg (or via the ANSIBLE_GALAXY_SERVER_LIST environment variable), which defines the server name and URL used for collection operations. Option E is correct because private Automation Hub requires authentication for publishing and often for downloading collections, so you must generate an API token in the Automation Hub UI and supply it via the token key under the server's section in ansible.cfg or through the corresponding environment variable (e.g., ANSIBLE_GALAXY_SERVER_<name>_TOKEN). Option B is not required because building a custom execution environment is an optional packaging/distribution approach, not a prerequisite for the client to share collections with a private hub. Option C is not required because --ignore-certs is only a workaround for certificate validation failures with self-signed certificates and is not part of the standard configuration for using a private Automation Hub. Option D is not required because --pull-policy missing is an ansible-navigator execution-environment behavior and has nothing to do with configuring a private Automation Hub as a collection source.

Answer

Build a custom execution environment that includes the collections.

Answer

Run ansible-galaxy collection install --ignore-certs if using self-signed certs.

Answer

Use ansible-navigator with --pull-policy missing.

Question 6

Which TWO statements about execution environments are true?

Accepted Answer

Execution environments can include both Ansible and system dependencies.. Option A is correct because an execution environment is an OCI container image that bundles the Ansible Core/ansible-runner runtime together with collections, Python libraries, and system-level dependencies (RPMs, etc.), so it can carry both Ansible and system dependencies. Option E is correct because execution environments are distributed and consumed as OCI container images (e.g., via podman or docker registries), which is the packaging format that makes them portable and reproducible. Option B is wrong because ansible-playbook can be run inside an execution environment (for example, via ansible-navigator or by invoking the container directly), so they are not incompatible. Option C is wrong because ansible-builder is only one tool for creating execution environments; they can also be built with a Containerfile/Dockerfile or other tooling. Option D is wrong because Ansible Navigator is a convenience CLI for running and inspecting execution environments, but it is not required — podman/docker or ansible-runner can use them directly.

Answer

Execution environments cannot be used with ansible-playbook directly.

Answer

Execution environments must be built using ansible-builder.

Answer

Ansible Navigator is required to use execution environments.

Question 7

Which THREE components are typically included in an execution environment?

Accepted Answer

Base OS image. An execution environment is a container image that bundles everything needed to run Ansible automation, so option A (Base OS image) is correct because the container must be built on a base operating system layer such as a UBI or Debian image. Option C (Ansible Core and collections) is correct because the execution environment packages ansible-core together with the required collections so playbooks and roles have their modules and plugins available. Option D (Python interpreter and dependencies) is correct because Ansible runs on Python, and the environment must include the Python interpreter plus any Python libraries the modules and collections depend on. Option B (Ansible Navigator) is not included; it is a separate command-line tool used to build, run, and inspect execution environments, not a component inside them. Option E (Ansible Tower/AWX) is not included either, since AWX and Tower are automation controller platforms that consume execution environments rather than being packaged within one.

Answer

Ansible Navigator

Answer

Ansible Tower/AWX

Question 8

Refer to the exhibit. A developer builds an execution environment using this execution-environment.yml. After building, the container starts but ansible-navigator cannot connect to the container because the required SSH packages are missing. Which file most likely needs to be updated?

Accepted Answer

bindep.txt. D is correct because `bindep.txt` specifies system-level package dependencies (like `openssh-clients` or `sshpass`) that must be installed in the container image. When building an execution environment, `ansible-builder` reads `bindep.txt` to install RPM packages via `dnf` (or `apt` on Debian-based images). If SSH packages are missing, the `bindep.txt` file is the most likely place to add them, as it directly controls which system packages are included in the final image.

Answer

The base image itself

Answer

requirements.yml

Answer

requirements.txt

Question 9

A system administrator wants to build an Ansible execution environment using ansible-builder. Which file format is required to define the base image, dependencies, and additional Python packages for the build?

Accepted Answer

execution-environment.yml. `ansible-builder` requires an `execution-environment.yml` file to define the build context, including the base image (under `version: 1`), system-level dependencies (under `dependencies: system:`), and additional Python packages (under `dependencies: python:`). This file is the mandatory definition file for building an Ansible Execution Environment (EE) using `ansible-builder build`.

Answer

ansible-navigator.yml

Answer

Containerfile

Answer

requirements.yml

Question 10

An organization uses a private automation hub to distribute collections. A developer has created a new collection and needs to ensure it is available in the hub for others. Which command should the developer use to upload the collection to the private automation hub?

Accepted Answer

ansible-galaxy collection publish. `ansible-galaxy collection publish` is the command specifically designed to upload a built collection artifact (a .tar.gz file) to a Galaxy server, including a private automation hub. This command sends the collection to the configured Galaxy server endpoint, making it available for others to install via `ansible-galaxy collection install`.

Answer

ansible-galaxy collection import

Answer

ansible-galaxy collection build

Answer

ansible-galaxy collection install

Question 11

Your team maintains a collection that includes custom modules and plugins. You have been tasked with creating a content collection that adheres to the Red Hat Ansible Content Collection requirements. You have created the directory structure and written the collection code. Now you need to package the collection for distribution to your internal automation hub. You run 'ansible-galaxy collection build' and it completes successfully, generating a tarball. However, when you try to publish it to your private automation hub using 'ansible-galaxy collection publish', you get an authentication error. You have verified that your automation hub server URL and API token are correct. What is the most likely cause of the error?

Accepted Answer

The 'namespace' or 'name' in galaxy.yml does not match the namespace you are allowed to publish to on the automation hub.. The authentication error despite correct server URL and API token indicates that the issue is not with credentials or connectivity, but with authorization. Ansible Automation Hub enforces namespace-based access control: the `namespace` field in `galaxy.yml` must match a namespace you are permitted to publish to. If the namespace does not match, the hub rejects the upload with an authentication/authorization error, even though the token itself is valid.

Answer

The automation hub server is not reachable from your network.

Answer

The collection tarball is corrupted and needs to be rebuilt.

Answer

The collection contains a module that violates a content policy enforced by the hub.

Question 12

Your organization is migrating from manually maintained control nodes to using execution environments. You have created an execution environment that includes all necessary collections and Python dependencies. You want to ensure that developers use this execution environment when running playbooks. You have configured ansible-navigator on their workstations. However, some developers report that when they run a playbook, it uses the local installation of Ansible instead of the execution environment. What should you check first?

Accepted Answer

Ensure that the developers are using the 'ansible-navigator run' command instead of 'ansible-playbook'.. `ansible-navigator` is the CLI tool designed to run Ansible inside an execution environment. If developers run `ansible-playbook` directly, it uses the locally installed Ansible, bypassing the execution environment entirely. The question states that `ansible-navigator` is configured on their workstations, but the developers must use the `ansible-navigator run` subcommand to invoke playbooks within the containerized environment.

Answer

Confirm that the developers have installed ansible-builder locally.

Answer

Verify that the ansible-navigator configuration file points to the correct execution environment image.

Answer

Check that the execution environment container is running on the developers' machines.

Question 13

An administrator needs to create a custom execution environment that includes a specific Ansible collection and a Python package. Which two steps are required to build and use the execution environment? (Choose two.)

Accepted Answer

Build the execution environment using ansible-builder.. `ansible-builder` is the official tool for building Ansible execution environments, which are container images that bundle Ansible, collections, and dependencies. It uses a definition file (execution-environment.yml) to specify collections and Python packages, then builds the container image. Option E is correct because a `requirements.yml` file is the standard way to list Ansible collections for inclusion in an execution environment, and `ansible-builder` reads this file during the build process.

Answer

Create a Dockerfile that installs the collection and package.

Answer

Define the execution environment in ansible.cfg.

Answer

Push the execution environment to a private container registry.

Question 14

An automation team wants to build an execution environment that includes a specific collection from a private Automation Hub. Which file must be present in the build context to specify the collection and its source?

Accepted Answer

requirements.yml. To include a collection in an execution environment, `ansible-builder` reads `requirements.yml` from the build context. This file lists collections (and roles) to install, and can specify the source server, making it the correct place to declare a collection from a private Automation Hub.

Answer

execution-environment.yml

Answer

galaxy.yml

Answer

bindep.txt

Question 15

An engineer is preparing to build an execution environment using `ansible-builder`. The build must include several collections and also install additional Python packages. Which two files are used to declare these dependencies? (Choose two.)

Accepted Answer

requirements.yml. The correct files are `requirements.yml` for Ansible collections and roles, and `requirements.txt` for Python packages. These are referenced by the `execution-environment.yml` file and are used by `ansible-builder` to install the necessary dependencies into the execution environment.

Answer

galaxy.yml

Answer

execution-environment.yml

Answer

bindep.txt