Ansible Automation Research & Evidence-Based Practice 4

Question 1

What does Ansible's 'batteries included' philosophy mean in the context of evidence-based automation design?

Accepted Answer

Ansible ships with thousands of built-in modules covering common use cases without extra plugins

Answer

Ansible's built-in module library covers most common infrastructure tasks so practitioners can rely on tested, maintained code rather than custom scripts.

Question 2

According to Ansible research and community practice, what is the recommended maximum number of tasks in a single task file before splitting into includes?

Accepted Answer

There is no hard limit, but readability is the guide

Answer

Ansible has no enforced task limit per file; the best-practice guide recommends splitting for readability and maintainability when files become unwieldy.

Question 3

Which Ansible feature allows practitioners to validate that collected facts match expected evidence before proceeding with tasks?

Accepted Answer

Assertions with the `assert` module

Answer

The `assert` module evaluates conditions against gathered facts and fails the play with a descriptive message if expectations are not met.

Question 4

What is the best-practice recommendation for storing Ansible playbooks and roles to enable team collaboration and change tracking?

Accepted Answer

A version control system such as Git

Answer

Version control (Git) provides change history, branching, peer review, and rollback—all essential for team-based infrastructure automation.

Question 5

Which Ansible construct is the evidence-based way to handle task failures gracefully and run cleanup tasks regardless of failure?

Accepted Answer

rescue and always within a block

Answer

A `block` with `rescue` handles failure recovery and `always` runs cleanup tasks whether or not the block succeeded.

Ansible Automation Practice Test

Ansible Automation Practice Test

Ansible Automation Research & Evidence-Based Practice 4