Refer to the exhibit. Drag and Drop Question. An engineer must automate the configuration of Layer 3 interfaces in an Ansible playbook. The engineer must configure interface GigabitEthernet0/3 with…

Question

Exhibit

Explanation

This question tests knowledge of Ansible network automation using the cisco.ios.ios_l3_interfaces module to configure primary and secondary IPv4 addresses on router interfaces without disrupting existing configuration.

Approach. The correct approach uses the cisco.ios.ios_l3_interfaces module with state: merged, which adds or updates configuration without overwriting what already exists (unlike state: replaced or state: overridden). GigabitEthernet0/3 is configured with a standard primary IPv4 address (192.168.2.100/24) under the ipv4: list. GigabitEthernet0/4 requires the secondary: true flag nested under its ipv4 address entry (192.168.4.100/24) to designate it as a secondary IP. The config block lists both interfaces as separate list items under the config: key, each with a name: field matching the full interface name.

Concept tested. Ansible network automation with cisco.ios.ios_l3_interfaces - specifically the distinction between state values (merged vs replaced/overridden), correct YAML structure for primary vs secondary IPv4 addresses, and idempotent interface configuration in IOS playbooks.

Reference. Cisco DevNet / CCNP Enterprise (ENAUTO 300-435) - Ansible ios_l3_interfaces module documentation; Ansible Galaxy cisco.ios collection

No community discussion yet for this question.