2.0 Compute
Free Implementing Cisco Data Center Core Technologies practice — 6 questions on 2.0 Compute, with explanations. No sign-up. Full 12-question mixed test →
A UCS admin has 20 B-Series blades with service profiles derived from a single updating template. The admin must change the BIOS policy for only 5 of these servers without affecting the other 15, while preserving the pool-derived identities (MAC, UUID, WWPN) already assigned to those 5 profiles. Which approach BEST meets this requirement?
Unbinding a service profile from its template converts it to a standalone profile while retaining its currently assigned pool-derived identities as static values. This lets the admin change the BIOS policy locally on exactly those 5 profiles without touching the other 15 still bound to the template.
A Cisco UCS domain has a MAC address pool containing exactly 20 addresses, all consumed by 20 associated service profiles. An administrator attempts to associate a 21st service profile referencing the same MAC pool. What is the outcome?
UCS identity pools are hard limits enforced for global uniqueness. When exhausted, the new service profile cannot be assigned a MAC address and enters a config-failure/pending state with a fault indicating insufficient pool resources, until the pool is expanded or an address is freed.
A service profile template built for Windows Server workloads on Cisco VIC 1400-series adapters requires vNICs and vHBAs to be enumerated by the OS in a specific PCIe slot order to match driver binding expectations. Which UCS Manager policy controls this behavior?
The vNIC/vHBA Placement Policy explicitly controls PCIe enumeration order (via virtual connection/vCon assignment) of vNICs and vHBAs as presented to the host OS, which is critical for consistent driver-to-interface mapping.
An organization is migrating fabric interconnects from UCS Manager to Intersight Managed Mode (IMM) and requires Fibre Channel connectivity to a SAN array with local zoning performed directly on the fabric interconnect. Which capability is NOT available when the fabric interconnects are running in IMM?
Fabric interconnects operating under Intersight Managed Mode support Fibre Channel connectivity only in NPV (N Port Virtualization) mode. Native FC Switching Mode with local zoning tables on the FI itself is not supported in IMM, so zoning must be performed upstream on an MDS or Nexus FC switch.
During initial fabric interconnect bring-up, an administrator mistakenly configures the ports connecting to the upstream Nexus switches as Server Ports instead of Uplink Ports. What is the immediate operational impact?
Server ports run UCS's proprietary chassis/IOM discovery protocol expecting a blade chassis or FEX connection. When miswired to core switches, the ports cannot establish valid uplink forwarding, and interfaces typically remain in a discovery-failed/unknown state, blocking all north-south traffic on those links.
A boot policy for SAN boot contains two vHBA boot entries, Fabric-A and Fabric-B, both mistakenly configured with the same boot order number (2), with no entry assigned order number 1. What happens when this service profile attempts to associate?
Cisco UCS boot policies require every boot device entry (vHBA, vNIC, CD/DVD, local disk, etc.) to have a unique, sequential order number. Duplicate order values are detected as an invalid boot policy configuration, generating a config-failure fault that blocks proper association/boot until corrected.
Ready for the real thing?
The full course has two full-length practice tests, video lessons for every exam domain, hands-on labs and detailed answer explanations.
Start my full course on Udemy →