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

Question 1

An automation engineer has written a custom Ansible role called `db_deploy` and wants to package it inside a new collection named `acme.database`. Which command initializes the collection skeleton with the correct directory layout for roles, modules, and plugins?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

ansible-galaxy collection init acme.database. Scaffolding a new collection requires the dedicated `ansible-galaxy collection init` subcommand, which generates the namespace/name directory tree plus a `galaxy.yml` manifest. Role initialization, building, and installing all operate on artifacts that already exist and therefore cannot produce the initial skeleton needed before a custom role is placed under `roles/`.

Answer

ansible-galaxy role init acme.database

Answer

ansible-galaxy collection build acme.database

Answer

ansible-galaxy collection install acme.database

Question 2

A platform team maintains an execution environment definition where `requirements.yml` lists several collections. They need to pin `community.general` to a specific version range so that only releases from 7.0.0 up to but not including 8.0.0 are installed during the build. Which syntax inside `requirements.yml` accomplishes this?

Accepted Answer

- name: community.general
  version: ">=7.0.0,<8.0.0". Ansible collection requirements use the `version` key with Python-style comparison operators. Combining a lower bound and an exclusive upper bound in a single quoted string yields the desired 7.x-only range, which is the only syntax among the choices that the resolver actually understands when building the execution environment.

Answer

- name: community.general
  version: "^7.0.0"

Answer

- name: community.general
  version_range: ">=7.0.0 <8.0.0"

Answer

- name: community.general
  version: "7.x"

Question 3

An automation engineer is preparing an execution environment for a project that requires the `community.general` collection and the `netaddr` Python library. The engineer has created an `execution-environment.yml` file in the project directory. Which command should be used to build the execution environment image?

Accepted Answer

ansible-builder build --file execution-environment.yml. The `ansible-builder build` command is the correct tool to create an execution environment image from an `execution-environment.yml` definition. It parses the definition, installs collections and Python dependencies, and produces a container image. Other commands like `ansible-galaxy collection build` or `podman build` serve different purposes and do not automate the execution environment creation process.

Answer

ansible-galaxy collection build

Answer

ansible-navigator build execution-environment.yml

Answer

podman build -t my-ee:latest .

Question 4

A developer is creating a new content collection named `acme.automation` and wants to ensure that the collection is structured correctly for distribution. After running `ansible-galaxy collection init acme.automation`, which directory should contain the custom Ansible modules that the collection will provide?

Accepted Answer

`plugins/modules/`. Ansible collections organize plugins by type. Modules are a type of plugin and belong in `plugins/modules/`. This structure allows Ansible to load modules from the collection namespace. Other directories like `roles/` or `library/` serve different purposes and are not scanned for collection modules. Using the correct directory is essential for the collection to work as intended.

Answer

`roles/modules/`

Answer

`modules/`

Answer

`library/`

Question 5

A developer is creating a new content collection and wants to include a custom module that requires the `requests` Python library. The collection will be used in an execution environment. Where should the developer declare this Python dependency so that it is automatically installed when the execution environment is built?

Accepted Answer

In the `execution-environment.yml` file under the `dependencies` section with a `python` key.. Python dependencies for an execution environment are declared in the `execution-environment.yml` file under the `dependencies` section, using the `python` key to list packages or a requirements file. This allows `ansible-builder` to install them during the build process. Other files like `galaxy.yml` or `meta/runtime.yml` serve different purposes and do not trigger Python package installation.

Answer

In a `requirements.txt` file at the root of the collection.

Answer

In the collection's `meta/runtime.yml` file under `requires_ansible`.

Answer

In the collection's `galaxy.yml` file under a `dependencies` key.

Question 6

You are creating a new Ansible content collection named 'acme.corp' using the ansible-galaxy collection init command. After running the command, you need to add a module that will be part of this collection. Where should you place the module file within the collection directory structure?

Accepted Answer

In the plugins/modules directory.. Ansible collections have a defined structure where plugins, including modules, are stored under the plugins directory. Modules specifically go in plugins/modules. This structure allows Ansible to automatically discover and load the module when the collection is installed, making it available for use in playbooks via the collection's fully qualified name.

Answer

In the roles directory under a role named after the module.

Answer

In the library directory at the root of the collection.

Answer

In the modules directory at the root of the collection.

Question 7

An administrator needs to create a new Ansible content collection named `myorg.automation` that will contain roles and modules. Which command initializes the collection directory structure with the required skeleton files?

Accepted Answer

ansible-galaxy collection init myorg.automation. The `ansible-galaxy collection init` command is the correct way to create a new collection skeleton. It sets up the directory structure with the namespace and collection name, and generates essential files like `galaxy.yml` and `README.md`. Other commands either initialize roles (`ansible-galaxy init`) or serve entirely different purposes.

Answer

ansible-playbook --init-collection myorg.automation

Answer

ansible-galaxy init myorg.automation

Answer

ansible-builder init myorg.automation

Question 8

Your team maintains a collection that depends on a module requiring the Python library netaddr. You are building an execution environment with ansible-builder and need that library available inside the image at run time. The collection itself is installed from a private Automation Hub. Which approach ensures the Python dependency is present in the execution environment?

Accepted Answer

Add netaddr to the requirements.txt referenced by the dependencies.python section of execution-environment.yml.. Python libraries needed by modules must be installed into the execution environment image during the build. The dependencies.python section of execution-environment.yml references a pip requirements file, and listing netaddr there causes ansible-builder to install it into the image. Collection metadata and Galaxy dependency lists do not install Python packages, and installing on the control node has no effect inside the container.

Answer

List netaddr under dependencies.galaxy in execution-environment.yml so ansible-galaxy installs it with the collection.

Answer

Install netaddr on the control node and rely on the module using the control node's Python environment.

Answer

Add netaddr to the collection's runtime.yml under the requires_ansible key.

Question 9

You are building an execution environment using ansible-builder with a definition that includes a base image and a list of collections. During the build, you need to run a custom shell command to install an additional system package that is not available via the standard package manager configuration. Which section of the execution-environment.yml file should you use to add this custom build step?

Accepted Answer

additional_build_steps. The additional_build_steps section is designed to inject custom commands into the execution environment build process. It supports stages like prepend_base, append_base, prepend_galaxy, etc., allowing you to run shell commands before or after key build phases. This is the correct way to install system packages or perform other customizations that are not handled by the standard dependencies section.

Answer

options

Answer

dependencies

Answer

build_arg_defaults

Question 10

A developer is creating a new content collection named acme.tools to distribute internal modules and roles. Which command initializes the collection with the standard directory skeleton, including the galaxy.yml metadata file?

Accepted Answer

ansible-galaxy collection init acme.tools. To scaffold a new collection, use ansible-galaxy collection init followed by the namespace and collection name. This generates the standard directory layout and the galaxy.yml metadata file that describes the collection. Other ansible-galaxy subcommands such as build and publish operate on an existing collection, and ansible-builder is unrelated to collection initialization.

Answer

ansible-galaxy collection create acme.tools

Answer

ansible-builder create acme.tools

Answer

ansible-galaxy init acme.tools --type collection

Question 11

You are preparing to publish a new version of a content collection to a private Automation Hub. The collection includes several roles and modules. Before publishing, you need to ensure the collection is properly built and packaged. Which two commands are required to build and publish the collection? (Choose two.)

Accepted Answer

ansible-galaxy collection build. To publish a collection to Automation Hub, you first build it into a tarball using ansible-galaxy collection build, then publish that tarball using ansible-galaxy collection publish. These two commands form the standard build and publish workflow, ensuring the collection is packaged correctly and uploaded to the repository.

Answer

ansible-galaxy collection install

Answer

ansible-galaxy collection verify

Answer

ansible-galaxy collection init

Question 12

You are developing a content collection and need to include a custom Ansible module that requires a specific Python library. The library is not available as a system package and must be installed via pip. Where should you declare this Python dependency so that it is automatically installed when the collection is used in an execution environment?

Accepted Answer

In the execution-environment.yml file under the dependencies section with the python option.. When building an execution environment, Python dependencies can be declared in the execution-environment.yml file under the dependencies section with the python key. This instructs ansible-builder to install the specified Python packages via pip into the execution environment, making them available to modules and plugins that require them.

Answer

In the galaxy.yml file under the dependencies key, specifying the Python package name.

Answer

In the module file itself, using a try/except ImportError block to install the library at runtime.

Answer

In the requirements.txt file within the collection root.

Question 13

A build of an execution environment fails with an error that ansible-builder cannot find the collection acme.internal.utils in any configured Galaxy server. The collection exists on the private Automation Hub, and the build host can reach it. The execution-environment.yml lists the collection under dependencies.galaxy pointing to requirements.yml. What is the most likely cause?

Accepted Answer

The ansible.cfg used by ansible-builder does not define the private Automation Hub as a Galaxy server with valid credentials.. The error indicates the collection cannot be found in any configured Galaxy server. Since the collection exists on the private Automation Hub and the host can reach it, the most likely cause is that the ansible.cfg used by ansible-builder does not define that Hub with valid credentials. Without the server URL and token, the builder cannot authenticate and will not see the collection.

Answer

The collection name in requirements.yml must be prefixed with the Galaxy server name, such as hub_internal.acme.internal.utils.

Answer

The execution environment base image does not include ansible-galaxy, so collection installation is skipped.

Answer

The collection version in requirements.yml is pinned to a version that does not exist on the private Automation Hub.

Question 14

An administrator is creating a new execution environment and wants to use a minimal base image provided by Red Hat that includes `ansible-core` and essential Python libraries. Which base image should be specified in the `execution-environment.yml` file?

Accepted Answer

`registry.redhat.io/ansible-automation-platform-23/ee-minimal-rhel8:latest`. Red Hat offers minimal execution environment base images specifically designed for Ansible Automation Platform. The `ee-minimal-rhel8` image includes `ansible-core` and required Python libraries, providing a supported and optimized foundation. Other images either lack Ansible components or are not minimal for this purpose. Using the Red Hat-provided minimal image simplifies the build and ensures compatibility.

Answer

`quay.io/ansible/ansible-runner:latest`

Answer

`registry.access.redhat.com/ubi8/ubi:latest`

Answer

`docker.io/library/python:3.9-slim`

Question 15

A developer is preparing a collection for distribution and must declare its metadata, including version, license, and the list of collections it depends on. Which file at the collection root contains these declarations?

Accepted Answer

galaxy.yml. The manifest that describes a collection to Galaxy and to dependency resolution is `galaxy.yml`, which holds version, license, and the `dependencies` mapping. Runtime requirements live elsewhere, and consumer-side requirement files are unrelated to how the collection itself is described when packaged.

Answer

requirements.yml

Answer

meta/runtime.yml

Answer

plugins/README.md