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

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.

Cisco UCS X-Series Direct is specifically designed for edge, retail, remote-office, and branch-office environments that require the operational characteristics of UCS without deploying separate top-of-rack Fabric Interconnect appliances. It combines the UCS X9508 chassis with integrated UCS 9108 100G Fabric Interconnect modules and supports centralized management through Cisco Intersight.

The decisive requirement is 200 Gbps of unified fabric connectivity per compute node . Cisco documents that two UCS 9108 100G Fabric Interconnect modules provide a total of 200 Gbps per compute node. The solution can support up to eight compute nodes per chassis and is explicitly positioned for remote and branch-office deployments.

The S3260 is primarily a storage-intensive UCS platform and does not represent the required branch-oriented modular compute architecture. Unified Edge is purpose-built for edge locations, but the specific 200-Gbps-per-compute-node requirement aligns directly with X-Series Direct. The C885A M8 is a high-density rack server for GPU-intensive AI workloads rather than a chassis solution optimized for these branch deployment requirements.

Study Guide Reference: 2.0 AI Infrastructure Components and Architecture — 2.2 compute scalability and redundancy; 2.5 hybrid AI deployment.

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

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.

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

The thermal events are the strongest diagnostic indicator in the scenario and should direct troubleshooting toward the server's cooling environment before workload-level tuning . Excessive temperature can cause processor or accelerator thermal throttling, which directly produces intermittent performance degradation and latency spikes even when CPU, memory, GPU, and storage utilization otherwise appear normal.

Cisco's C-Series installation requirements emphasize correct airflow and specifically warn that obstructing server ventilation can cause overheating, higher fan speeds, and increased power consumption. Cisco's C885A M8 documentation, representative of modern AI-oriented UCS C-Series platforms, specifies twelve hot-swappable system fans for proper front-to-back cooling.

Therefore, the administrator should first inspect ambient temperature, cold-aisle/hot-aisle conditions, physical airflow, obstructions, and fan health. Any failed fan should be replaced promptly.

Option A is a sensible performance-analysis step when there is no stronger hardware fault indicator, but repeated thermal events make it secondary here. Storage inspection in option B is not supported by the symptoms. Option C focuses on power delivery, yet the event evidence specifically points toward thermal management rather than insufficient PSU capacity.

Troubleshooting should follow the fault evidence, beginning with the lowest-level physical condition that can explain the observed symptoms.

Study Guide Reference: AI Infrastructure Operations and Troubleshooting — UCS health monitoring, environmental faults, thermal conditions, and performance troubleshooting.

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

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 uploaded source marks C and D . GPU Memory Utilization in option D is clearly relevant: GPU memory pressure is a critical accelerator metric because model weights, activations, KV caches, tensors, and training state consume GPU-attached memory. Cisco AI monitoring material explicitly includes GPU memory utilization among the telemetry used for AI infrastructure visibility.

Option C, Active CPU Utilization , is useful as a supporting performance metric because AI workloads can become CPU-bound during data preprocessing, tokenization, orchestration, input-pipeline execution, or host-to-device preparation. A CPU bottleneck can therefore leave GPUs underutilized even when sufficient accelerator capacity exists.

However, the question as written has a notable construction issue: Cisco documentation treats GPU utilization itself as a principal metric for evaluating accelerator utilization, but that metric is absent from the available answer choices. Cisco current material explicitly identifies GPU utilization and GPU memory utilization as AI monitoring measurements.

Therefore, CD is retained because it is the answer supplied by the source , but the technically ideal metric pair would be GPU Utilization + GPU Memory Utilization if GPU Utilization were offered.

Study Guide Reference: AI Infrastructure Operations and Troubleshooting — GPU utilization, GPU memory utilization, host-resource bottlenecks, and AI performance monitoring.

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

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.

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

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.

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

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.

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

In Cisco Intersight Managed Mode, Fabric Interconnect physical port roles and port-channel definitions are configured through the Port Policy . Cisco's current Intersight configuration documentation states that a Port Policy configures ports and port roles on a Fabric Interconnect and permits administrators to enable or disable individual ports or port channels. Supported roles include Ethernet uplinks and Ethernet uplink port channels.

The Port Policy is subsequently associated with the UCS Domain Profile. Cisco documents that a Domain Profile configures an FI pair through reusable policies and controls ports, port channels, VLANs, and VSANs. During Domain Profile creation, the administrator attaches the appropriate Port Policy to each Fabric Interconnect.

A LAN Connectivity Policy is used primarily at the server-profile level to define vNIC connectivity. A Network Connectivity Policy configures DNS-related server-management settings rather than FI uplink topology. An Ethernet Network Group Policy defines VLAN groups associated with Ethernet connectivity and can be referenced by uplink configurations, but it does not itself create the FI port channel.

Consequently, the policy that must be changed to build the multiple-100-GbE uplink port channel is the Port Policy .

Study Guide Reference: AI Infrastructure Deployment and Data Management — Intersight Managed Mode, UCS Domain Profiles, Fabric Interconnect port configuration, and uplink resiliency.

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

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.

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

Cisco NX-OS configures interface-specific Dynamic Load Balancing through the DLB hardware profile , not independently under each physical interface. The administrator first enters hardware profile dlb and then uses dlb-interface within that submode to specify the interfaces on which DLB is enabled. Cisco's current Nexus 9000 documentation provides examples such as dlb-interface Eth1/5,Eth1/7,Eth1/17..., which directly supports selecting only odd-numbered interfaces.

Therefore, option C most accurately describes the required configuration: create or enter the DLB hardware profile and provide the selected interface list. Cisco also notes that changes to this interface list generally require a switch reload before they become effective.

Option A incorrectly implies that dlb-interface is applied in standard interface configuration mode. It is actually configured under the hardware profile dlb submode. Option B describes policy-driven DLB, which is a separate mechanism requiring QoS classification with set dlb mode; it is unnecessary when the requirement is simply to enable DLB on a predetermined set of interfaces. Option D reverses the logic and would not enable the requested interfaces.

Correction: the uploaded file marks A , but current Cisco NX-OS configuration documentation supports C as written.

Study Guide Reference: AI Infrastructure Deployment and Data Management — load distribution and Dynamic Load Balancing.

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

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.

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

Selecting and correctly engineering the Nexus fabric is the most important option for achieving scalable AI performance because distributed LLM training depends heavily on communication among GPUs located in different servers. The C885A M8 provides eight high-performance GPUs and high-speed NICs, but cluster-level performance depends on whether the network can transport collective-communication traffic at high bandwidth with extremely low latency and negligible packet loss.

Cisco AI reference architectures use dedicated, nonblocking backend fabrics based on Cisco Nexus switching for GPU-to-GPU RoCEv2 traffic. Cisco specifically applies rail-optimized designs, PFC, ECN, high-speed Ethernet, and nonblocking leaf-spine connectivity to preserve collective communication efficiency as GPU clusters scale.

Option B overemphasizes host CPU cores. LLM training on the C885A is primarily GPU accelerated, and additional CPU capacity does not compensate for a congested inter-node fabric. Option C is essential for availability but does not directly optimize distributed training throughput or scalability. Option D would actively undermine workload capability because adequate host memory is important for data preprocessing, orchestration, caching, and other AI operations.

Therefore, the network fabric's topology, bandwidth, congestion-control behavior, and latency are central to realizing the performance of a multi-node C885A deployment.

Study Guide Reference: AI Infrastructure Components and Architecture — evaluate network and compute deployments based on bandwidth, latency, scalability, GPU characteristics, and workload 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.

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

VXLAN EVPN provides scalable logical segmentation without requiring physically separate fabrics. Separate VXLAN Network Identifiers can isolate individual AI training projects, while Cisco's Group Policy Option adds a security group identifier to the VXLAN header and enables granular microsegmentation through security-group policies. This makes it possible to isolate tenant or project traffic while selectively allowing access to common services such as centralized storage.

Cisco specifically describes GPO as supporting microsegmentation within VXLAN EVPN fabrics and granular traffic control between application segments. This approach preserves a high-performance shared fabric, avoiding the operational complexity and resource inefficiency of constructing physically separate networks for every project. Cisco also positions VXLAN EVPN as an architecture for AI/ML environments requiring segmentation, secure multitenancy, and scalable high-throughput communication.

Option A provides strong isolation but wastes switching resources and complicates shared-storage connectivity. Option C relies on conventional VLAN boundaries and centralized router ACL enforcement, introducing scaling and potentially additional forwarding constraints. Option D confuses QoS classification with security segmentation; DSCP identifies service classes but is not a security-isolation mechanism.

Study Guide Reference: 2.1 Evaluate network deployment based on bandwidth, latency, scalability, and security.

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

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.

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