300-640 Implementing Cisco Data Center AI Infrastructure (DCAI) Questions and Answers

In an Intersight Managed Mode UCS domain, DNS and NTP configuration is policy-controlled through the UCS Domain Profile deployed to the Fabric Interconnects. Changes entered locally through the Device Console can restore temporary reachability, but the policy configuration maintained by Intersight remains authoritative. If the Domain Profile still contains the previous DNS or NTP configuration, a subsequent deployment can overwrite the locally modified values.

Cisco documents that the Domain Profile references both the Network Connectivity Policy , which contains DNS settings, and the NTP Policy , which defines the NTP servers. The appropriate persistent remediation is therefore to edit the configuration associated with the deployed Domain Profile and redeploy it.

The IMC Access Policy applies primarily to server-management addressing and access rather than Fabric Interconnect DNS/NTP persistence. A Device Connector policy does not supply these domain DNS settings. Option C incorrectly applies a Network Connectivity Policy to the blade chassis; for the Fabric Interconnect domain, the relevant network-connectivity configuration is referenced through the UCS Domain Profile.

Cisco also advises that DNS and NTP should be configured on the management interface rather than being treated as Device Connector settings.

Study Guide Reference: AI Infrastructure Deployment and Data Management — Intersight Managed Mode, UCS Domain Profiles, DNS/NTP policies, and management connectivity.

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.

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

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.

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

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.

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

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.

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

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.

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

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.

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

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.

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

NVIDIA NVLink is a high-bandwidth interconnect technology designed primarily to accelerate communication between GPUs. Within systems such as the Cisco UCS C885A M8 equipped with NVIDIA HGX H100 or H200 GPUs, NVLink creates a high-speed GPU interconnect that allows accelerator devices to exchange data substantially more efficiently than would be possible through conventional host-mediated communication paths.

Cisco specifically documents that the eight NVIDIA H200 SXM GPUs in the C885A M8 are interconnected through high-speed NVLink interconnects . Cisco positions this architecture for demanding workloads such as large language model training, fine-tuning, inference, and RAG, where frequent exchange of tensors, gradients, and intermediate values between GPUs can become a major performance constraint.

Option A concerns remote GPU access and resource virtualization, which require separate virtualization or orchestration technologies. Option B describes platform power and thermal management rather than interconnect functionality. Option C incorrectly characterizes NVLink as a secure external-storage transport; storage connectivity instead uses technologies such as Ethernet/RDMA, NVMe, GPUDirect Storage, or Fibre Channel depending on the architecture.

The defining examination concept is therefore direct, high-bandwidth, low-latency communication among GPUs within an accelerated computing platform.

Study Guide Reference: AI Infrastructure Components and Architecture — GPU architecture, GPU interconnects, compute performance, latency, and scalability.

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

backend network

frontend network

storage network

management network

Large AI environments normally separate traffic into purpose-built fabrics because GPU collective communication, storage I/O, application access, and infrastructure management have fundamentally different performance and availability characteristics. Cisco identifies the backend network as the east-west fabric dedicated to inter-GPU communication. It carries high-bandwidth RoCEv2/RDMA traffic associated with distributed training and must provide exceptionally low latency and lossless behavior.

The frontend network provides north-south connectivity between AI nodes and the wider data center, supporting application access, inference traffic, general data movement, logging, and other in-band services. The storage network connects compute nodes to shared datasets, model checkpoints, and high-performance parallel or distributed storage systems. Cisco AI POD designs may use dedicated storage-leaf connectivity to prevent storage traffic from interfering with backend GPU collective communication. The management network serves out-of-band management interfaces for servers, switches, storage platforms, and other infrastructure components. Cisco AI reference architectures explicitly distinguish backend, frontend/storage, and management connectivity for these purposes.

Maintaining these traffic domains independently improves deterministic performance, fault isolation, congestion control, security, and operational manageability.

Study Guide Reference: AI Infrastructure Components and Architecture — network fabrics, bandwidth, latency, scalability, and AI infrastructure connectivity.

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

Cisco Intersight's automated OS installation workflow requires the operating-system installation media to be available through the Software Repository and an appropriate OS configuration source to supply unattended-install parameters. Cisco's UCS X-Series installation workflow first adds an OS image link to the Software Repository and subsequently selects an OS configuration file during the installation wizard.

The configuration file contains or exposes variables needed for unattended deployment, such as hostname, IP addressing, gateway, DNS configuration, credentials, and other operating-system installation parameters. Cisco also supports validated configuration templates for supported operating systems, depending on the deployment mode and OS version.

A firmware policy is not an OS-installation prerequisite; firmware lifecycle configuration is separate from installation of the guest operating system. A virtual KVM policy is likewise unnecessary for an unattended Cisco Mode installation.

A Server Configuration Utility can be relevant to certain Intersight installation workflows and older/standalone platform procedures, but the question specifically asks for the Cisco Mode prerequisite pair represented by the available choices. The combination of the OS image and operating-system configuration file is therefore the intended answer.

Study Guide Reference: AI Infrastructure Deployment and Data Management — Cisco Intersight automated provisioning, Software Repository, and operating-system deployment.

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

hardware profile dlb

dlb-interface all

mode flowlet

The exhibit shows materially uneven utilization across the eight interfaces, with receive utilization ranging from approximately 32.5% to 75.3%. Cisco Dynamic Load Balancing addresses this problem by considering current path utilization rather than relying exclusively on static ECMP hashing.

The configuration begins with hardware profile dlb, which enters the DLB hardware-profile context. dlb-interface all enables DLB on all eligible Layer 3 physical interfaces. Cisco documents both an explicit interface list and the all keyword for this purpose. The document's supplied drag-and-drop answer then selects mode flowlet. Cisco defines flowlet load balancing as the default DLB mode, in which forwarding decisions use Dynamic Resilient Ethernet metrics to select less-loaded paths while maintaining packet ordering within a flowlet.

Cisco also supports per-packet DLB, which can produce even greater path utilization but can reorder packets. When NVIDIA adaptive-routing capabilities are explicitly enabled and endpoints can handle reordering, Cisco documents per-packet DLB as an optimized alternative. That additional prerequisite is not stated in this question.

Therefore, the source-derived configuration is DLB / all interfaces / flowlet .

Study Guide Reference: AI Infrastructure Deployment and Data Management — Dynamic Load Balancing, ECMP optimization, AI backend fabrics, and traffic distribution.

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

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.

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

Rapid provisioning supports scalability by reducing the time required to make compute, GPU, networking, storage, and orchestration resources available for workloads. The most appropriate description is therefore the efficient launch of computational platforms . When new AI capacity can be provisioned consistently and quickly, organizations can expand training environments, increase inference capacity, respond to workload bursts, and introduce additional accelerator resources without lengthy manual configuration.

Cisco's DCAI objectives explicitly cover orchestration as a component of AI environments and require candidates to evaluate infrastructure scalability. Cisco also emphasizes that AI infrastructure must scale to accommodate changing workloads and that cloud-oriented infrastructure offers rapid access to computational resources when demand changes.

Option A introduces fragmented management, which generally increases operational complexity. Option B restricts connectivity and therefore conflicts with scalable distributed AI execution. Option C explicitly delays resource availability and is the opposite of rapid provisioning.

The architectural objective is to make infrastructure consumption repeatable and automated. Efficient provisioning allows the underlying platform to expand at the pace demanded by GPU-intensive training and production inference rather than becoming an operational bottleneck.

Study Guide Reference: 1.0 AI Fundamentals and Applications — 1.5.d Orchestration; AI infrastructure scalability concepts.

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

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.

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