Ansible Collections Flashcards

Which command installs an Ansible collection from Ansible Galaxy?

Answer: ansible-galaxy collection install namespace.collection

The correct syntax is `ansible-galaxy collection install namespace.collection`, which downloads and installs the specified collection from Galaxy.

Where are Ansible Collections stored by default when installed via ansible-galaxy for a non-root user?

Answer: ~/.ansible/collections

By default, ansible-galaxy installs collections to ~/.ansible/collections unless overridden by the COLLECTIONS_PATHS setting in ansible.cfg.

What metadata file at the root of an Ansible Collection defines its namespace, name, version, and dependencies?

Answer: galaxy.yml

galaxy.yml is the primary metadata file for an Ansible Collection and is required for building and publishing to Ansible Galaxy.

Within an Ansible Collection's directory structure, where should custom modules be placed?

Answer: plugins/modules/

Custom modules in a collection live under plugins/modules/ because modules are treated as a plugin type in the collection layout.

What is the correct way to reference a module from an installed collection named 'myns.mycol' in a playbook task?

Answer: myns.mycol.my_module:

Collection modules are referenced using the Fully Qualified Collection Name (FQCN) as the task's module key: `myns.mycol.my_module:`.

Which file is used with `ansible-galaxy collection install -r` to install multiple collections at once?

Answer: requirements.yml

requirements.yml lists collections (and optionally roles) with their versions so that `ansible-galaxy collection install -r requirements.yml` can install all of them.

In which Ansible release were Collections first introduced as a stable, supported feature?

Answer: Ansible 2.9

Ansible Collections became a stable feature in Ansible 2.9, replacing the older approach of bundling everything in the core Ansible package.