Ansible Automation Professional Standards & Competencies 2

Question 1

Which practice best demonstrates professional competency when writing Ansible roles for a team environment?

Accepted Answer

Following a consistent directory structure and documenting defaults in defaults/main.yml

Answer

Using Ansible's standard role directory structure and documenting defaults promotes maintainability and team collaboration.

Question 2

A colleague's playbook uses 'shell' module for every task. What is the professional standard recommendation?

Accepted Answer

Use purpose-built Ansible modules whenever available, falling back to shell only when necessary

Answer

Ansible's purpose-built modules are idempotent, handle errors consistently, and follow best practices compared to raw shell commands.

Question 3

What is the professional approach to handling secrets in Ansible playbooks committed to version control?

Accepted Answer

Use Ansible Vault to encrypt sensitive files before committing

Answer

Ansible Vault encrypts sensitive data so secrets can be safely stored in version control alongside playbooks.

Question 4

According to Ansible best practices, how should playbook task names be written?

Accepted Answer

Write descriptive, action-oriented names that clearly state what each task does

Answer

Descriptive task names improve readability, make play output understandable, and serve as inline documentation.

Question 5

What does the principle of idempotency require in a professionally written Ansible task?

Accepted Answer

Running the task multiple times produces the same result as running it once

Answer

Idempotency ensures that repeated playbook runs do not cause unintended changes when the system is already in the desired state.

Ansible Automation Practice Test