Ansible Automation Research & Evidence-Based Practice 2

Question 1

Which Ansible module is the recommended evidence-based approach for managing packages across multiple Linux distributions in a single playbook?

Accepted Answer

package

Answer

The `package` module is distribution-agnostic and lets a single task manage packages on any supported OS without conditional logic.

Question 2

What does the Ansible documentation recommend as the primary method to test a playbook's changes without applying them?

Accepted Answer

ansible-playbook --check

Answer

`ansible-playbook --check` runs a dry-run that predicts changes without modifying the target hosts.

Question 3

According to Ansible best practices, where should group-specific variables be stored to keep inventory readable?

Accepted Answer

In group_vars/ directories

Answer

The `group_vars/` directory is the recommended location for variables scoped to an inventory group.

Question 4

Which evidence-based practice does Ansible Galaxy promote for sharing reusable automation content?

Accepted Answer

Using roles and collections

Answer

Ansible Galaxy promotes roles and collections as the standard, shareable units of reusable automation.

Question 5

What is the best-practice reason for using `become: yes` at the task level rather than the play level?

Accepted Answer

It limits privilege escalation to only tasks that require it

Answer

Applying `become` at the task level follows the principle of least privilege by escalating only where necessary.

Ansible Automation Practice Test