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

Question 1

Which THREE of the following are valid directives that can be used in an `execution-environment.yml` file for `ansible-builder`?

Accepted Answer

`version:`. `version:` is a valid directive in an `execution-environment.yml` file for ansible-builder. It specifies the version of the execution environment definition format, ensuring compatibility with the builder tool. This directive is used at the top level of the file to declare the schema version, such as `version: 1`.

Answer

`system_packages:`

Answer

`python_requirements:`

Question 2

Which TWO of the following are valid methods to install a collection from a private Automation Hub?

Accepted Answer

Configure `server_list` in `ansible.cfg` under `[galaxy]` with the Automation Hub URL and then run `ansible-galaxy collection install my_namespace.my_collection`.. Configuring the `server_list` in `ansible.cfg` under the `[galaxy]` section allows you to define multiple Galaxy servers, including a private Automation Hub. Once configured, `ansible-galaxy collection install` will automatically use the specified server list to resolve and install the collection. Option D is also correct because the `--server` flag directly specifies the Automation Hub URL, overriding any default server configuration for that single command.

Answer

`ansible-galaxy collection install my_namespace.my_collection --server automationhub`

Answer

`ansible-navigator run --pp never --pull-policy missing -- ... `

Answer

Download the tarball and place it in the `collections/` directory of the role path.

Question 3

Based on the exhibit, which collection provides modules for managing Red Hat Insights subscriptions?

Accepted Answer

`redhat.insights`. The `redhat.insights` collection is the official Ansible collection from Red Hat that provides modules specifically for managing Red Hat Insights subscriptions, including `insights_register` and `insights_unregister`. This collection is maintained by Red Hat and is the correct source for automating Insights registration and subscription management tasks.

Answer

`community.general`

Answer

`ansible.posix`

Answer

`insights`

Question 4

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 5

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 6

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 7

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 8

An execution environment is built using ansible-builder. The definition file includes a base image from registry.redhat.io. After building, the container runs but ansible-navigator can't find the EE. What is the most likely cause?

Accepted Answer

The EE was not pushed to a registry accessible by ansible-navigator.. The most likely cause is that the execution environment (EE) was built locally but not pushed to a registry that `ansible-navigator` can access. By default, `ansible-navigator` pulls EEs from a container registry (e.g., `registry.redhat.io` or a private registry) specified in its configuration; it does not automatically discover locally built images. If the EE is only present in the local Docker/Podman store, `ansible-navigator` will fail to find it, resulting in a runtime error.

Answer

ansible-navigator uses a different Python interpreter.

Answer

The base image is not compatible with the installed collections.

Answer

The EE was not tagged correctly.

Question 9

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

Question 10

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 11

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 12

Which command runs a playbook using an execution environment named 'my-ee'?

Accepted Answer

ansible-navigator run playbook.yml --execution-environment my-ee. Both Option A and Option D are correct because `ansible-navigator run` supports both the full flag `--execution-environment` and its shorthand `--ee` to specify an execution environment. Option A uses the full flag, while Option D uses the shorthand; both are valid. Options B and C are incorrect because `ansible-playbook` does not support execution environments directly, and `ansible-runner` is a different tool typically used in automation controller environments, not directly for running playbooks with execution environments in the same manner.

Answer

ansible-playbook -i inventory playbook.yml -e 'ansible_python_interpreter=/usr/bin/python3' --ee my-ee

Answer

ansible-runner run --ee my-ee playbook.yml

Question 13

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 14

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 15

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.. Required because you must configure the private Automation Hub server in ansible.cfg under [galaxy] server_list to tell ansible-galaxy where to find collections. Option E is required because you need an API token for authentication, stored in ansible.cfg or as an environment variable; without it, access to the private hub is denied. Option B (building a custom execution environment) is optional and not a prerequisite for sharing collections – it is used for distributing collections in EEs. Option C (--ignore-certs) is only necessary if you use self-signed certificates, not a general requirement. Option D (ansible-navigator with --pull-policy missing) relates to pulling EEs, not to sharing collections from a private hub.

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.