Ansible Automation Ansible Playbook Structure and Variables 2

Question 1

In an Ansible playbook, what is the purpose of the 'become: true' directive?

Accepted Answer

It enables privilege escalation so tasks run as a different user (e.g., root)

Answer

'become: true' enables privilege escalation, typically via sudo, allowing tasks to run as root or another privileged user.

Question 2

What is the difference between 'import_playbook' and 'include_playbook' in Ansible?

Accepted Answer

import_playbook is static (processed at parse time) while include_playbook is dynamic (processed at runtime)

Answer

Static imports are processed when the playbook is parsed, enabling features like --list-tasks. Dynamic includes are processed during execution, enabling conditional logic.

Question 3

How do you reference a variable named 'app_port' inside a task's module arguments in an Ansible playbook?

Accepted Answer

Answer

Ansible uses Jinja2 templating syntax with double curly braces to reference variables within task arguments.

Question 4

What keyword in a playbook task definition allows you to run a task only when a specific condition is true?

Accepted Answer

when

Answer

The 'when' keyword evaluates a Jinja2 expression and only runs the task if it evaluates to true.

Question 5

What is the purpose of 'vars_prompt' in an Ansible playbook?

Accepted Answer

It prompts the user for variable values interactively at playbook runtime

Answer

'vars_prompt' enables interactive playbook runs by asking the user to enter values for specified variables before task execution begins.

Ansible Automation Practice Test

Ansible Automation Practice Test

Ansible Automation Ansible Playbook Structure and Variables 2