Ansible Automation Ansible Collections 3

Question 1

What is the primary purpose of the `meta/runtime.yml` file in an Ansible Collection?

Accepted Answer

Specifies the minimum Ansible version required and can define routing or deprecation redirects

Answer

meta/runtime.yml declares the minimum supported Ansible version (requires_ansible) and can redirect or deprecate module names within the collection for backward compatibility.

Question 2

Which of the following is a valid Ansible Collection identifier (namespace and name)?

Accepted Answer

my_namespace.my_collection

Answer

Ansible Collection names must follow lowercase snake_case for both namespace and collection name, separated by a dot: namespace.collection_name.

Question 3

In a `requirements.yml` file, how do you install a collection from a private Automation Hub instead of the public Galaxy?

Accepted Answer

Add a `source:` key in the collection entry pointing to the private Hub URL

Answer

The `source:` key in a requirements.yml collection entry allows you to specify an alternate Galaxy-compatible server URL, such as a private Automation Hub.

Question 4

What effect does the `--upgrade` flag have when running `ansible-galaxy collection install`?

Accepted Answer

Updates installed collections to the latest versions satisfying version constraints

Answer

The --upgrade flag instructs ansible-galaxy to check for and install newer versions of already-installed collections, similar to `pip install --upgrade`.

Question 5

In a collection's `galaxy.yml`, which field lists other collections this collection requires at runtime?

Accepted Answer

dependencies

Answer

The `dependencies` field in galaxy.yml maps other collection FQCNs to their required version ranges, and ansible-galaxy uses this to automatically install transitive dependencies.

Ansible Automation Practice Test

Ansible Automation Practice Test

Ansible Automation Ansible Collections 3