nerdexam
Cisco

300-910 · Question #12

An Interface on a router as a Layer 3 link has been configured to another device by updating an Ansible playbook that is executed via a CI/CD pipeline. The Ansible playbook was written to push the con

The correct answer is D. Add a pipeline step that captures and parses the show ip interface output so that the operational state can be referenced.. To validate that a router interface configured via an Ansible playbook is functioning correctly, an automated test should capture and parse the show ip interface output to reference its operational state.

CI/CD Pipelines

Question

An Interface on a router as a Layer 3 link has been configured to another device by updating an Ansible playbook that is executed via a CI/CD pipeline. The Ansible playbook was written to push the configuration change using the ios_config module. Which automated test validates that the interface is functioning as it should?

Options

  • AAdd a pipeline step that runs the playbook a second type. If it does not modify the device on the second run, then the interface is correctly configured.
  • BAutomated testing is already built-in because the playbook execution is successful only after Ansible validates that it applied the change.
  • CAdd a pipeline step that captures and parses the packet flow for the interface.
  • DAdd a pipeline step that captures and parses the show ip interface output so that the operational state can be referenced.

How the community answered

(31 responses)
  • A
    13% (4)
  • B
    3% (1)
  • C
    10% (3)
  • D
    74% (23)

Why each option

To validate that a router interface configured via an Ansible playbook is functioning correctly, an automated test should capture and parse the `show ip interface` output to reference its operational state.

AAdd a pipeline step that runs the playbook a second type. If it does not modify the device on the second run, then the interface is correctly configured.

Running the playbook a second time only confirms idempotency (no changes on subsequent runs) but does not validate the operational functionality of the configured interface itself.

BAutomated testing is already built-in because the playbook execution is successful only after Ansible validates that it applied the change.

Ansible's successful execution only confirms the configuration was applied without errors, not that the interface is functionally operating as intended from a network perspective.

CAdd a pipeline step that captures and parses the packet flow for the interface.

Capturing and parsing packet flow is complex and primarily validates data plane forwarding, not necessarily the correct Layer 3 operational state of the interface configuration itself.

DAdd a pipeline step that captures and parses the show ip interface output so that the operational state can be referenced.Correct

Capturing and parsing the `show ip interface` command output allows checking key operational parameters such as the interface's line protocol status (up/down), IP address, and MTU, which directly indicate if the interface is correctly configured and functioning. This provides objective evidence of the configuration's effect on the device's operational state.

Concept tested: Ansible network automation, interface operational validation

Source: https://docs.ansible.com/ansible/latest/collections/cisco/ios/ios_command_module.html

Topics

#Network Automation#CI/CD Testing#Post-Configuration Validation#Operational State

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 300-910 Practice