Cisco 300-640 Implementing Cisco Data Center AI Infrastructure (DCAI) Exam Practice Test

The UCS X9516 X-Fabric Module provides PCIe Gen5 connectivity between supported M8 compute nodes and X580p PCIe nodes. Before enabling that connectivity, the affected compute nodes must be powered down and equipped with the appropriate UCS PCI Gen5 mezzanine cards .

Cisco identifies the UCSX-V5-PCIME rear mezzanine card as a required hardware component for X580p connectivity. The card provides PCIe Gen5 electrical lanes between each CPU and the X9516 X-Fabric modules. Cisco also specifies that companion compute-node host power must be off for insertion or removal operations involving X580p PCIe connectivity, and that X9516 modules must be installed before the X580p PCIe nodes are installed.

Therefore, powering down the affected blades and installing their required PCI mezzanine cards are the appropriate preparatory actions.

The IFMs provide normal UCS network connectivity and do not need to be powered off or disconnected from Fabric Interconnects merely to install the X-Fabric modules. Similarly, disconnecting the Device Connector is unrelated to physical PCIe fabric installation and would unnecessarily interrupt Intersight connectivity.

Study Guide Reference: AI Infrastructure Deployment and Data Management — Cisco UCS X-Series GPU expansion, X-Fabric, PCIe connectivity, and hardware deployment.

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

Cisco Unified Edge directly matches the distributed branch deployment requirements. The Cisco UCS XE9305 chassis contains two Unified Edge Management Controllers, providing redundancy for the chassis management plane. Its XE130c M8 compute node supports up to 768 GB of memory , precisely matching the stated in-memory processing requirement, and supports optional GPU acceleration.

Operationally, Unified Edge is designed for highly distributed sites where qualified IT personnel may not be present. Cisco documents remote server launch with no onsite IT staff, zero-touch provisioning, fleet visibility, and automated lifecycle management through Cisco Intersight. Intersight provides SaaS-based infrastructure lifecycle operations across distributed Unified Edge systems.

Although X-Series Direct is also suitable for remote locations, the exact combination of dual management controllers, 768-GB memory capacity, remote server launch, and Unified Edge's edge-focused lifecycle capabilities uniquely identifies option C. C845A M8 and C240 rack servers provide substantial compute capabilities but do not match the integrated edge chassis and zero-touch operational model required by the scenario.

This is a classic DCAI compute-selection question in which architectural and operational requirements must be evaluated together rather than selecting solely by raw compute performance.

Study Guide Reference: 2.2 Evaluate compute deployment; 2.5 Evaluate hybrid AI deployment with distributed infrastructure.

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

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.

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

Retrieval-Augmented Generation enhances an LLM by retrieving relevant information from external knowledge sources and incorporating that material into the context supplied to the model during generation. This permits a pretrained model to answer questions using organization-specific information without requiring its underlying model parameters to be retrained for every knowledge update.

Cisco describes RAG as a technique that connects LLM applications to additional data sources, including internal repositories containing sensitive customer or business information. Cisco's enterprise RAG guidance specifically emphasizes using proprietary organizational data to ground responses in enterprise information. Therefore, providing access to proprietary data is the correct answer.

Option A is incorrect because RAG does not eliminate ingestion, parsing, chunking, cleaning, embedding, or indexing requirements. Option B is too absolute: grounding can improve factual relevance but does not inherently remove model bias. Option D describes modification of model parameters, which is characteristic of training or fine-tuning rather than standard RAG retrieval.

Cisco explicitly includes RAG as a required DCAI workload type, so candidates must distinguish retrieval-based augmentation from model training and fine-tuning.

Study Guide Reference: 1.0 AI Fundamentals and Applications — 1.1.a RAG.

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

Priority Flow Control is a foundational mechanism used to provide lossless Ethernet behavior for RoCEv2. PFC operates on individual Ethernet priorities and allows a congested receiver or switch to pause transmission for the affected priority while permitting traffic in other classes to continue. Cisco's AI networking guidance explicitly states that PFC is enabled for RoCEv2 traffic to prevent packet drops caused by congestion.

This characteristic is critical for RDMA workloads because packet loss can trigger retransmission behavior and significantly degrade GPU collective communication performance. In an AI backend fabric, RoCEv2 is normally placed in a no-drop QoS class with PFC configured for that traffic class. ECN is commonly used alongside PFC to provide proactive congestion signaling, but PFC is the mechanism that directly prevents loss when buffers approach critical utilization.

Traffic shaping in option A may moderate burst rates but does not establish lossless transport. A high DSCP marking in option C provides classification and forwarding preference, not loss prevention. Weighted fair queuing in option D allocates scheduling bandwidth but also does not guarantee that packets will not be discarded during congestion.

Study Guide Reference: 3.1.a Congestion control mechanisms — PFC, ECN, ETS; 3.1.b RoCE/RoCEv2; 3.1.c QoS.

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

Cisco's validated guidance for connecting VAST Data storage through an ACI fabric explicitly configures the RDMA storage class with Weighted Random Early Detection and Congestion Notification enabled . This makes option A directly consistent with Cisco's documented configuration.

In Cisco's VAST Data ACI design example, storage traffic arrives marked with DSCP 26 and is assigned to the Level2 QoS class. PFC is enabled for the corresponding no-drop DSCP, bandwidth is reserved for storage traffic, the congestion algorithm is configured as WRED, and congestion notification is enabled.

WRED and ECN-style congestion notification work together to detect developing queue pressure before buffers overflow. Rather than waiting for tail-drop conditions, the network can mark congestion-capable traffic so RoCEv2 endpoints reduce their transmission rates. PFC provides the complementary no-drop behavior when congestion becomes sufficiently severe.

Option B disables the required congestion signaling. Options C and D use Tail Drop, which Cisco's documented VAST RDMA storage class does not use. Tail Drop is instead shown in the same Cisco design for control-plane and ordinary traffic classes where lossless RDMA behavior is not required.

This configuration is therefore not merely a generic QoS preference; it directly follows Cisco's published ACI-to-VAST storage design.

Study Guide Reference: AI Infrastructure Deployment and Data Management — QoS, ECN/WRED, PFC, RDMA storage, and lossless fabric configuration.

The surveillance workload creates a substantial persistent-capacity requirement across every location. Even at the stated minimum of ten cameras, each store generates approximately 240 GB per day and roughly 3.36 TB over fourteen days before considering filesystem overhead, redundancy, additional cameras, or growth. A scalable IP-based shared-storage architecture is therefore the appropriate option.

Cisco Unified Edge is designed around integrated high-speed Ethernet networking and supports network-accessible storage through standard IP mechanisms. Cisco's validated Unified Edge guidance describes network storage using protocols such as NFS and iSCSI , while explicitly noting that Fibre Channel is not validated in that design. Unified Edge also supports software-defined and distributed storage architectures carried over its Ethernet infrastructure.

Fibre Channel would introduce specialized SAN adapters, switches, cabling, and operational complexity that are generally inappropriate for a cost-sensitive, highly distributed retail edge. InfiniBand is optimized for specialized high-performance computing rather than economical video retention. Local storage could hold surveillance data at each store, but the question explicitly requires a centralized storage solution and long-term capacity that can be managed across locations.

IP-based shared storage therefore provides the best combination of scalability, standardization, cost efficiency, and Unified Edge compatibility.

Study Guide Reference: AI Infrastructure Components and Architecture — edge AI storage, IP storage, scalability, capacity, and deployment requirements.

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

Cisco UCS X-Series is the strongest fit because it is designed as a modular, scalable compute platform that can support conventional enterprise workloads and GPU-accelerated AI workloads within the same architectural framework. Cisco explicitly positions UCS X-Series for workload consolidation, allowing compute nodes and GPU resources to be added as requirements evolve without replacing the entire infrastructure. The platform supports substantial memory capacity, virtualization, GPU acceleration, and centralized lifecycle management through Cisco Intersight.

The current UCS X-Series portfolio supports X210c and X215c compute nodes, X580p GPU expansion, and X-Fabric connectivity. Cisco further positions the platform for AI workloads through high-bandwidth, low-latency GPU connectivity and scalable GPU and CPU configurations.

UCS M-Series is not the current strategic modular platform for these requirements. Unified Edge is optimized for distributed edge deployments rather than a large, expanding enterprise data center. A standalone C-Series deployment can provide powerful GPU servers, but it does not offer the same chassis-level composability and resource expansion model described in the scenario.

Study Guide Reference: 2.0 AI Infrastructure Components and Architecture — 2.2 Evaluate compute deployment based on CPU, GPU, memory, virtualization, scalability, redundancy, and workload requirements.

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

The PFC pause-frame transmission rate per interface is the most directly relevant congestion indicator for an AI training fabric carrying RoCEv2 traffic. Priority Flow Control protects lossless traffic classes by transmitting pause frames when a receiving interface or switch queue approaches a congestion threshold. An elevated or sustained PFC pause rate therefore indicates that the lossless RDMA traffic class is repeatedly encountering queue pressure.

This is particularly significant for distributed AI training. GPU collective operations require synchronized communication between large numbers of accelerators, and excessive congestion can create tail latency, reduce effective network throughput, and extend Job Completion Time. Cisco AI networking guidance consequently treats PFC, ECN, queue occupancy, drops, and congestion telemetry as key operational signals for AI backend fabrics.

Spanning-tree topology changes are largely irrelevant in a modern routed or VXLAN-EVPN AI backend. BGP EVPN route counts are useful for control-plane capacity assessment but do not directly reveal congestion. VXLAN encapsulation rates measure traffic volume rather than whether buffers are becoming saturated.

PFC should not be interpreted as inherently problematic—some pause activity may occur during microbursts. However, unusually high or persistent pause-frame rates are a strong signal that congestion behavior requires investigation.

Study Guide Reference: AI Infrastructure Operations and Troubleshooting — RoCEv2 monitoring, PFC, congestion, telemetry, and AI training performance.

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

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.

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

Cisco Intersight Fleet Management is designed specifically for large numbers of geographically distributed systems where infrastructure and workloads must be deployed consistently across remote sites. Cisco describes Fleet Management as providing location profiles and reusable Blueprints that support zero-touch provisioning of hardware and operating systems after devices are claimed in Intersight. This directly addresses the scenario's requirement to manage different branch-office locations and automate their OS installation and configuration at scale.

A fleet abstraction removes the operational burden of individually configuring every remote server. Administrators can define standardized site and workload characteristics centrally, then reproduce the configuration across distributed infrastructure with policy consistency. This is particularly valuable for edge AI, where hundreds or thousands of sites may host inference workloads without dedicated local IT personnel.

Domain management focuses on UCS domains rather than mass deployment across geographically distributed sites. Server management provides lifecycle operations for individual or grouped servers but does not provide the location-profile and Blueprint-based fleet abstraction requested. Chassis management controls chassis-level resources and therefore does not address workload rollout across numerous sites.

Study Guide Reference: AI Infrastructure Deployment and Data Management — Cisco Intersight deployment, orchestration, provisioning, and distributed AI infrastructure.

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

Cisco Nexus 9000 integration with NVIDIA adaptive-routing capabilities requires the Nexus switch to enable the Spectrum-X hardware profile . Cisco's current NX-OS configuration guide explicitly specifies the global configuration command hardware profile spectrum-x to enable NVIDIA Spectrum-X adaptive routing. When a Nexus switch peers with a supported NVIDIA NIC, this capability allows the NIC to handle packet reordering created by granular techniques such as per-packet Dynamic Load Balancing.

This is particularly important for AI training because large synchronized RDMA flows can create uneven utilization under conventional hash-based ECMP. Cisco explains that per-packet DLB can spray packets over multiple paths and that NVIDIA adaptive routing/direct data placement enables the receiver to correctly handle packets that arrive out of order, improving utilization and collective-operation performance.

Option A is not the documented NX-OS configuration syntax. Option B is not the Cisco-prescribed Nexus integration command. Option D may be relevant to traffic classification in other designs but does not activate Spectrum-X adaptive-routing interoperability.

Therefore, the Cisco-documented configuration is C. This differs from the supplied file's marked answer B.

Study Guide Reference: 3.0 AI Infrastructure Deployment and Data Management — 3.1.d Load distribution.

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

NVIDIA Collective Communications Library (NCCL) is the appropriate framework for validating communication performance between NVIDIA GPU nodes. NCCL provides highly optimized implementations of collective operations such as AllReduce, AllGather, Reduce, Broadcast, and ReduceScatter. These operations closely represent the communication patterns generated by distributed AI training and therefore provide much more meaningful validation of GPU-cluster performance than conventional network-throughput tests.

NCCL-based benchmarks can reveal whether GPU-to-GPU communication is achieving expected bandwidth and latency across NVLink, PCIe, and the external backend network. They are particularly useful when validating RoCEv2 fabrics because distributed training performance depends on collective communication efficiency rather than simple host-to-host TCP throughput.

iPerf measures conventional TCP or UDP network performance between hosts and is useful for basic network validation, but it does not exercise NVIDIA GPU collective communications. Spirent and Ixia provide sophisticated packet-generation and network-testing platforms, yet they test the network primarily from a packet-forwarding perspective rather than measuring actual GPU collective-operation behavior.

For a newly deployed NVIDIA AI cluster, NCCL benchmarking therefore provides workload-representative validation of the end-to-end GPU communication architecture and can expose problems involving topology, NIC configuration, congestion control, bandwidth imbalance, or fabric design.

Study Guide Reference: AI Infrastructure Operations and Troubleshooting — performance benchmarking, NVIDIA GPU communications, backend-fabric validation, and distributed AI workload testing.

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

The UCS X210c M8 combined with the UCS X580p PCIe Node satisfies the complete requirement set. The X210c M8 uses Intel Xeon 6 processors, while the X580p provides modular GPU expansion and supports up to four PCIe GPUs. Cisco specifically positions this combination for generative AI, inference, and other GPU-accelerated workloads. Management is policy-driven through Cisco Intersight, providing the required cloud-based operational model.

The X580p also supports NVIDIA H200 NVL GPUs and NVLink Bridge capabilities. This is significant where low-latency communication is required between specific GPU pairs because NVLink provides substantially higher-bandwidth GPU-to-GPU communication than standard PCIe-only communication. Cisco's UCS ordering guidance specifies that H200 NVL supports NVL Bridge configurations with a minimum of two GPUs.

Options C and D are high-density AI systems, but they use AMD EPYC-based architectures rather than satisfying the stated Intel CPU requirement. Option A likewise does not match the specified X-Series composability, cloud-managed GPU resource model, and Intel-based requirement as directly as the X210c M8 configuration.

Study Guide Reference: 2.0 AI Infrastructure Components and Architecture — 2.2 Compute deployment; 2.4 power and efficiency considerations.

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

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.

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

A rail-optimized architecture is intentionally designed so that communication among corresponding GPU ranks within a single scalable unit can remain on the rail or leaf switches. This provides single-hop forwarding and avoids unnecessary traversal through spine switches, reducing latency for collective communication.

Spines become necessary when the deployment expands beyond one scalable unit. Cisco explicitly documents that multiple scalable units can be interconnected through leaf-and-spine switching. Traffic among GPUs inside one scalable unit benefits from rail-optimized single-hop communication, whereas traffic between GPUs located in different scalable units traverses the spine layer.

Therefore, option C precisely describes when spine switches provide architectural value: scaling the AI fabric beyond the boundaries of one scalable unit .

Option A is inaccurate because the rail design already provides the required local GPU bandwidth within the scalable unit; adding spines is not primarily intended to increase local rail bandwidth. Option B mischaracterizes the principal design purpose. Although additional topology can contribute to resiliency, spines are introduced fundamentally for interconnecting scalable units and enabling scale-out. Option D is also incorrect because increased buffering is not the architectural reason for introducing a spine tier.

Study Guide Reference: AI Infrastructure Components and Architecture — rail-optimized topology, scalable units, nonblocking network design, latency, and horizontal scaling.

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

Congestion Notification Packets are control-feedback messages used by RoCEv2 congestion-management mechanisms. When a receiving endpoint observes an ECN-marked packet, it generates a CNP toward the sender, instructing the transmitting endpoint to reduce its transmission rate. Losing these packets would delay congestion response and allow queues to continue building.

Cisco's validated RoCEv2-over-VXLAN design explicitly states that CNP packets use DSCP 48 and are classified into a high-priority queue . In Cisco's example, ordinary RoCEv2 traffic is mapped to QoS group 3, while CNP is mapped to QoS group 7. Cisco further states that the high-priority classification ensures that CNP packets are not dropped in the network.

Traffic shaping in option A would regulate CNP transmission rather than guarantee timely feedback. Option C places CNP in the same potentially congested queue as the data traffic that generated the congestion, defeating the purpose of reliable feedback. Option D is also incorrect because PFC is intended to protect a lossless data priority; CNP itself should be forwarded through a high-priority queue and should not depend on pause behavior.

Study Guide Reference: AI Infrastructure Deployment and Data Management — RoCEv2, ECN, CNP, QoS classification, and congestion management.

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