Ansible Handlers and Notifications Flashcards

Where must Ansible handlers be defined within a playbook?

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

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

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

Answer: Once, at the end of the play

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

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

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

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

Can a handler notify another handler in Ansible?

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

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

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

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

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

What is the 'listen' keyword used for in Ansible handlers?

Answer: It allows multiple handlers to subscribe to a single notification topic, so all can be triggered with one 'notify'

The 'listen' keyword lets handlers subscribe to a named topic, allowing a single 'notify' to trigger multiple handlers.