Ansible Automation Ansible Handlers and Notifications

Question 1

Where must Ansible handlers be defined within a playbook?

Accepted Answer

In a 'handlers' section at the play level, separate from the 'tasks' section

Answer

Handlers are defined in a dedicated 'handlers' section at the play level, keeping them separate from regular tasks.

Question 2

How many times will a handler execute if it is notified by 5 different tasks during a single play run?

Accepted Answer

Once, at the end of the play

Answer

Ansible deduplicates handler notifications—regardless of how many tasks notify the same handler, it runs only once at the end of the play.

Question 3

What is the 'meta: flush_handlers' task used for in an Ansible playbook?

Accepted Answer

It forces all pending handlers to execute immediately at that point in the play rather than waiting until the end

Answer

'meta: flush_handlers' is a special task that immediately runs all pending handlers at that point in the play execution.

Question 4

Can a handler notify another handler in Ansible?

Accepted Answer

Yes, a handler can use 'notify' to trigger another handler

Answer

Handlers can include 'notify' directives to chain handler execution, allowing one handler to trigger another.

Question 5

What happens to pending handlers if a task fails during a play that has 'force_handlers: false' (the default)?

Accepted Answer

Pending handlers are not executed—the play aborts and handlers are skipped

Answer

By default, if a play fails, pending handlers are not executed. Setting 'force_handlers: true' overrides this to ensure cleanup handlers always run.

Ansible Automation Practice Test