Q25Infrastructure and Automation
A network operations team is using the cloud to automate some of its managed customer and branch locations. It requires all tooling to be ephemeral by design, and the complete automation environment must be recreatable without manual commands. Automation code and configuration state will be kept in git for change control and versioning. The engineering high-level plan is to use VMs in a cloud-provider environment, then install open-source tooling on those VMs to poll, test, and configure the remote devices, and to deploy the tooling itself. Which configuration-management and/or automation tooling is required for this solution?
← → navigate · a answer
Community votes
Discussion · 7
11
I think B is right, Terraform is open source and that is the keyword here.
6
I think answer B is correct here: Terraform is for building the VMs in the cloud environment and Ansible for automating the network operations.
6
Yes, but NSO isn't open source and therefor B is correct as stated earlier. Ansible is open source and Terraform. Terraform is used to deploy the infrastructure and Ansible to deploy the rule set's on VM's and Network equipment.
2
I will go with NSO or NSO and Ansible, because it is talking about a networking operation team and well NSO is perfect for Network Orchestation with different vendors. The one thing that makes me doubt is if you can save the automation code and NSO is used for automation in git, i know that it uses YANG and that can be saved on git, but if NSO cant automate then it will be a great combo with Ansible, but if it can i will just go with NSO.
2
Yeah, but Ansible is technically open source.
2
Terraterm - Infrastructure Provisioning
Ansible - Infrastructure Configurations
B 1
Selected Answer: B
B is correct since Terraform will be used to provision the VM while Ansible will be used for configuration management.