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

Question 1

An automation team is designing a content collection to distribute internal Ansible modules across the organization. The collection should be installed from a private Galaxy server. To minimize namespace conflicts and ensure discoverability, which naming convention should be used for the collection?

Accepted Answer

namespace.collection_name. In Ansible, collections are distributed using a fully qualified collection name (FQCN) in the format `namespace.collection_name`. This naming convention is required by the Ansible Galaxy server and the `ansible-galaxy collection install` command to uniquely identify and install collections, minimizing namespace conflicts and ensuring discoverability across the organization.

Answer

collection_name.namespace

Answer

namespace_collection_name

Answer

namespace-collection_name

Question 2

When building an execution environment with ansible-builder, a developer notices that the build process fails with an error about missing dependencies. The developer wants to ensure all required Python packages are installed in the execution environment. Which file should be used to specify additional Python packages?

Accepted Answer

requirements.txt. In Ansible Builder, the `requirements.txt` file is used to specify additional Python packages that should be installed in the execution environment. When building an execution environment, Ansible Builder reads this file and installs the listed packages via pip, ensuring all required Python dependencies are present.

Answer

meta/runtime.yml

Answer

galaxy.yml

Answer

bindep.txt

Question 3

A system administrator wants to publish a custom Ansible collection to a private Automation Hub. What is the correct command to build the collection before publishing?

Accepted Answer

ansible-galaxy collection build. Option D is correct because `ansible-galaxy collection build` is the command that compiles the collection directory into a distributable tarball (e.g., `mycollection-1.0.0.tar.gz`), which is the required artifact for publishing to a private Automation Hub. Without this build step, there is no archive to upload.

Answer

ansible-galaxy collection init mycollection

Answer

ansible-galaxy collection publish ./mycollection-1.0.0.tar.gz

Answer

ansible-galaxy collection install .

Question 4

An organization uses custom Ansible plugins stored in a collection. A junior admin reports that after updating the collection to version 2.0.0, a playbook that uses a custom filter plugin fails with 'undefined filter'. What is the most likely cause?

Accepted Answer

The filter plugin was placed in the wrong directory inside the collection.. In Ansible collections, filter plugins must reside in the `plugins/filter/` directory within the collection structure. If the plugin is placed in the wrong directory (e.g., `plugins/modules/` or `plugins/lookup/`), Ansible will not load it as a filter, resulting in an 'undefined filter' error. The collection update to version 2.0.0 likely reorganized the directory structure, causing the filter to be misplaced.

Answer

The playbook uses an outdated syntax that is incompatible with the new collection.

Answer

The playbook does not use the fully qualified collection name (FQCN) for the filter.

Answer

The collection's metadata file galaxy.yml is missing a dependency declaration.

Question 5

A DevOps engineer is creating an execution environment for a team that needs both Ansible and the 'requests' Python library. The engineer creates an execution environment definition file (EE.yml) with the following content:
---
version: 3
images:
  base_image:
    name: registry.redhat.io/ansible-automation-platform-22/ee-minimal-rhel8:latest
options:
  package_manager_path: /usr/bin/microdnf
dependencies:
  python: requirements.txt
  system: bindep.txt

What is missing from this definition to ensure the 'requests' library is installed?

Accepted Answer

The requirements.txt file must contain 'requests'.. The execution environment definition file (EE.yml) specifies dependencies via external files like requirements.txt for Python packages. To install the 'requests' library, the requirements.txt file must explicitly list 'requests' as a dependency. Without it, the build process will not include the library, regardless of other configuration options.

Answer

The package_manager_path should be /usr/bin/yum.

Answer

The galaxy.yml file must be added to the dependencies section.

Answer

The base image should be ee-supported-rhel8 instead.

Question 6

Which TWO statements about Ansible content collections are correct?

Accepted Answer

Collections can be distributed via Automation Hub or Galaxy.. Option C is correct because Ansible content collections can be distributed via either Red Hat Automation Hub (for certified collections) or Ansible Galaxy (for community collections). This dual distribution model allows organizations to use curated, supported content from Automation Hub while also leveraging community-contributed collections from Galaxy.

Answer

Collections can be installed only from Galaxy.

Answer

The collection name must be a single word without namespace.

Answer

A collection can contain only roles and playbooks.

Question 7

Which THREE files are commonly used when building an execution environment with ansible-builder?

Accepted Answer

bindep.txt. Option A is correct because `bindep.txt` is one of the three files that `ansible-builder` uses by default to define system-level package dependencies (e.g., `libffi-devel`, `python3-devel`) that must be installed in the execution environment image. Along with `execution-environment.yml` (the main recipe file) and `requirements.txt` (Python package dependencies), `bindep.txt` is automatically consumed during the build process to ensure the container has the necessary OS packages.

Answer

ansible.cfg

Answer

galaxy.yml

Question 8

A user wants to run a playbook that uses a module from 'myorg.mycollection'. The playbook is located in /home/user/projects. Which of the following is true about the collection discovery?

Accepted Answer

Ansible will automatically find the collection in the default search path.. Option D is correct because Ansible automatically searches for collections in the default search path, which includes the collections directory adjacent to the playbook. Since the playbook is located in /home/user/projects, Ansible will look in /home/user/projects/collections/ansible_collections/myorg/mycollection, among other default paths, without requiring any environment variable or manual configuration.

Answer

The user must set the ANSIBLE_COLLECTIONS_PATH environment variable.

Answer

The collection is not installed, so the playbook will fail.

Answer

Ansible will look only in /usr/share/ansible/collections.

Question 9

What is the most likely cause of the build failure?

Accepted Answer

The base image already includes python3-devel, causing a conflict with the bindep.txt entry.. The build failure is most likely caused by a conflict between the base image's pre-installed python3-devel package and the bindep.txt entry that also specifies python3-devel. In Ansible Builder, bindep.txt lists system packages to install via dnf, but if the base image already includes that package, the build process may fail due to duplicate or conflicting package manager operations, especially if the base image uses a different package version or repository configuration.

Answer

The package_manager_path should be /usr/bin/dnf.

Answer

The version field in execution-environment.yml is incorrect.

Answer

The base image name is misspelled.

Question 10

You are an automation engineer at a large enterprise. The company uses Ansible Automation Platform 2.x and has a private Automation Hub server. The security team mandates that all execution environments must be built from a hardened base image that has been approved by the security team. The base image is stored in a private container registry at registry.internal.company.com/hardened-ee:latest. You need to create an execution environment that includes a custom collection 'company.tools' which is hosted on the private Automation Hub. Additionally, the execution environment must include the Python library 'cryptography' version 3.4.8. You have created the following files:

execution-environment.yml:
---
version: 3
images:
  base_image:
    name: registry.internal.company.com/hardened-ee:latest
options:
  package_manager_path: /usr/bin/microdnf
dependencies:
  galaxy: requirements.yml
  python: requirements.txt

requirements.yml:
---
collections:
  - name: company.tools
    source: https://automationhub.company.com/api/galaxy/content/private/

requirements.txt:
cryptography==3.4.8

When you run 'ansible-builder build -f execution-environment.yml', the build fails with an error: 'Error: Failed to resolve dependency cryptography==3.4.8'. Based on this scenario, what is the most likely cause of the failure?

Accepted Answer

The base image already includes cryptography but not version 3.4.8, causing a version conflict.. Option B is correct because the error 'Failed to resolve dependency cryptography==3.4.8' indicates a version conflict with the Python cryptography library already present in the hardened base image. The base image likely includes a different version of cryptography, and pip cannot satisfy the pinned version constraint due to conflicts with the pre-installed package. Ansible Builder uses pip to install Python dependencies, and if the base image has a conflicting version, the build fails unless the dependency is unpinned or the base image is adjusted.

Answer

The requirements.yml file has an incorrect source URL for the private Automation Hub.

Answer

The execution-environment.yml is missing the 'system' dependency section for bindep.txt.

Answer

The package_manager_path should be /usr/bin/dnf instead of microdnf.

Question 11

An admin wants to build an execution environment using ansible-builder. Which file is required to define the base image and additional Python dependencies?

Accepted Answer

execution-environment.yml. Option A is correct because `execution-environment.yml` is the required file for `ansible-builder` to define the base image (via the `base_image` field) and additional Python dependencies (via the `python` section under `dependencies`). This YAML file serves as the build definition that `ansible-builder` reads to construct the container image, making it essential for creating custom execution environments.

Answer

requirements.yml

Answer

galaxy.yml

Answer

Dockerfile

Question 12

A team develops an Ansible collection and wants to distribute it internally. They have a private Automation Hub. Which approach best ensures that collection dependencies from external sources are also available?

Accepted Answer

Define a requirements.yml in the execution environment that references both the private hub and external sources. Option B is correct because defining a `requirements.yml` in the execution environment allows you to specify collections from both the private Automation Hub and external sources (e.g., Ansible Galaxy). When building the execution environment, `ansible-builder` processes this file and resolves dependencies from the listed sources, ensuring all required collections are bundled into the container image. This approach automates dependency management and avoids manual installation or repository bloat.

Answer

Manually install each dependency on the control node

Answer

Include all dependencies directly in the collection's repository

Answer

Use ansible-galaxy collection download and then upload to private hub

Question 13

Which TWO statements are true about Ansible content collections?

Accepted Answer

Collections can be installed from Automation Hub, Galaxy, or a Git repository.. Option A is correct because Ansible collections can be installed from multiple sources: Automation Hub (a Red Hat curated repository), Galaxy (the community repository), or directly from a Git repository using the `ansible-galaxy collection install` command with a Git URL. This flexibility allows users to leverage curated, community, or custom collections as needed.

Answer

Collections cannot contain playbooks.

Answer

A role stored in a collection can be referenced by its short name without the collection prefix.

Answer

Execution environments are required to use collections.

Question 14

An admin attempts to build an execution environment using the exhibited files. The build fails with an error about incompatible Python dependency. What is the most likely cause?

Accepted Answer

The Python requirements.txt tries to install a version of Ansible that conflicts with the version in the base image.. The build fails because the Python `requirements.txt` file attempts to install a version of Ansible that conflicts with the version already present in the base image `ee-minimal-rhel8`. Execution environments are designed to include a specific Ansible version in the base image; adding a different version via pip creates a dependency conflict that breaks the build.

Answer

The execution-environment.yml file uses incorrect syntax for the 'dependencies' section.

Answer

The collections in requirements.yml are not fully qualified.

Answer

The base image 'ee-minimal-rhel8' is not a valid execution environment base image.

Question 15

Your organization uses Ansible Automation Platform 2.2 with private Automation Hub. You have developed a custom collection named 'my_company.network' that depends on 'cisco.ios' and 'vyos.vyos'. The collection is published in your private hub. You are building an execution environment using ansible-builder. The execution-environment.yml specifies 'EE_BASE_IMAGE: registry.redhat.io/ansible-automation-platform-22/ee-supported-rhel8:latest'. The dependencies section points to a requirements.yml file that includes your collection. When you run 'ansible-builder build', the build succeeds, but when running a playbook that uses modules from 'cisco.ios', you get an error 'module not found'. What is the most likely reason and the correct action to resolve it?

Accepted Answer

Add 'cisco.ios' to the requirements.yml file used during the execution environment build. The execution environment build process uses the requirements.yml file to determine which collections to include in the image. If the custom collection 'my_company.network' depends on 'cisco.ios', but that dependency is not explicitly listed in the requirements.yml, the builder will not include 'cisco.ios' in the execution environment. Adding 'cisco.ios' to the requirements.yml ensures it is installed during the build, making the module available at runtime.

Answer

Reinstall the collection on the controller node using 'ansible-galaxy collection install'

Answer

Use a different base image that includes 'cisco.ios'

Answer

Update the collection metadata to include dependencies and rebuild