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

Question 1

Which THREE actions are required to successfully publish a collection to Automation Hub?

Accepted Answer

Build the collection with ansible-galaxy collection build.. `ansible-galaxy collection build` is the required command to package a collection into a distributable tarball (e.g., `namespace-collection-1.0.0.tar.gz`). This tarball is the artifact that is then uploaded to Automation Hub. Without building the collection, there is no file to publish.

Answer

Sign the collection with GPG.

Answer

Run ansible-galaxy collection test.

Question 2

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.. An execution environment is a container image that includes all dependencies needed to run Ansible automation. For it to function correctly, the base image must contain `ansible-core` and `ansible-runner`, as these provide the core automation engine and the runner that manages playbook execution, respectively. Without these components, the container cannot execute Ansible jobs, making their presence a mandatory requirement.

Answer

The date of the last update.

Answer

The size of the image.

Answer

The number of layers.

Question 3

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 4

Refer to the exhibit. A user includes this in the execution-environment.yml. The build process fails because the second collection cannot be resolved. What is the most likely reason?

Accepted Answer

The source URL is not a valid Galaxy server endpoint.. The execution-environment.yml references a Galaxy server endpoint that is not a valid Ansible Galaxy server. Ansible Builder resolves collections from Galaxy servers, and if the URL does not point to a recognized Galaxy API endpoint (e.g., https://galaxy.ansible.com), the build process cannot fetch the collection. The error indicates the second collection cannot be resolved, which directly points to an invalid or unreachable Galaxy server URL.

Answer

The format of the version constraint is invalid.

Answer

The source URL does not include the required endpoint like '/api/v3/'.

Answer

The second collection is not authorized for download.

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

A developer is building an execution environment using `ansible-builder` and encounters the error: 'Error: Failed to pull base image: manifest for registry.redhat.io/ansible-automation-platform/ansible-builder-rhel8:2.0.0 not found: manifest unknown.' The developer checks the registry and verifies that the image exists with a different tag. Which action should the developer take to resolve the issue?

Accepted Answer

Change the tag in `execution-environment.yml` to a valid tag, such as 'latest'.. The error indicates the specified tag '2.0.0' does not exist in the registry. The developer confirmed the image exists with a different tag, so updating the tag in `execution-environment.yml` to a valid one, such as 'latest', resolves the manifest lookup failure. `ansible-builder` uses this file to define the base image and tag for building the execution environment.

Answer

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

Answer

Modify the `execution-environment.yml` to use a different base image from Docker Hub.

Answer

Update the container runtime to the latest version.

Question 7

An organization wants to share a collection internally across multiple teams while ensuring that each team can only use specific modules from the collection. Which approach best supports this requirement?

Accepted Answer

Create separate collections for each team and publish them to the private Automation Hub.. It uses separate collections published to a private Automation Hub, which allows each team to access only the specific collection containing the modules they need. This approach leverages Automation Hub's role-based access control (RBAC) to enforce team-specific permissions, ensuring that teams cannot see or use modules from other collections.

Answer

Use a single collection and annotate modules with metadata to restrict access.

Answer

Store the collection in a Git repository and use branch permissions to hide modules.

Answer

Publish a single collection with all modules and rely on documentation to indicate which modules are for which team.

Question 8

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 9

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 10

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 11

A developer has created a collection and needs to publish it to a private Automation Hub. Which command should be used to upload the collection archive?

Accepted Answer

`ansible-galaxy collection publish ./my-namespace-my_collection-1.0.0.tar.gz`. The correct command to upload a collection archive to a private Automation Hub is `ansible-galaxy collection publish ./my-namespace-my_collection-1.0.0.tar.gz`. This command authenticates to the configured Automation Hub server (as defined in `ansible.cfg` or the `--server` flag) and publishes the tarball, making it available for other users to install. The `publish` subcommand is specifically designed for this purpose, handling the API call to the Galaxy or Automation Hub server.

Answer

`ansible-galaxy collection server upload ./tar.gz`

Answer

`ansible-galaxy role import my-namespace my_collection`

Answer

`ansible-galaxy collection upload ./my-namespace-my_collection-1.0.0.tar.gz`

Question 12

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 13

A team uses `ansible-navigator` to run playbooks with an execution environment. The playbook requires a collection that is not included in the execution environment. Which approach allows the team to use the collection without rebuilding the execution environment?

Accepted Answer

Set the `ANSIBLE_COLLECTIONS_PATHS` environment variable to a directory containing the collection and use `--execution-environment-image` with the EE.. Setting the `ANSIBLE_COLLECTIONS_PATHS` environment variable tells `ansible-navigator` to look for collections in a specified directory on the host, and using `--execution-environment-image` ensures the correct execution environment image is used. This allows the team to inject a collection into the container at runtime without modifying the execution environment image itself, as `ansible-navigator` mounts the specified host directory into the container automatically.

Answer

Use the `--container-options` flag to mount a volume with the collection.

Answer

Use `ansible-galaxy collection install` inside the execution environment at runtime.

Answer

Rebuild the execution environment with the collection included.

Question 14

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 15

Which TWO of the following are required in a valid Ansible collection directory structure?

Accepted Answer

`galaxy.yml` file. The `galaxy.yml` file is mandatory in a valid Ansible collection directory structure because it serves as the metadata file that defines the collection's name, version, author, and dependencies. Without this file, the collection cannot be properly built, published, or installed via `ansible-galaxy`. It is the equivalent of a package manifest for the collection.

Answer

`tests/` directory

Answer

`docs/` directory

Answer

`roles/` directory