Ansible Automation Ansible Handlers and Notifications 3

Question 1

In Ansible, what is the primary purpose of using handlers instead of regular tasks for service restarts?

Accepted Answer

Handlers prevent redundant restarts by only running once even when notified multiple times, maintaining idempotency

Answer

Handlers execute faster than regular tasks

Answer

Handlers can access elevated privileges that tasks cannot

Answer

Handlers support more modules than regular tasks

Question 2

What status must a task report for its 'notify' directive to actually queue the handler?

Accepted Answer

changed

Answer

ok

Answer

skipped

Answer

failed

Question 3

How do you define a handler in an Ansible playbook that restarts the 'httpd' service?

Accepted Answer

handlers:
  - name: Restart Apache
    service:
      name: httpd
      state: restarted

Answer

tasks:
  - handler: Restart Apache
    service: name=httpd state=restarted

Answer

handlers:
  - Restart Apache: service name=httpd state=restarted

Answer

notify:
  - name: Restart Apache
    service: name=httpd state=restarted

Question 4

What is a common anti-pattern when using Ansible handlers, and how should it be avoided?

Accepted Answer

Using generic names like 'restart service' across multiple roles causes conflicts; use role-prefixed names like 'apache : restart service'

Answer

Defining more than 3 handlers per play causes performance issues; split into multiple plays

Answer

Using handlers for database operations; use tasks with 'run_once: true' instead

Answer

Notifying handlers inside loops; this is unsupported and causes errors

Question 5

When using Ansible with 'serial' execution (rolling updates), when do handlers run?

Accepted Answer

At the end of each serial batch, not at the very end of the entire play

Answer

At the very end of the entire play after all batches complete

Answer

After each individual task within each host

Answer

Only on the last host in the last serial batch

Question 6

Can Ansible handlers use 'when' conditions to conditionally execute?

Accepted Answer

Yes, handlers support 'when' conditions just like regular tasks

Answer

No, handlers always execute if notified regardless of conditions

Answer

Yes, but only if the handler uses the 'listen' topic mechanism

Answer

No, conditional logic must be in the notifying task instead