A team is choosing an automation tool that pushes configuration to network devices over SSH using human-readable YAML playbooks and runs without a permanent agent installed on each device. Which tool matches this agentless, push-based description?
- ATerraform, which uses HashiCorp Configuration Language to declare and provision infrastructure resources
- BA REST client alone, which issues raw HTTP verbs against device APIs but has no playbook engine
- CAnsible, which is agentless and pushes YAML playbooks to devices over SSH from a control node Correct
- DNETCONF by itself, which is a configuration protocol carrying XML payloads rather than an automation tool
Why A is wrong: Terraform is a valid current tool but declares infrastructure in HCL and focuses on provisioning state, not pushing YAML playbooks over SSH, so the description does not fit.
Why B is wrong: A bare REST client sends HTTP requests but provides no YAML playbook automation framework, so it does not satisfy the stated workflow.
Why C is correct: Ansible is agentless and uses a push model, connecting from a control node over SSH and applying YAML playbooks, which matches every detail of the requirement.
Why D is wrong: NETCONF is a management protocol that exchanges XML over a secure transport, not an agentless tool that runs YAML playbooks, so it is the wrong category.