Question 110
A service-provider operations test targets: An Ansible network playbook uses `hosts: all` and changes every backbone router though the request approved only an isolated PoP. Which result is required?
Explanation
Correct Answer
Dry-run output lists only the intended routers and unrelated devices show no changes. This confirms the approved response: Scope inventory groups and host limits to approved lab or PoP devices before network configuration tasks run. It is relevant because: Ansible host selection controls deployment blast radius independently of the syntax of the configured tasks.
Incorrect Answers
A revised plan preserves the deployed service VM and updates only the intended metadata. This would validate ANOTHER scenario: A Terraform plan proposes deleting an NSO integration virtual machine because its resource label was renamed in source code without preserving state identity. The specific correction here is: Scope inventory groups and host limits to approved lab or PoP devices before network configuration tasks run.
The second apply is blocked or serialized until state reconciliation completes and the final plan matches desired topology. This would validate ANOTHER scenario: Two Terraform jobs edit the same service-provider cloud network workspace in parallel, creating conflicting route-table state and duplicate resources. The specific correction here is: Scope inventory groups and host limits to approved lab or PoP devices before network configuration tasks run.
Counter retrieval succeeds and a controlled mutation remains rejected by schema or datastore rules. This would validate ANOTHER scenario: A network operator attempts to PATCH a YANG counter marked `config false`, then blames access control when the edit is rejected. The specific correction here is: Scope inventory groups and host limits to approved lab or PoP devices before network configuration tasks run.