Ansible Automation Research & Evidence-Based Practice 5

Question 1

Which evidence-based practice does Ansible's collection structure enforce compared to standalone roles?

Accepted Answer

Collections bundle roles, modules, plugins, and documentation into a versioned, distributable unit

Answer

Collections package all related automation content together with versioning, enabling reproducible, shareable automation at scale.

Question 2

What is the best-practice way to ensure an Ansible execution environment is reproducible across different control nodes?

Accepted Answer

Use an execution environment image built with ansible-builder

Answer

`ansible-builder` creates container-based execution environments that bundle Ansible, collections, and Python dependencies into a portable image.

Question 3

According to Ansible's security research guidance, what is the risk of using `no_log: false` on tasks that handle secrets?

Accepted Answer

Sensitive values will appear in verbose output and log files

Answer

Without `no_log: true`, sensitive module arguments are printed in Ansible's verbose output and stored in any configured log file.

Question 4

What does the Ansible community identify as the primary benefit of using `delegate_to` in a playbook?

Accepted Answer

Executing a task on a different host than the one currently being iterated

Answer

`delegate_to` redirects task execution to a specified host while still using the current host's variables, useful for registration or load-balancer operations.

Question 5

Which Ansible practice does the `molecule` framework support in evidence-based role development?

Accepted Answer

Testing roles in isolated environments with multiple verifier options

Answer

Molecule provides a testing harness for Ansible roles, spinning up instances, applying the role, and running verifiers like Testinfra or Ansible itself.

Ansible Automation Practice Test

Ansible Automation Practice Test

Ansible Automation Research & Evidence-Based Practice 5