Which protocol is used for device authentication, authorization, and accounting?
Correct Answer: A
Question 17
What is an information-gathering capability of Cisco IOS Flexible NetFlow in Cisco NFVI?
Correct Answer: A
Comprehensive and Detailed Explanation From Cisco NFVI Knowledge Cisco IOSFlexible NetFlowis the primary telemetry and flow-collection mechanism used across Cisco NFVI platforms. One of its powerful information-gathering capabilities is the ability to createmultiple, separate flow caches, each one with: * Its own key fields * Its own record type * Its own export destination This allows NFVI deployments to capturedifferent types of traffic visibility(control plane, data plane, management, or tenant-specific flows) withindependent caches, which improves scalability and granularity. Why the other options are incorrect: * DockerandKubernetes(B, D) are container orchestration tools, unrelated to NetFlow flow-gathering capabilities. * Single cache(C) is traditional NetFlow, not Flexible NetFlow. Flexible NetFlow explicitly supports multiple independent caches.
Question 18
The main advantage of using NetFlow/IPFIX in network monitoring is:
Correct Answer: B
Question 19
The primary goal of implementing a virtual private cloud (VPC) is to:
Correct Answer: C
Question 20
Refer to the exhibit. An engineer is troubleshooting an issue with switch LEAF-SW-11. The engineer observes that several main servers on the VXLAN BGP EVPN Multi-Site network experience 50-60% packet loss inbound and outbound, and all the DCI tracking interfaces are down. Which two actions must be taken to resolve the issue? (Choose two.)
Correct Answer: C,D
In a VXLAN BGP EVPNMulti-Siteenvironment: * DCI trackingmonitors the health of the DCI links. If all DCI-tracking interfaces go down, the leaf can incorrectly keep advertising or learning remote MAC/IP reachability, leading to packet loss and sub- optimal forwarding for servers in that VLAN/L2VNI. * For proper operation, eachDCI-facing interfacemust be enabled with evpn multisite dci-tracking so that the Multi-Site border leaf tracks reachability over that link. * When using EVPN Multi-Site, BUM (broadcast, unknown unicast, multicast) traffic toward remote sites is typically handled viaingress replication, not multicast groups, for each L2VNI participating in Multi-Site. The configuration snippet shows an L2VNI (vn-segment 16535) still mapped to mcast- group 239.1.1.0, which is inconsistent with Multi-Site recommendations and contributes to packet loss. Therefore, to fix the problem: * Enable DCI tracking on the uplink: * interface Ethernet1/1 * evpn multisite dci-tracking This restores proper DCI-link state monitoring for Multi-Site. #Option C * Change the L2VNI behavior from multicast to Multi-Site ingress replication: Under the VNI for VLAN 11, configure: evpn vni 16535 l2 multisite ingress-replication or the equivalent command for the specific NX-OS release, thereby aligning the L2VNI with EVPN Multi- Site design and eliminating packet loss. #Option D Options A and B are ELAM (embedded logic analyzer) filters used only for packet capture and do not resolve the forwarding issue. Option E is an ACL line unrelated to EVPN VXLAN or DCI tracking and does not address the underlying problem.
