The stated requirement is: show the delta, then apply, and keep a state file of owned IOS XE objects. Which CM solution identification fits 5.4?
Select an answer to reveal the explanation.
Short Explanation
“Show the delta, apply, keep state” is Terraform’s calling card—identify it under 5.4, don’t rebuild a second full 5.3.b lab in the stem.
Full Explanation
When the stated requirement is to show the delta, then apply, and keep a state file of owned IOS XE objects, Terraform is the configuration-management solution that fits DEVCOR 5.4 identification: plan and apply plus state-backed ownership of resources. Municipal change processes that insist on a durable ownership map and a preview of creates, updates, and destroys are describing Terraform’s core workflow against campus devices, not an ad-hoc CLI checklist.
Ansible check mode alone does not store a durable ownership state file by default the way Terraform state does, so it fails that part of the requirement bundle even though check mode is useful elsewhere. Puppet catalog compile is not the official plan/apply and state model for this v1.1 bank. A spreadsheet of CLI commands with no automation tool fails the configuration-management solution requirement entirely and cannot enforce convergence.
Exam caveat: Ansible remains correct when requirements emphasize agentless plays without state-file ownership; read the stem’s verbs (plan, apply, state) as Terraform signals. Do not drag Puppet back in as a primary answer on updated items.
Operational check: implement a tiny VLAN root module, show plan output, apply, and demonstrate state listing owned objects—matching the requirement language literally for reviewers and auditors.