Ansible Automation Ansible Handlers and Notifications 2

Question 1

A handler is defined with the name 'Restart Nginx'. Which task directive triggers it?

Accepted Answer

notify: Restart Nginx

Answer

The 'notify' directive with the exact handler name queues that handler for execution at the end of the play if the task changed.

Question 2

In Ansible roles, where should handler files be placed?

Accepted Answer

In the 'handlers/' directory of the role, typically in a file named main.yml

Answer

Role handlers are placed in the 'handlers/' directory, with Ansible automatically loading 'handlers/main.yml'.

Question 3

What happens if a handler is notified but the task that notified it is skipped (not run)?

Accepted Answer

The handler is not triggered because a skipped task is not considered changed

Answer

Handlers are only triggered when the notifying task actually runs and reports 'changed'. A skipped task never changes, so the handler is not notified.

Question 4

Which Ansible command-line option allows you to run only the handlers of a playbook without running the tasks?

Accepted Answer

There is no such option—handlers can only be triggered by task notifications, not run independently

Answer

Ansible does not have a built-in option to run handlers independently. Handlers are always triggered by task notifications.

Question 5

How can you notify multiple handlers from a single task in Ansible?

Accepted Answer

Use 'notify' as a list with multiple handler names

Answer

The 'notify' directive accepts a list of handler names, allowing a single task to queue multiple handlers.

Ansible Automation Practice Test

Ansible Automation Practice Test

Ansible Automation Ansible Handlers and Notifications 2