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

Question 1

Which key in the galaxy.yml file defines the collection's namespace?

Accepted Answer

namespace. The `namespace` key in the `galaxy.yml` file explicitly defines the collection's namespace, which is the first part of the fully qualified collection name (FQCN) and is used to organize collections under a specific publisher or organization on Ansible Galaxy. This is a required field in the `galaxy.yml` metadata file, as per the Ansible Collection structure.

Answer

collection

Answer

authors

Answer

name

Question 2

Which TWO options are valid methods for including collections in an execution environment?

Accepted Answer

List collections under 'collections' in execution-environment.yml.. Option B is correct because the execution-environment.yml definition file supports a 'collections' key where you list collection names (and optionally versions/sources) that ansible-builder will install into the resulting execution environment image. Option D is correct because ansible-builder recognizes a requirements.yml file (referenced via the 'dependencies' section, e.g. galaxy: requirements.yml) that specifies collections to install, using the standard Galaxy requirements format. Option A is not the intended answer because running ansible-galaxy collection install in a pre-build script is a manual workaround rather than a declared, supported method for including collections in the execution environment definition. Option C is incorrect because galaxy.yml is a collection's own metadata/manifest file used when building or publishing a collection, not a mechanism for adding collections to an execution environment. Option E is incorrect because baking collections into the base image is not a valid ansible-builder method for including collections; collections should be declared in the execution environment definition so they are installed during the build.

Answer

Use ansible-galaxy collection install command in a pre-build script.

Answer

Use a 'galaxy.yml' file in the build context.

Answer

Include collections in the base image directly.

Question 3

Which TWO factors should be considered when choosing a base container image for an execution environment?

Accepted Answer

The presence of ansible-core and ansible-runner.. Option B is correct because an execution environment must contain ansible-core and ansible-runner to actually execute Ansible playbooks and roles; without these packages the image cannot function as an automation execution environment. Option D is correct because the base operating system version determines package availability, supported Python versions, and compatibility with the ansible-core and collection dependencies you install, so it must be chosen deliberately. Option A is not a primary selection factor because a recent update date alone does not guarantee the required Ansible tooling or OS compatibility. Option C is not a primary factor because image size affects pull time and storage but does not determine whether the environment can run Ansible content. Option E is not a primary factor because the number of layers is an optimization detail, not a functional requirement for an execution environment.

Answer

The date of the last update.

Answer

The size of the image.

Answer

The number of layers.

Question 4

Refer to the exhibit. A user runs ansible-runner with --container-image localhost/ee-30:latest and receives the error shown. What is the most likely cause?

Accepted Answer

The container image has not been pulled or built locally.. The error indicates that the container image `localhost/ee-30:latest` is not available locally. The `--container-image` flag tells ansible-runner to use a specific execution environment image, but if that image has not been pulled from a registry or built locally, the container runtime (e.g., Podman or Docker) cannot find it. Option D is correct because the image must exist in the local container storage before ansible-runner can launch it.

Answer

The container image tag is incorrect.

Answer

The ansible-runner process does not have network access.

Answer

The execution environment is not listed in the project's execution-environment.yml.

Question 5

Refer to the exhibit. A user attempts to download the collection using the download URL but the signature verification fails. What is the most likely reason?

Accepted Answer

The user's client does not have the corresponding public key.. B is correct because signature verification of a downloaded collection requires the client to have the corresponding public key that was used to sign the collection. If the user's client lacks this public key, the verification process will fail, even if the collection itself is properly signed and the URL is valid.

Answer

The collection version does not match.

Answer

The collection is not properly signed.

Answer

The download URL is invalid.

Question 6

An Ansible developer needs to use the `podman_container` module in a playbook. The module is part of the `containers.podman` collection. Which command must be run first to make the module available?

Accepted Answer

`ansible-galaxy collection install containers.podman`. The `podman_container` module is part of the `containers.podman` collection, which must be installed from Ansible Galaxy before it can be used in a playbook. The correct command is `ansible-galaxy collection install containers.podman`, which downloads and installs the collection into the local collections path, making all its modules and plugins available.

Answer

`ansible-galaxy install containers.podman`

Answer

`ansible-galaxy collection search containers.podman`

Answer

`ansible-galaxy collection install containers.podman:1.0.0`

Question 7

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

Accepted Answer

Verify DNS settings in `/etc/resolv.conf` or configure a custom DNS server for the container runtime.. A DNS resolution error for `registry.redhat.io` indicates that the container runtime (e.g., Podman) cannot resolve the registry's hostname to an IP address. This is a network/DNS issue, not an authentication or caching problem. Verifying or correcting DNS settings in `/etc/resolv.conf` or configuring a custom DNS server for the container runtime directly addresses the root cause by ensuring the host or container runtime can resolve the registry's FQDN.

Answer

Run `podman login registry.redhat.io` to authenticate.

Answer

Restart the container runtime service.

Answer

Use the `--no-cache` flag to force a fresh build.

Question 8

An organization wants to include custom Python packages in their execution environment to support custom modules. Which method should be used to define these Python dependencies?

Accepted Answer

Create a `requirements.txt` file and reference it in the `execution-environment.yml` under `dependencies: python:`.. The `execution-environment.yml` file supports a `dependencies` key with a `python` subkey that points to a `requirements.txt` file. This is the standard method defined by the Ansible Builder specification for including custom Python packages in an execution environment, ensuring they are installed during the build process.

Answer

List them in the `galaxy-requirements.yml` file.

Answer

Use `ansible-navigator` to install them during runtime.

Answer

Add them to the `collection-requirements.yml` file.

Question 9

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?

Accepted Answer

Create a `pip.conf` file that uses environment variables or BuildKit secrets to inject credentials.. `ansible-builder` supports BuildKit secrets and environment variable injection via a `pip.conf` file, allowing credentials to be passed securely at build time without hardcoding them into the execution environment definition. This approach ensures that sensitive authentication tokens are not exposed in the `execution-environment.yml` or the generated `Containerfile`, and it mirrors the local developer workflow where environment variables or secret mounts are used.

Answer

Store the credentials in the Automation Hub token and reference it.

Answer

Add the credentials directly to the `Containerfile` that `ansible-builder` generates.

Answer

Include the credentials in the `execution-environment.yml` under `dependencies: python:`.

Question 10

A developer wants to create a new Ansible collection from a skeleton template. Which command should be used?

Accepted Answer

`ansible-galaxy collection init my_namespace.my_collection`. The correct command is `ansible-galaxy collection init my_namespace.my_collection`, which creates a new collection skeleton with the required directory structure and metadata files. This is the official Ansible command for bootstrapping a collection from a template.

Answer

`ansible-galaxy collection generate my_namespace.my_collection`

Answer

`ansible-galaxy collection create my_namespace.my_collection`

Answer

`ansible-galaxy collection start my_namespace.my_collection`

Question 11

Based on the exhibit, what is the purpose of the `galaxy` dependency entry?

Accepted Answer

Define which Ansible collections to install in the execution environment.. In the context of Ansible execution environments (EEs), the `galaxy` key within the `dependencies` section of the `execution-environment.yml` file specifies a list of Ansible collections to be installed from Ansible Galaxy or an Automation Hub. This allows the EE to include the necessary content collections required for playbook execution, ensuring all roles and modules are available inside the container.

Answer

Set the base container image.

Answer

Specify Python packages to install via pip.

Answer

Configure environment variables for the container.

Question 12

Based on the exhibit, which file is generated by `ansible-builder` to support the build?

Accepted Answer

Containerfile. The `ansible-builder` tool uses a definition file (typically `execution-environment.yml`) to construct a container image. During the build process, it generates a `Containerfile` (or `Dockerfile`) that contains the exact instructions for building the container image, such as base image selection, package installation, and collection inclusion. This generated file is the actual artifact that the container runtime (e.g., Podman or Docker) uses to create the execution environment image.

Answer

requirements.yml

Answer

execution-environment.yml

Answer

ansible.cfg

Question 13

A user wants to use a collection from Automation Hub. Which command downloads and installs the collection to the default collections path?

Accepted Answer

ansible-galaxy collection install. The correct command to download and install a collection from Automation Hub to the default collections path is `ansible-galaxy collection install`. This command uses the `ansible-galaxy` utility, which is the standard tool for managing Ansible roles and collections, and the `collection install` subcommand specifically handles collection installation from configured sources like Automation Hub or Ansible Galaxy.

Answer

ansible-pull collection install

Answer

ansible-playbook collection install

Answer

ansible-collection install

Question 14

An organization uses a private Automation Hub. A user has configured the server in ansible.cfg. Which command installs a collection from this server?

Accepted Answer

ansible-galaxy collection install my_namespace.my_collection. When the Automation Hub server is already configured in ansible.cfg under the [galaxy] section with the server_url and auth_url, the ansible-galaxy collection install command will automatically use that server and its authentication. No additional flags are needed; the command simply specifies the collection name in the format namespace.collection.

Answer

ansible-galaxy collection install my_namespace.my_collection --api-key=mykey

Answer

ansible-galaxy collection install my_namespace.my_collection --server=https://privatehub.example.com

Answer

ansible-galaxy collection download my_namespace.my_collection

Question 15

Which directory is the default location for installed Ansible collections on a control node for a regular user?

Accepted Answer

~/.ansible/collections. For a regular (non-root) user on an Ansible control node, the default location for installed collections is `~/.ansible/collections`. This is defined by Ansible's default collection search path, which includes the user's home directory under `~/.ansible/collections` for user-level installations. When a user runs `ansible-galaxy collection install` without specifying a custom path, the collection is placed in this directory by default.

Answer

/usr/share/ansible/collections

Answer

/etc/ansible/collections

Answer

/opt/ansible/collections