An organization with big data requirements is implementing NETCONF as part of its migration to a new cloud-based environment. The organization has multiple offices across widespread geography. A…

Question

Exhibits

Options

• A<xml version="1.0" encoding="utf-8"?> <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id=""> <edit-config> <target> <running/> </target> <config> </config> </rpc>
• Bsnmp-server community public RW snmp-server trap link ietf snmp-server enable traps snmp authentication linkdown linkup snmp-server enable traps syslog snmp-server manager
• C<xml version="1.0" encoding="utf-8"?> <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id=""> <cisco-ia:save-config xmlns:cisco-ia="http://cisco.com/yang/cisco-ia"/> </rpc>
• Dlogging history debugging logging snmp-trap emergencies logging snmp-trap alerts logging snmp-trap critical logging snmp-trap errors logging snmp-trap warnings logging snmp-trap notifications logging snmp-trap informational logging snmp-trap debugging

• A
  5% (2)
• B
  3% (1)
• C
  89% (34)
• D
  3% (1)

Explanation

The configuration in chosen option represents the NETCONF <rpc> request used to save the running configuration. It uses the cisco-ia:save-config operation, which is specific to Cisco devices. This operation ensures that the running configuration is saved persistently on the device, meeting the requirement for managing configurations in a NETCONF-enabled environment.

No community discussion yet for this question.