Ansible Automation Professional Standards & Competencies 3

Question 1

What is the recommended professional approach for organizing Ansible inventory in a multi-environment setup?

Accepted Answer

Separate inventory directories per environment (dev, staging, prod) with consistent group structures

Answer

Separate inventory directories prevent cross-environment accidents and allow environment-specific variables to be clearly scoped.

Question 2

Which competency is reflected when an engineer writes a molecule test for a new Ansible role?

Accepted Answer

Role testing and quality assurance

Answer

Molecule is the standard testing framework for Ansible roles, validating role behavior in isolated environments before deployment.

Question 3

When should an Ansible professional use 'block' with 'rescue' and 'always' sections?

Accepted Answer

When grouping tasks that may fail and require cleanup or error-handling logic

Answer

Block/rescue/always provides structured error handling similar to try/catch/finally, enabling graceful failure management.

Question 4

A professional decides to use 'include_tasks' instead of 'import_tasks'. What is the key difference driving this decision?

Accepted Answer

include_tasks is dynamic and allows conditional inclusion at runtime; import_tasks is static

Answer

include_tasks is processed dynamically at runtime, enabling conditional and looped task inclusion, while import_tasks is statically loaded at parse time.

Question 5

What professional standard should guide the use of 'become: true' in Ansible tasks?

Accepted Answer

Apply become only to specific tasks that require elevated privileges, following least-privilege principles

Answer

Least-privilege principle dictates that privilege escalation should be scoped as narrowly as possible to reduce security risk.

Ansible Automation Practice Test

Ansible Automation Practice Test

Ansible Automation Professional Standards & Competencies 3