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

Inside the 'tasks' section alongside regular tasks

Answer

In a separate file always named handlers.yml

Answer

At the top of the playbook before the 'hosts' key

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

Five times, once per notification

Answer

Zero times unless explicitly flushed

Answer

Once per unique notifying task

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

It clears all queued handlers without executing them

Answer

It resets handler notification status

Answer

It exports handler definitions to a file

Question 4

Can a handler notify another handler in Ansible?

Accepted Answer

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

Answer

No, handlers cannot contain notify directives

Answer

Yes, but only in Ansible 2.8 and later with listen topics

Answer

No, circular dependencies would crash Ansible

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

Pending handlers still execute before the play stops

Answer

Pending handlers execute only on hosts that haven't failed

Answer

Pending handlers are saved and run on the next playbook execution

Question 6

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

Accepted Answer

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

Answer

It makes a handler listen on a network port for trigger events

Answer

It enables handlers to respond to system log messages

Answer

It creates a handler that polls for state changes