Cisco Updated 300-610 Exam Questions and Answers by millie-mae

IEEE 802.1AX and the earlier IEEE 802.3ad specification identify link aggregation controlled through LACP. Cisco documents that LACP bundles multiple physical Ethernet interfaces into one logical port channel. A virtual port channel extends that model across two Cisco Nexus peer switches, allowing the attached device to form one standards-based logical channel while the physical members terminate on separate switches. The design increases usable aggregate bandwidth, permits hashing of independent flows across member links, and preserves connectivity after a link or peer-switch failure. Those characteristics address both throughput and resilience without replacing the existing PFC and jumbo-frame configuration. PFC protects selected traffic classes from congestion loss but does not create additional link capacity. Jumbo frames reduce per-packet overhead but likewise do not aggregate bandwidth. DCBX with Enhanced Transmission Selection can negotiate data-center bridging parameters and allocate bandwidth among traffic groups; it manages contention rather than adding physical forwarding capacity. Hierarchical QoS prioritizes and shapes classes but cannot eliminate an undersized aggregate link. Upgrading individual links could increase raw capacity, but Option C is not the action tied to the IEEE link-aggregation standards explicitly cited in the question. vPC with LACP is therefore the intended standards-aligned solution: it combines multiple links, uses the available bandwidth more effectively, and removes a single-switch attachment failure domain while presenting a single logical port channel to the connected system. Cisco Nexus LACP and port-channel configuration guide

================

A three-node physical Nexus Dashboard cluster is the correct production NDFC deployment for active-active high availability. Cisco documents NDFC on a three-node Nexus Dashboard cluster as an active-active model: all three nodes participate in running the application microservices, and if one node fails, its services are rescheduled onto the surviving nodes. This avoids the active-standby controller design used by older DCNM releases and improves resource utilization and service continuity. Because the requirement explicitly calls for physical appliances, the pND form factor must be selected rather than vND. A five-node vND cluster is a supported scale-out virtual model in some releases, but it contradicts the physical-appliance requirement. A four-node vND cluster is not the standard NDFC active-active virtual cluster described in the deployment options. A four-node pND cluster is principally relevant when capacity planning or cohosting additional Nexus Dashboard services requires an extra worker node; the question identifies only NDFC management of two production fabrics and provides no NDI cohosting or scale requirement that would justify that fourth node. Cisco also states that a minimum of three Nexus Dashboard nodes is required for production NDFC LAN Controller deployments. Therefore, the precise deployment matching physical form factor, production use, and active-active HA is the three-node pND cluster. Cisco NDFC installation and deployment options

================