Free Practice Questions for the Cisco CCNP Data Center 300-640 Exam (2026 Updated)

Configuring an email address as a notification endpoint is not sufficient by itself. Cisco Nexus Hyperfabric requires the recipient endpoint to undergo email verification . After an email endpoint is created, Hyperfabric sends a verification code; the administrator must enter that code and confirm that the endpoint status is verified and active. An unverified address therefore causes the condition described in option B.

The endpoint must also be associated with a notification policy . Cisco documents that assertion notifications are configured by selecting one or more fabrics and one or more notification endpoints in the notification policy. If the relevant fabric and the newly created email endpoint are not paired in the policy, assertion messages are not sent to that address. This makes option C correct.

Options A and E incorrectly assume that Hyperfabric directly uses the organization's own email server. Nexus Hyperfabric provides the notification service through its controller architecture. Option D similarly does not represent the required notification configuration described by Cisco.

The correct operational workflow is therefore: create the email endpoint, complete verification, then associate the desired fabric and endpoint through the notification policy.

Study Guide Reference: AI Infrastructure Operations and Troubleshooting — Hyperfabric monitoring, assertions, notification endpoints, and notification policies.

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

The exhibit reports etherErrStats rcvDelta for switch-B/slot-1/switch-ether/port-11 and shows that the receive-error delta has exceeded the configured threshold. This is a physical Ethernet interface error condition on Fabric Interconnect B, port 11. The first troubleshooting action should therefore target the Layer 1 components associated with that port .

Cisco troubleshooting guidance for Fabric Interconnect interfaces recommends checking the physical layer when interfaces report errors or bad packets, including verifying that transceivers are functioning correctly, cabling is intact, and optics are compatible. This establishes option C as the appropriate first action.

Option A begins at the application and compute layers even though the fault identifies a network-interface receive-error condition. Option B examines port-channel configuration, but the alarm identifies physical port 11 rather than a logical port-channel state problem. Option D would be appropriate when PFC congestion or excessive pause behavior is indicated; the exhibit instead reports Ethernet receive errors.

A disciplined troubleshooting sequence begins with the fault domain explicitly identified by telemetry. Physical errors should be eliminated before higher-layer QoS, port-channel, or application analysis is undertaken.

Study Guide Reference: AI Infrastructure Operations and Troubleshooting — UCS network faults, interface telemetry, physical-layer troubleshooting, and network performance analysis.

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

A rail-optimized topology is specifically engineered for large GPU clusters where collective communication performance and minimum inter-GPU latency are critical. In a rail-optimized design, corresponding GPU/NIC interfaces across compute nodes attach to the same rail switch. This allows communication between GPUs of the same rank to remain on a single leaf or rail switch whenever possible, eliminating unnecessary spine traversal and reducing network hops.

Cisco's AI/ML networking guidance gives a directly applicable design example: a rail-optimized, nonblocking architecture connecting 512 GPUs in 64 nodes, with eight GPUs per node . The design uses eight rail/leaf switches and four spine switches and maintains nonblocking bandwidth while optimizing GPU collective communication. Cisco explicitly states that rail-optimized design is recommended for NVIDIA GPU environments.

A conventional leaf-spine architecture can certainly provide high performance and nonblocking bandwidth, but option C is more specific to the requirement for the lowest possible GPU-to-GPU latency at this scale. Flat Layer 2 does not provide the required scalable fabric architecture, while a traditional three-tier model introduces additional hops and potential oversubscription.

Study Guide Reference: 2.0 AI Infrastructure Components and Architecture — 2.1 Evaluate network deployment based on bandwidth, latency, redundancy, scalability, and security.

Ethernet Network Control Policy

Ethernet Network Group Policy

Ethernet QoS Policy

Ethernet Adapter Policy

The mappings correspond to the functional boundaries of Cisco Intersight vNIC policies. Ethernet Network Control Policy manages link-layer behavior including CDP and LLDP. Cisco's Intersight documentation explicitly identifies CDP, LLDP transmit/receive, MAC registration, and uplink-failure behavior as Network Control settings.

Ethernet Network Group Policy controls VLAN membership for FI-attached servers, including the set of allowed VLANs and the optional native VLAN. Ethernet QoS Policy supplies performance-oriented vNIC characteristics such as MTU, rate limiting, traffic priority, CoS, and burst parameters. Cisco's current RoCE configuration guide lists MTU and rate-limit values directly under Ethernet QoS configuration.

Finally, Ethernet Adapter Policy contains adapter-level behavior and performance parameters, including RoCE configuration used for high-performance RDMA interfaces.

Ethernet Network Policy is the unused choice. Cisco documents that policy primarily for VLAN configuration on standalone servers, whereas Ethernet Network Group Policy is the relevant VLAN policy for Fabric Interconnect-attached UCS X-Series vNICs.

Study Guide Reference: AI Infrastructure Deployment and Data Management — UCS vNIC templates, Ethernet policies, QoS, VLAN configuration, and RoCE.

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

ECN (Explicit Congestion Notification)

PFC (Priority Flow Control)

ECN and PFC address different congestion conditions in a RoCEv2 fabric and are intended to complement rather than replace each other. ECN is the appropriate mechanism for fabric-level congestion generated by incast patterns. When several GPU or storage senders simultaneously transmit toward the same destination, switch queues begin to build. ECN-capable switches mark packets rather than immediately dropping them, allowing the receiving endpoint to generate congestion feedback so the transmitting source can reduce its sending rate.

PFC provides hop-by-hop loss prevention for the designated lossless Ethernet priority. When an endpoint or downstream interface cannot accept a burst quickly enough and a queue approaches its configured threshold, PFC transmits pause frames for that specific priority. This temporarily stops upstream transmission and prevents packet loss.

Cisco's RoCEv2 designs combine ECN and PFC precisely because ECN provides proactive end-to-end congestion management while PFC acts as the protective mechanism when queue buildup becomes severe or occurs faster than endpoint rate adaptation can respond.

WRED can provide the queue-marking mechanism associated with ECN, but the requested logical congestion-control mechanism is ECN. AFD is not the corresponding RoCEv2 lossless mechanism for either description.

Study Guide Reference: AI Infrastructure Deployment and Data Management — congestion control, RoCEv2, ECN, PFC, QoS, and lossless Ethernet.

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

Image recognition is a computer-vision application in which an AI model processes digital imagery and identifies meaningful visual content. Depending on the model and use case, the output can include image classifications, detected objects, faces, locations, labels, bounding boxes, or other semantic information describing what appears in the image. Therefore, detection and labeling of visual elements from digital sources is the correct result.

Cisco identifies computer vision as an established AI/ML workload and has used image-recognition techniques in technologies where models learn to identify objects despite variations in position and orientation. The DCAI exam blueprint requires candidates to understand AI use cases, making the distinction between computer-vision workloads and unrelated infrastructure functions important.

Option A is a security and compliance operation involving data anonymization. Option C is an infrastructure scheduling function generally performed by orchestration or management systems. Option D belongs to network control-plane and forwarding behavior and has no direct relationship to image recognition.

The key examination principle is that image recognition transforms unstructured visual input into meaningful classifications or detections that can subsequently drive automated decisions or analytics.

Study Guide Reference: 1.0 AI Fundamentals and Applications — 1.3 Describe AI use cases.

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

The organization already owns third-party AI servers and NVMe storage, so it requires a network-centric AI fabric rather than a Cisco full-stack solution that bundles UCS compute. Cisco Nexus Hyperfabric supports bring-your-own infrastructure scenarios while providing cloud-based design, deployment, management, telemetry, and lifecycle operations.

The licensing distinction is critical. Cisco's current Nexus Hyperfabric documentation defines Essentials primarily for general-purpose fabrics, whereas Premier is the entitlement tier designed for AI fabrics. Premier includes AI-specific functionality such as alignment with NVIDIA reference architectures, adaptive routing support, AI-validated blueprints, automated lossless backend networking, and monitoring between switches and servers.

Option A uses the correct bring-your-own model but the wrong subscription tier for an AI fabric. Option D represents the full-stack Hyperfabric AI model, which includes Cisco UCS servers and therefore conflicts with the requirement to retain existing third-party compute. Option C does not match the requested Cisco 6000 Series cloud-managed Hyperfabric architecture.

Accordingly, BYO AI Hyperfabric using Cisco 6000 Series switches with the Premier entitlement satisfies both reuse of existing infrastructure and AI-specific cloud-managed networking.

Study Guide Reference: 3.3.c Hyperfabric — deploy AI-ready fabrics using Cisco orchestration tools.

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

VAST Data Universal Storage is the architecture explicitly associated with these requirements. Cisco's AI Data Platform documentation describes VAST's Disaggregated Shared-Everything (DASE) architecture, which separates stateless compute from persistent flash capacity so that storage performance and capacity can scale independently. This architecture is designed to eliminate conventional storage-controller bottlenecks and support extremely large AI datasets.

Cisco's AI POD with VAST architecture integrates Cisco UCS infrastructure, Cisco Intersight lifecycle management, high-performance Ethernet/RDMA networking, and VAST's all-flash storage platform. Cisco documentation also identifies UCS C225 M8 systems within VAST-based storage designs and describes the solution as optimized for high-throughput AI workloads.

GPU Direct Storage is particularly important because it reduces unnecessary CPU involvement and intermediate data copies when transferring datasets between storage and GPU memory. Combined with RDMA, this architecture can sustain the high parallel bandwidth required by large training and fine-tuning environments.

NetApp AFF and Pure Storage FlashBlade are capable enterprise storage products, but the DASE terminology uniquely identifies VAST. Local NVMe cannot provide the required exabyte-scale shared-storage architecture and would fragment datasets across individual GPU servers.

Study Guide Reference: AI Infrastructure Components and Architecture — high-performance storage, AI PODs, RDMA, scale, and shared AI data platforms.

NVMe over RoCE uses Remote Direct Memory Access over Converged Ethernet and can employ Priority Flow Control (PFC) to provide lossless behavior between directly connected Ethernet devices. PFC is a link-level IEEE 802.1Qbb mechanism: a congested interface can transmit pause frames for a specific priority to its directly connected upstream peer. This allows the RoCE traffic class to pause without stopping unrelated Ethernet classes.

Cisco's current Intersight guidance for NVMe over RoCEv2 explicitly requires a consistent no-drop class across the network. Cisco recommends enabling the Platinum QoS class, disabling packet drops for that class, and using jumbo MTU values for NVMe/RoCE traffic.

NVMe/TCP and iSCSI operate over conventional TCP/IP. TCP provides end-to-end transport reliability and congestion control, but these protocols do not depend on PFC-based lossless Ethernet between adjacent devices. Fibre Channel has its own native credit-based flow-control mechanisms, but it is not an IP-based storage transport, eliminating option D.

The key distinction is therefore the combination of IP transport, RDMA, and Ethernet priority-based link flow control , which identifies NVMe/RoCE.

Study Guide Reference: AI Infrastructure Components and Architecture — storage technologies including NVMe; high-performance storage networking and RoCE.

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

A high-performance Cisco UCS architecture normally uses redundant fabric interconnects to provide both high availability and aggregated bandwidth. Cisco documentation describes Fabric Interconnects as typically deployed as a pair, integrating UCS components into a highly available management and connectivity domain. Modern UCS X-Series connectivity can provide up to 200 Gbps aggregate unified-fabric bandwidth per compute node through dual 100-Gbps paths.

Option D therefore aligns with UCS architecture: dual fabrics eliminate the single point of failure associated with one Fabric Interconnect, while 100-Gbps connectivity supports high-throughput AI inference workloads. Port channels on uplinks provide bandwidth aggregation and link-level resiliency toward the upstream data center network.

Option A incorrectly limits the Fabric Interconnect to management traffic; UCS unified fabric carries production Ethernet, storage, and management-related connectivity. Option B bypasses the integrated UCS fabric architecture and unnecessarily separates management onto Catalyst infrastructure. Option C introduces both a single point of failure and a severe bandwidth constraint by using one FI and 10-Gbps links.

For AI inference, where throughput and deterministic latency directly influence application performance, redundant high-speed fabric design is the appropriate implementation.

Study Guide Reference: 3.0 AI Infrastructure Deployment and Data Management — 3.2 Configure high-performance compute and storage using Cisco UCS; 3.2.d LAN connectivity and vNIC policies.

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

The Cisco UCS C885A M8 contains six 3000-W 54-V AC power supplies and normally supports an N+2 power configuration . In the scenario, three PSUs are connected to each independent power grid. Losing one complete grid therefore leaves only three operational 54-V PSUs.

Cisco's installation and service documentation specifies the resulting behavior precisely: when only three 54-V AC PSUs remain available, the server continues operating but enters a reduced-performance condition in which power to each GPU is capped at 60 percent . Cisco further states that four or more 54-V power supplies allow operation at full performance.

Consequently, the system does not immediately shut down, eliminating option A. A graceful operating-system shutdown is also not automatically initiated, eliminating D. Option C is incorrect because three active supplies are insufficient for full-performance operation on this platform.

This behavior allows the server to remain available during a significant power-domain failure while keeping its consumption within the capacity of the remaining PSUs. The operational tradeoff is reduced accelerator performance until adequate power redundancy is restored.

Study Guide Reference: AI Infrastructure Operations and Troubleshooting — UCS C885A M8 power redundancy, degraded operation, GPU power management, and availability.

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

Data Center Quantized Congestion Notification, or DCQCN, combines ECN-based end-to-end congestion signaling with Priority Flow Control to maintain efficient and effectively lossless RoCE transport. Cisco states that ECN reacts first , while PFC functions as a safety mechanism if congestion escalates faster than endpoint rate control can respond. With moderate queue buildup, WRED marks ECN-capable packets. If queue utilization continues toward critical levels, PFC pauses the affected priority before packet loss occurs.

The second statement in option C is also correct. When the receiving host receives a RoCEv2 packet carrying the ECN Congestion Experienced marking, the receiving endpoint generates a Congestion Notification Packet, or CNP, toward the transmitting source. The source then reduces its transmission rate according to the congestion-control algorithm.

The network switch performs the ECN marking but does not generate the RoCE CNP on behalf of the receiver. This eliminates options A, B, and D. Options A and D additionally reverse the normal operational sequence by claiming that PFC responds before ECN.

The distinction is important because efficient AI fabrics seek to manage congestion proactively through ECN while reserving PFC for severe congestion and microbursts.

Study Guide Reference: 3.1.a Congestion control mechanisms — PFC and ECN; 3.1.b RoCEv2.

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

Traffic Analytics and Flow Telemetry are mutually exclusive flow-collection modes within Cisco Nexus Dashboard. Cisco's current Nexus Dashboard documentation identifies both under Flow Collection settings and states that Flow Telemetry must be disabled at the fabric level before Traffic Analytics can be enabled.

Traffic Analytics automatically discovers services and visualizes conversations based primarily on Layer 4 information. It provides visibility into network characteristics such as congestion, latency, and drops, which directly matches the monitoring requirements in the scenario. Cisco's Nexus Dashboard Insights guidance likewise states that if Flow Telemetry is already active, it must first be disabled for the relevant sites before Traffic Analytics is selected.

Delta Analysis is an assurance/comparison capability and is not the mutually exclusive collection mode described here. Connectivity Analysis performs reachability and path-oriented diagnostics. SNMP traps remain a separate event-notification mechanism and are not displaced by Traffic Analytics.

The operational distinction matters because Traffic Analytics and Flow Telemetry use different approaches to flow collection and analysis. An administrator cannot simply enable both collection modes simultaneously and expect them to operate in parallel on the same fabric configuration.

Study Guide Reference: AI Infrastructure Operations and Troubleshooting — Nexus Dashboard monitoring, telemetry, congestion analysis, latency, and packet-drop visibility.

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

The Cisco UCS C885A M8 with NVIDIA H200 GPUs is purpose-built for dense accelerated computing and directly satisfies the NVLink requirement. Cisco's C885A M8 NVIDIA configuration supports eight H100 or H200 SXM Tensor Core GPUs on an HGX platform. Those GPUs are interconnected using NVIDIA NVLink, providing the high-bandwidth GPU-to-GPU communication necessary for distributed tensor processing inside the server.

The platform also provides substantial host-memory capacity, dual AMD EPYC processors, high-speed local NVMe storage, multiple 400-GbE adapters for inter-node GPU communication, and Cisco Intersight integration. These capabilities make it appropriate for large language models, generative AI training, fine-tuning, RAG, and large inference workloads.

Option A does not provide the same HGX NVLink-based eight-GPU architecture with an L40 configuration. Option B uses AMD accelerators; AMD GPU connectivity employs AMD interconnect technologies rather than NVIDIA NVLink. Option C is designed for materially different workload and GPU-density requirements and does not deliver the HGX H200 NVLink topology specified by the scenario.

The critical selection criterion is not merely whether a server can host a discrete GPU. The question explicitly requires direct GPU-to-GPU access through NVLink , which identifies the NVIDIA HGX-based C885A M8 configuration.

Study Guide Reference: AI Infrastructure Components and Architecture — compute selection based on CPU, GPU, memory, virtualization, interconnect performance, and workload requirements.

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

Natural language processing enables computer systems to interpret, analyze, transform, and generate human language. It operates on textual or spoken language and is foundational to applications such as speech recognition, transcription, conversational assistants, document intelligence, summarization, sentiment analysis, and information extraction. Consequently, converting human speech or written material into machine-processable, structured information is the function that best represents NLP in this question.

Cisco describes NLP-oriented technologies in its collaboration platforms through natural-language understanding, speech-to-text, transcription, translation, conversational AI, and question-answering capabilities. Cisco's AI workforce material also associates NLP engineering with text understanding, speech-to-text AI, semantic search, and language models.

Option A is a storage and compression function. Option C relates to networking, protocol processing, and authorization rather than natural-language interpretation. Option D represents data cleansing or deduplication and does not specifically require NLP.

Within the DCAI blueprint, this capability falls under the broader requirement to understand AI use cases and AI workload characteristics. The essential distinction is that NLP operates on human language and converts linguistic information into representations that applications can process programmatically.

Study Guide Reference: 1.0 AI Fundamentals and Applications — 1.3 Describe AI use cases.

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