350-601 Implementing and Operating Cisco Data Center Core Technologies (DCCOR) Practice Questions

All 32 ports in slot 1 on a Cisco Nexus 5548UP switch are unified ports. Unified ports are physical ports that can be dynamically configured as either Ethernet ports for data networking or Fibre Channel ports for SAN connectivity. This flexibility allows organizations to optimize their infrastructure based on current needs without requiring separate switches for Ethernet and FC traffic.

Store-and-forward switching operates in the data plane by receiving the entire frame, checking for errors using the Frame Check Sequence (FCS), and then forwarding it to the destination port. This method ensures data integrity by performing error checking before forwarding, though it introduces slightly higher latency compared to cut-through switching. Error recovery and BGP operation are control plane functions.

Cut-through switching operates in the data plane by forwarding frames immediately after reading the destination MAC address, without waiting for the complete frame arrival. This reduces latency significantly compared to store-and-forward switching, but does not perform error checking, potentially forwarding corrupted frames. Both switching methods handle actual packet forwarding in the data plane.

Cisco UCS Manager provides several default user roles for role-based access control (RBAC): Administrator has full access to all functions, Operations can perform most configuration tasks but cannot create users, Read-Only can only view configurations, AAA Administrator manages authentication and users, and Network Administrator manages network-related configurations. Each role provides specific permission levels for different management responsibilities.

L2 will not forward the packet to a spine switch because both the sending host and receiving host are directly connected to the same leaf switch (L2). In FabricPath, when the source and destination are on the same leaf switch, the packet is switched locally within that leaf switch without needing to traverse the spine layer. The spine switches are only used for inter-leaf communication when hosts are connected to different leaf switches.

The peer-switch command, configured under the vPC domain, is specifically designed to address this scenario. It allows both vPC peer devices to act as the root bridge for the same spanning-tree instance and, more importantly, enhances loop prevention in case of a peer-link failure. When the peer-link fails, the secondary switch (which can still reach the primary via the peer-keepalive link) recognizes the split-brain condition and will shut down its vPC member ports, preventing duplicate traffic forwarding and potential loops.

The APIC GUI in Advanced mode should not be mixed with other configuration methods because it provides unrestricted access to the Management Information Tree (MIT) and allows direct manipulation of managed objects. Unlike Basic mode which provides a simplified interface, Advanced mode bypasses policy validation and can lead to configuration conflicts. The other methods (NX-OS CLI, REST API, and Basic mode GUI) can be safely combined as they follow proper policy enforcement.

The port-channel load-balance dst-port module 4 command configures port channel load balancing to use the destination port as the load balancing criteria specifically for module 4. When dst-port is specified, traffic distribution across port channel members is based on the destination TCP/UDP port number in the packet headers. The other options are incorrect because source port, IP addresses, and MAC addresses are not specified in this command, and the syntax is valid for NX-OS.

An endpoint registry is best described as a collection of current endpoints known to the Cisco ACI fabric. The endpoint registry maintains a database of all discovered endpoints including their MAC addresses, IP addresses, VLAN assignments, and location information. This registry works with the policy repository to apply appropriate policies to known endpoints. The other options describe policy controllers, rule collections, or policy distribution mechanisms rather than the endpoint registry itself.

A virtual Port Channel (vPC) logically combines ports from multiple physical Nexus switches into a single logical port channel bundle, allowing downstream devices to connect to both switches simultaneously while appearing as a single port channel. This provides redundancy and increased bandwidth without Spanning Tree Protocol blocking. VIC (Virtual Interface Card), VRF instances, and VDC (Virtual Device Context) do not combine ports from multiple switches into bundles.

A contract is the primary tenant element that can be of type regular, taboo, or out-of-band (OOB). Regular contracts define allowed communication between EPGs, taboo contracts define prohibited communication, and OOB contracts govern management traffic. Bridge domains, EPGs, and filters do not have these type classifications - they serve different functions in the ACI policy model.