Why use Ansible for switch setup?
Why C is the answer
Repeatable, version-controlled changes
Playbooks apply the same settings each time.
In detail
- Playbooks apply the same settings each time.
- Playbooks live in version control.
Use case
An illustrative scenario, not a real incident.
A team uses Ansible, so all its switches get the same settings each time.
See it in different ways
flowchart LR A["Inventory and variables"] --> B["Playbook"] B --> C["Render NVUE configuration"] C --> D["Apply to switches"] D --> E["Verify"]
sequenceDiagram participant G as Git participant A as Ansible participant S as Switches G->>A: Playbook and variables A->>S: Applies the desired state A->>S: Second run reports no changes
flowchart LR S0["Edit playbook"] --> S1["Commit"] --> S2["Run"]
Key point: Ansible gives repeatable changes.
Why the other options are wrong
- A. It replaces the need for any testing
- You still test.
- B. It removes the need for a network design
- You still need a design.
- D. It increases the speed of each link
- It does not change link speed.