Ansible Automation Quality Control & Assurance 5

Question 1

Which approach helps catch regressions when updating shared Ansible roles used by multiple teams?

Accepted Answer

Tagging role versions and running Molecule tests in CI before releasing a new version

Answer

Version-tagging roles and gating releases behind automated Molecule tests in CI ensures changes don't silently break consumers of shared roles.

Question 2

What does the `delegate_to: localhost` pattern enable in a quality assurance workflow?

Accepted Answer

Runs a task on the control node instead of the managed host, useful for API calls or local checks

Answer

`delegate_to: localhost` redirects task execution to the Ansible control node, commonly used for calling external APIs or running local validation scripts.

Question 3

Which Ansible-lint profile provides the strictest set of rules for enterprise-grade playbook quality?

Accepted Answer

safety

Answer

The `safety` profile enforces rules focused on preventing dangerous patterns and is recommended for production-grade Ansible code.

Question 4

What is the function of `meta: flush_handlers` in a quality assurance context?

Accepted Answer

Forces all pending handlers to run immediately at that point in the play

Answer

`meta: flush_handlers` triggers queued handlers immediately rather than waiting until the end of the play, enabling mid-play service restarts followed by verification tasks.

Question 5

In Ansible Tower / AWX, which feature allows automated quality gate enforcement before a job template runs in production?

Accepted Answer

Approval workflows on job templates

Answer

Approval workflows require a designated user or team to manually approve a job before it executes, providing a human quality gate for critical environments.

Ansible Automation Practice Test

Ansible Automation Practice Test

Ansible Automation Quality Control & Assurance 5