XK0-006 Automation, Orchestration, and Scripting Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  A template task with notify pointing to a handler that restarts nginx

  Why this is correct

  The template module reports changed status only when the rendered file differs from the destination, and notify queues the named handler exclusively on that change. Handlers run once at the end of the play, so nginx restarts only after an actual template modification, which is exactly the idempotent behavior the scenario requires.

• ✗

  A copy task with force: no followed by a shell task that runs systemctl restart nginx

  Why it's wrong here

  The copy module cannot render Jinja2 variables the way template does, so the configuration would be deployed literally. Even with force: no, the shell task restarts nginx on every run regardless of change, reintroducing the unnecessary restarts. Both the module choice and the lack of change gating are wrong.

• ✗

  A template task with a when clause that checks whether the nginx process is running

  Why it's wrong here

  A when clause evaluates a condition before the task runs and has no awareness of whether the template content changed. Testing process state would either always copy or always skip, and it never triggers a restart based on file modification. The scenario needs change-driven notification, not a pre-run condition.

• ✗

  A template task followed by a service task with state: restarted and no conditional

  Why it's wrong here

  An unconditional service task with state restarted bounces nginx on every playbook execution whether or not the template changed. That defeats the goal of avoiding needless restarts and breaks idempotence reporting, since the play always records a change. It ignores the change status that the template module already tracks.

Go deeper

Related to this question