300-610 Sample Questions & Answers

This is the comprehensive and correct design. Creating a dedicated system class for FCoE allows for specific treatment. Enabling Priority Flow Control (PFC) is essential for creating a no-drop (lossless) behavior for this class. Assigning a guaranteed bandwidth percentage ensures FCoE traffic has the resources it needs, even during congestion. The remaining traffic can fairly share the rest of the bandwidth in the default class.

The peer-gateway command allows a vPC peer switch to act as the active gateway for packets that are sent to the router MAC address of the vPC peer. This prevents traffic from being dropped when, for example, a connected device or an upstream router sends traffic to the MAC address of the other vPC peer. It enables local forwarding on the secondary peer without needing to traverse the peer-link.

N_Port Virtualization (NPV) mode allows the Fabric Interconnect to act as a pass-through device, aggregating multiple N_Port logins from servers into one or more external links to the core Fibre Channel fabric. To the upstream FC switch, the FI appears as a host with multiple devices (via NPIV), not as another switch. This simplifies SAN administration and avoids domain ID limitations. FC Switching Mode would make the FI a full-fledged FC switch, which is not the requirement.

A Rollback Workflow is a crucial component for creating resilient automation. It is a separate workflow designed to execute automatically if any task in the primary workflow fails. Its purpose is to reverse the changes made by the successful tasks that ran before the failure, returning the system to its original state and preventing partially completed, failed configurations.

Stretching the Layer 2 broadcast domain (VNI) across both data centers is fundamental. It ensures that the VM's original subnet is available in the destination data center, so it does not need to change its IP address after the move.

Using a distributed anycast gateway, where the same default gateway IP and MAC address exist on all VTEPs in both data centers, is crucial. This ensures that when the VM moves, its default gateway is immediately available locally without requiring any ARP updates, preventing traffic from being black-holed or inefficiently routed back to the original DC.

A core-edge fabric topology is the standard for large, scalable, and resilient SANs. It consists of high-performance core switches (like Cisco MDS Directors) and lower-cost edge switches where servers and storage connect. This design provides high inter-switch bandwidth, predictable latency (maximum two hops between any devices), and excellent fault isolation. A full mesh is often too costly and complex to scale.

VRF-lite (Virtual Routing and Forwarding) is the ideal technology for this requirement. It allows a single physical router or switch to host multiple independent virtual routing tables. This provides complete Layer 3 isolation between tenants, allowing for overlapping IP address schemes, without the overhead of MPLS. It is the standard method for multi-tenant L3 segmentation within a data center.

A vCon (Virtual Connection) Placement Policy defines how virtual interfaces (vNICs/vHBAs) are mapped to the physical uplink paths on the VIC adapter. This allows an administrator to control the distribution of virtual interfaces across the available physical hardware paths (VIFs - Virtual Interface Functions) on the adapter, which is critical for managing redundancy and performance, especially in designs with dynamic vNICs.

NX-API REST is the ideal choice. It is a native, on-box HTTP/HTTPS-based API that allows you to send CLI commands (like show interface) and receive the output structured in JSON or XML. This meets all the requirements: programmatic, structured data, and no special client software needed beyond a standard HTTP client.

This statement is true. The physical mgmt0 port on a Nexus 7000/7700 series switch belongs to the default VDC but can be used to provide management access to non-default VDCs. Each VDC can be assigned a unique IP address for its management interface, which is then routed through the shared physical mgmt0 port. This allows for isolated management of each VDC over a single physical connection.