Courseiva

CCNA Dc Compute Questions

75 of 104 questions · Page 1/2 · Dc Compute topic · Answers revealed

Practice these questionsExam hubAll questions
1
Multi-Selecthard

Which THREE components are required to configure a Cisco UCS Direct-attached storage environment using SAS expanders?

Select 3 answers
A.SAS cables connecting the storage enclosure to the server's storage controller.
B.SAS expanders within the enclosure to connect multiple drives.
C.SAS hard drives installed in the storage enclosure.
D.Fibre Channel over Ethernet (FCoE) uplinks from the storage enclosure to the Fabric Interconnect.
E.Fibre Channel switch for SAN connectivity.
AnswersA, B, C

Direct SAS cabling is required for connectivity.

Why this answer

Option A is correct because in a Cisco UCS Direct-attached storage environment using SAS expanders, SAS cables are required to physically connect the storage enclosure to the server's storage controller (typically an LSI-based SAS HBA). This direct cabling enables the SAS protocol to carry SCSI commands and data between the server and the drives without any intervening network fabric.

Exam trap

Cisco often tests the distinction between Direct-attached storage (SAS) and Fabric-attached storage (FCoE/Fibre Channel), so the trap here is assuming that any storage enclosure requires Fabric Interconnect or SAN components, when in fact Direct-attached storage uses only SAS cabling and expanders.

Practice this question →
2
MCQmedium

A financial services firm has deployed Cisco UCS C-Series rack servers running VMware vSphere 7.0. They use Cisco Intersight for management. Recently, a critical application server (Server-A) became unresponsive. The Intersight dashboard shows the server's health status as 'Warning' with a firmware compliance alert: the server's Cisco Integrated Management Controller (CIMC) firmware version is 4.0(1a), while the Intersight firmware baseline is 4.2(1c). The server is running ESXi 7.0u2 on a local datastore. The storage is provided by a Cisco MDS switch via Fibre Channel. The server has two 10GbE uplinks to the fabric interconnect. The engineer notices that the vCenter Server cannot communicate with Server-A, and all VMs on that host are isolated. The engineer suspects the issue is related to the firmware mismatch. What is the most appropriate first step to resolve this issue while minimizing downtime?

A.Check vCenter logs to determine why communication failed.
B.Reinstall ESXi on Server-A to ensure a clean operating system.
C.Upgrade the CIMC firmware on Server-A from 4.0(1a) to 4.2(1c) using Intersight's firmware update capability.
D.Change the Intersight firmware baseline to match the current CIMC version (4.0(1a)).
AnswerC

Directly upgrades the firmware to the compliant version, resolving the underlying issue.

Why this answer

The CIMC firmware mismatch (4.0(1a) vs. baseline 4.2(1c)) is a known cause of management-plane instability in Cisco UCS C-Series servers managed by Intersight. Upgrading the CIMC firmware to match the Intersight baseline using Intersight's built-in firmware update capability directly addresses the root cause, restoring proper communication between the server, Intersight, and vCenter, while minimizing downtime by avoiding disruptive OS-level changes.

Exam trap

Cisco often tests the misconception that a firmware mismatch only affects compliance reporting and not actual data-plane or management-plane functionality, leading candidates to choose a non-disruptive but ineffective option like changing the baseline (Option D) instead of performing the necessary firmware upgrade.

How to eliminate wrong answers

Option A is wrong because checking vCenter logs is a diagnostic step that does not resolve the firmware mismatch; the root cause is already identified (CIMC firmware version out of compliance). Option B is wrong because reinstalling ESXi is unnecessarily disruptive and does not fix the CIMC firmware version mismatch, which is the underlying cause of the management communication failure. Option D is wrong because changing the Intersight firmware baseline to match the outdated CIMC version (4.0(1a)) would bypass the compliance alert but leave the server running an unsupported and potentially buggy firmware version, failing to resolve the actual issue and risking future stability.

Practice this question →
3
Multi-Selectmedium

A UCS administrator must ensure that a service profile can be updated without disrupting production traffic. Which two configuration options support this requirement? (Choose two.)

Select 2 answers
A.Use of a service profile template with 'Disruptive Update'
B.Maintenance policy with 'Immediate'
C.Use of a service profile template with 'Upgrade Policy'
D.Maintenance policy with 'User Ack' and 'Enable Fast Reboot'
E.Maintenance policy with 'On Next Boot'
AnswersD, E

User acknowledgment provides manual control; fast reboot minimizes downtime.

Why this answer

Option D is correct because a maintenance policy with 'User Ack' requires manual acknowledgment before the update proceeds, and enabling 'Fast Reboot' minimizes traffic disruption by reducing the reboot time. Option E is correct because a maintenance policy with 'On Next Boot' defers the update until the next scheduled reboot, allowing the administrator to control when the change takes effect and avoid impacting production traffic.

Exam trap

Cisco often tests the distinction between 'Disruptive Update' and non-disruptive maintenance policies, and the trap here is that candidates confuse 'Upgrade Policy' (a non-existent term) with 'Maintenance Policy', or assume 'Immediate' is acceptable because it is fast, ignoring the disruption requirement.

Practice this question →
4
Multi-Selectmedium

Which TWO statements correctly describe the use of Cisco UCS Manager service profiles for server deployment?

Select 2 answers
A.Service profiles can only be applied to servers of the same model.
B.Service profiles decouple server identity from hardware, enabling rapid provisioning.
C.A service profile can be associated with multiple servers simultaneously.
D.Service profiles are stored locally on the server's boot drive.
E.Service profiles include policies for firmware, BIOS, boot order, and network.
AnswersB, E

Service profiles abstract server identity, allowing quick redeployment.

Why this answer

Service profiles decouple the logical server identity (UUID, MAC addresses, WWPNs) from the physical hardware. This allows an administrator to rapidly provision or repurpose a server by simply associating the profile with a different blade or rack server, without reconfiguring the OS or SAN/NIC settings. This abstraction is the core value of Cisco UCS Manager for scalable, stateless computing.

Exam trap

The trap here is that candidates often confuse service profiles with server templates or think they are tied to specific hardware models (Option A), when in fact the entire purpose of UCS stateless computing is to abstract identity from hardware.

Practice this question →
5
MCQeasy

A Cisco Intersight managed UCS domain has a policy that requires all firmware updates to be applied within 30 days of release. An engineer needs to check compliance for a specific server. Which Intersight feature should be used?

A.Software repository
B.Actions tab with pending updates
C.Compliance and drift management
D.Firmware update policy
AnswerC

This feature checks if firmware versions meet the defined baseline.

Why this answer

Compliance and drift management in Intersight continuously monitors the firmware versions of managed UCS servers against the defined baseline policies. When a policy requires updates within 30 days of release, this feature automatically detects servers that are out of compliance and reports the drift, allowing the engineer to verify compliance for a specific server without manual checks.

Exam trap

Cisco often tests the distinction between a policy that defines an action (like firmware update policy) and a monitoring/reporting feature (like compliance and drift management), leading candidates to confuse the policy that enforces updates with the tool that checks compliance.

How to eliminate wrong answers

Option A is wrong because the software repository is used to store and manage firmware images, not to check compliance against a time-based policy. Option B is wrong because the Actions tab with pending updates shows only immediate pending firmware actions, not historical or policy-based compliance status over a 30-day window. Option D is wrong because a firmware update policy defines the update schedule and target version, but it does not provide a compliance report or drift analysis for a specific server against a release-date-based policy.

Practice this question →
6
Multi-Selectmedium

Which TWO options are correct regarding Cisco UCS server profiles? (Select TWO.)

Select 2 answers
A.Service profiles can be updated while the server is in OS configuration.
B.Resource pools, such as UUID pools, can be shared across service profile templates.
C.A vHBA in a service profile inherits the boot policy automatically.
D.A service profile can be associated with multiple servers simultaneously to provide load balancing.
E.A service profile becomes operational only after it is associated with a physical server.
AnswersB, E

Pools are defined globally and can be used by multiple templates.

Why this answer

Option B is correct because resource pools like UUID pools, MAC pools, and WWN pools are global objects in Cisco UCS Manager that can be shared across multiple service profile templates. This allows administrators to define a pool once and reference it from any template, ensuring consistent allocation and avoiding conflicts.

Exam trap

The trap here is that candidates often confuse the one-to-one binding of service profiles to servers with load-balancing concepts, or assume that boot policies are automatically inherited by vHBAs, when in fact they must be explicitly linked via the service profile's boot policy configuration.

Practice this question →
7
Multi-Selecthard

A UCS domain is configured with two fabric interconnects in end-host mode. The engineer needs to ensure that traffic from a specific VLAN is load-balanced across both uplinks to the upstream network. Which THREE of the following are valid methods to achieve load balancing on the uplink ports?

Select 3 answers
A.VLAN load balancing using the pin-groups
B.Configure SPAN on the uplink ports
C.Fabric port channel with LACP
D.MAC pinning to assign source-destination pairs to uplinks
E.vPC-host mode on the fabric interconnects
AnswersC, D, E

A fabric port channel aggregates multiple uplinks into a single logical link, load balancing traffic.

Why this answer

Option C is correct because a Fabric Port Channel with LACP allows multiple uplink ports to be aggregated into a single logical link, providing load balancing across the physical links based on a hash algorithm (e.g., source/destination MAC or IP). This is a standard method for distributing traffic from a specific VLAN across both uplinks to the upstream network in a UCS domain configured with two fabric interconnects in end-host mode.

Exam trap

Cisco often tests the distinction between Ethernet load-balancing methods (like Fabric Port Channel with LACP and MAC pinning) and Fibre Channel-specific features (like pin-groups), leading candidates to mistakenly select pin-groups for Ethernet traffic.

Practice this question →
8
MCQeasy

A network engineer needs to create a consistent QoS policy for all servers in a UCS service profile template. Which policy must be attached to the template to ensure uniform traffic management?

A.QoS Policy
B.Network Control Policy
C.LAN Connectivity Policy
D.Flow Control Policy
AnswerA

QoS policy defines traffic prioritization and is attached to vNICs.

Why this answer

A QoS Policy is the correct attachment because it defines traffic classification, marking, and queuing behavior at the interface level within a UCS service profile template. By applying a QoS Policy, the engineer ensures uniform traffic management across all servers by controlling bandwidth allocation, priority, and drop preferences consistently. This policy directly maps to the system class definitions in UCS Manager, enabling per-interface QoS settings that are inherited by all service profiles using the template.

Exam trap

Cisco often tests the distinction between QoS Policy (which controls traffic prioritization and queuing) and Flow Control Policy (which only manages Ethernet pause frames), leading candidates to confuse link-level flow control with end-to-end quality of service.

How to eliminate wrong answers

Option B is wrong because a Network Control Policy manages MAC address mode, VLAN port configuration, and CDP/LLDP settings, not traffic prioritization or bandwidth management. Option C is wrong because a LAN Connectivity Policy defines the number and order of vNICs and their failover relationships, but does not include QoS parameters like classification or scheduling. Option D is wrong because a Flow Control Policy controls Ethernet pause frames (IEEE 802.3x) for link-level congestion, not the classification, marking, or queuing required for consistent QoS across servers.

Practice this question →
9
MCQmedium

A UCS C-Series rack server with a boot from SAN policy fails to discover the LUN during POST. The HBA is correctly zoned with the storage array. Which step should be taken to troubleshoot the issue?

A.Verify VSAN membership on the fabric interconnect
B.Update the server firmware to the latest version
C.Review the SAN boot target configuration in Cisco IMC
D.Check the service profile association in UCS Manager
AnswerC

CIMC stores the SAN boot settings for C-Series servers

Why this answer

Option C is correct because when a UCS C-Series rack server with a boot-from-SAN policy fails to discover the LUN during POST, the most direct troubleshooting step is to review the SAN boot target configuration in Cisco IMC. The HBA is already correctly zoned, so the issue likely lies in the boot target parameters (e.g., WWPN, LUN ID, or target name) configured in the IMC's SAN boot settings, which the HBA uses during the BIOS-level boot process. Verifying these settings ensures the HBA can properly address and log into the storage target.

Exam trap

Cisco often tests the distinction between UCS B-Series (managed via UCS Manager with service profiles) and C-Series (standalone with Cisco IMC) to trap candidates who apply B-Series troubleshooting steps to a C-Series scenario.

How to eliminate wrong answers

Option A is wrong because VSAN membership on the fabric interconnect applies to UCS B-Series blade servers and Fabric Interconnects, not to C-Series rack servers, which use Cisco IMC for direct SAN boot configuration. Option B is wrong because updating server firmware is a generic troubleshooting step that does not address the specific boot-from-SAN discovery failure; the issue is configuration-related, not a firmware bug. Option D is wrong because service profile association in UCS Manager is relevant for UCS B-Series blades managed by UCS Manager, not for standalone C-Series rack servers, which are managed independently via Cisco IMC.

Practice this question →
10
MCQeasy

An engineer is troubleshooting a Cisco UCS B-Series blade that fails to boot. The service profile is associated and the boot policy is set to 'SAN Boot'. The storage administrator confirms the LUN is properly mapped to the WWPN. Which check should the engineer perform first?

A.Verify that the UCS Fabric Interconnect is connected to the SAN switches
B.Reboot the chassis to reinitialize the IOM
C.Check that the vHBA has a dynamic WWPN assigned
D.Ensure the local disk is set as primary boot device
AnswerA

Without fabric connectivity, the server cannot reach the storage.

Why this answer

Since the service profile is associated, the boot policy is set to SAN Boot, and the LUN is properly mapped to the WWPN, the most likely cause is a physical or Layer 2 connectivity issue between the UCS Fabric Interconnect and the SAN switches. Without this link, the fabric interconnect cannot forward FCP frames to the storage array, preventing the blade from discovering the boot LUN. Verifying this connection is the logical first step before investigating other configuration or zoning issues.

Exam trap

Cisco often tests the misconception that a properly mapped LUN and associated service profile guarantee SAN boot success, leading candidates to overlook the physical or Layer 2 connectivity between the Fabric Interconnect and the SAN switches.

How to eliminate wrong answers

Option B is wrong because rebooting the chassis or reinitializing the IOM would disrupt all blades and is unnecessary when the issue is isolated to a single blade failing to boot from SAN; it also does not address the connectivity between the Fabric Interconnect and SAN switches. Option C is wrong because a dynamic WWPN is the default and recommended assignment for vHBAs in UCS, and changing it would not resolve a missing SAN path; the storage administrator has already confirmed the LUN is mapped to the correct WWPN. Option D is wrong because the boot policy is explicitly set to 'SAN Boot', meaning the local disk should not be the primary boot device; forcing local disk boot would bypass the intended SAN boot process and is not a troubleshooting step for SAN boot failures.

Practice this question →
11
Multi-Selecteasy

Which TWO UCS components are part of the unified fabric architecture?

Select 2 answers
A.Fabric Interconnect
B.Storage Array
C.I/O Module (IOM)
D.Control Plane
E.Blade Server
AnswersA, C

Central switching component

Why this answer

The Fabric Interconnect (A) is the core switching component in Cisco UCS, providing both network and storage connectivity over a unified fabric, typically using Fibre Channel over Ethernet (FCoE) to consolidate LAN and SAN traffic. The I/O Module (IOM) (C) connects blade servers to the Fabric Interconnects, extending the unified fabric by aggregating traffic from the chassis and forwarding it to the Fabric Interconnects, thereby eliminating the need for separate network and storage switches.

Exam trap

Cisco often tests the distinction between components that are part of the unified fabric (Fabric Interconnect and IOM) versus components that connect to or use the fabric (storage arrays, blade servers), leading candidates to mistakenly include endpoints or external devices as fabric components.

Practice this question →
12
Multi-Selecthard

Which TWO troubleshooting steps should be taken when a UCS blade server fails to discover during the initial discovery process?

Select 2 answers
A.Verify the physical cabling between the IOM and fabric interconnect
B.Immediately replace the blade server
C.Power cycle the chassis
D.Reset the fabric interconnect to factory defaults
E.Check firmware compatibility between FI and chassis
AnswersA, E

Physical connectivity is essential

Why this answer

Option A is correct because the initial discovery process relies on the IOM (Fabric Interconnect) establishing a link to the blade server through the chassis midplane. If the physical cabling between the IOM and the fabric interconnect is faulty, loose, or using incorrect transceivers, the discovery will fail. Verifying this cabling is a fundamental first step in troubleshooting discovery failures.

Exam trap

Cisco often tests the misconception that a blade server discovery failure is always a hardware fault, leading candidates to choose 'replace the blade' or 'power cycle the chassis' instead of checking the physical and logical connectivity between the IOM and the FI.

Practice this question →
13
Multi-Selectmedium

An engineer is troubleshooting a UCS B-Series blade that fails to boot from SAN. Which TWO actions should be verified first? (Choose TWO.)

Select 2 answers
A.Verify that the vHBA WWPN is correctly zoned on the SAN switches.
B.Confirm the boot policy includes the SAN target LUN.
C.Check the MAC address assigned to the vNIC.
D.Ensure the QoS policy for FC traffic is set to Platinum.
E.Verify the server's boot order lists local disk first.
AnswersA, B

Common issue: incorrect zoning.

Why this answer

Option A is correct because the vHBA WWPN must be properly zoned on the SAN switches to allow the blade to discover and connect to the storage target. Without correct zoning, the Fibre Channel initiator cannot communicate with the target, preventing SAN boot. This is a fundamental prerequisite for any Fibre Channel-based boot.

Exam trap

Cisco often tests the distinction between SAN boot prerequisites (WWPN zoning and boot policy LUN) versus performance or Ethernet-related settings, leading candidates to mistakenly select MAC address or QoS options.

Practice this question →
14
MCQhard

In a Cisco HyperFlex cluster, the management plane uses vCenter, but the data plane uses which protocol to replicate data across nodes?

A.Fibre Channel
B.HX Data Platform
C.NFS
D.iSCSI
AnswerB

HyperFlex uses its own HX Data Platform protocol for data replication and distribution.

Why this answer

In a Cisco HyperFlex cluster, the data plane replication across nodes is handled by the HX Data Platform, which is a distributed, log-structured file system that synchronously replicates data at the hypervisor level. This platform manages all I/O operations and ensures data consistency across the cluster without relying on external storage protocols like Fibre Channel or iSCSI.

Exam trap

Cisco often tests the distinction between the management plane (vCenter) and the data plane (HX Data Platform), and the trap here is that candidates may confuse the data replication protocol with common storage protocols like NFS or iSCSI, which are used for external storage access but not for HyperFlex's internal replication.

How to eliminate wrong answers

Option A is wrong because Fibre Channel is a block-level storage protocol used in SAN environments, not for HyperFlex's distributed data replication which uses the HX Data Platform's own replication mechanism. Option C is wrong because NFS is a network file system protocol for accessing files over a network, not a replication protocol for HyperFlex's data plane. Option D is wrong because iSCSI is a block-level storage protocol that encapsulates SCSI commands over IP networks, but HyperFlex does not use iSCSI for its internal data replication; it relies on the HX Data Platform's proprietary replication.

Practice this question →
15
MCQeasy

A UCS domain has two Fabric Interconnects in end-host mode. Which statement about server-side traffic is true?

A.Fabric Interconnects run IEEE 802.1D STP on the server-facing ports.
B.The Fabric Interconnect learns server MAC addresses on the server-facing ports.
C.The Fabric Interconnect performs VLAN-based load balancing to the upstream network.
D.Each Fabric Interconnect independently forwards frames to the upstream switches using the same uplink.
AnswerB

Yes, it learns host MAC addresses.

Why this answer

In end-host mode, the Fabric Interconnect (FI) acts as a Layer-2 forwarding device that learns server MAC addresses on the server-facing ports to build its forwarding table. This is required because the FI does not run Spanning Tree Protocol (STP) on those ports; instead, it relies on MAC learning to forward traffic correctly between servers and the upstream network.

Exam trap

The trap here is that candidates confuse end-host mode with switching mode, assuming STP is required on server ports, when in fact end-host mode disables STP and relies on MAC learning to maintain a loop-free topology.

How to eliminate wrong answers

Option A is wrong because Fabric Interconnects in end-host mode do not run IEEE 802.1D STP on server-facing ports; they use a pinning or forwarding mode that disables STP to avoid blocking server links. Option C is wrong because VLAN-based load balancing to the upstream network is not performed by the FI in end-host mode; instead, uplink load balancing is typically based on source/destination MAC or IP hashing, not VLAN. Option D is wrong because each Fabric Interconnect does not independently forward frames using the same uplink; in end-host mode, each FI uses its own dedicated uplinks and does not share forwarding paths with the other FI for the same frame.

Practice this question →
16
MCQeasy

A data center engineer is planning a Cisco UCS deployment for a virtualized environment. The requirement is to maximize performance for virtual machine traffic while minimizing latency. Which feature should be enabled on the UCS Manager to offload packet processing from the host CPU?

A.Data Center Ethernet (DCE) priority flow control
B.vNIC failover policy
C.Hardware VLAN tagging and checksum offload
D.Fibre Channel over Ethernet (FCoE) offload
AnswerC

These offloads reduce CPU utilization and improve throughput.

Why this answer

Hardware VLAN tagging and checksum offload offloads packet processing tasks (VLAN insertion/stripping and checksum calculation) from the host CPU to the Cisco UCS virtual interface card (VIC) adapter. This reduces CPU overhead and minimizes latency for virtual machine traffic, directly meeting the requirement to maximize performance in a virtualized environment.

Exam trap

The trap here is that candidates confuse 'offload' with any feature that improves performance, but only hardware VLAN tagging and checksum offload directly offloads packet processing from the host CPU, while options like FCoE offload are storage-specific and not applicable to general VM traffic.

How to eliminate wrong answers

Option A is wrong because Data Center Ethernet (DCE) priority flow control (PFC) is a Layer 2 flow control mechanism that prevents packet loss due to congestion, but it does not offload packet processing from the host CPU. Option B is wrong because vNIC failover policy provides redundancy by switching traffic to a standby vNIC on link failure, but it does not reduce CPU overhead or latency for packet processing. Option D is wrong because Fibre Channel over Ethernet (FCoE) offload is specific to storage traffic (SAN) and does not address general VM packet processing offload; it offloads FCoE encapsulation, not general network packet processing.

Practice this question →
17
MCQmedium

A Cisco UCS Manager administrator notices that a newly provisioned service profile is showing 'Config Error' for the vNIC. The vNIC is configured to use a dynamic MAC address from a pool that has no free addresses. What is the correct remediation?

A.Add more MAC addresses to the MAC pool used by the vNIC
B.Upgrade the firmware on the Fabric Interconnect
C.Change the vNIC to use a static MAC address
D.Reassociate the service profile to a different blade
AnswerA

Extending the pool provides available addresses for assignment.

Why this answer

The 'Config Error' for the vNIC indicates that the dynamic MAC address assignment failed because the MAC pool is exhausted. Adding more MAC addresses to the pool resolves the issue by providing available addresses for the vNIC to consume, allowing the service profile to deploy successfully.

Exam trap

Cisco often tests the misconception that a 'Config Error' on a vNIC is due to hardware or association issues, leading candidates to choose reassociation or firmware upgrades, when the actual cause is a resource pool exhaustion that requires pool expansion.

How to eliminate wrong answers

Option B is wrong because upgrading the Fabric Interconnect firmware does not address MAC pool exhaustion; it is unrelated to address allocation. Option C is wrong because changing to a static MAC address bypasses the pool but is not the correct remediation for a pool exhaustion issue—it is a workaround, not a fix. Option D is wrong because reassociating the service profile to a different blade does not resolve the underlying MAC pool depletion; the same error would occur on any blade if the pool has no free addresses.

Practice this question →
18
MCQhard

A CCNP engineer is troubleshooting a UCS environment where a server is stuck in 'Discovery: In Progress' state. The chassis has been power-cycled, but the issue persists. FEX fabric port is configured correctly. What is the most likely cause?

A.Incorrect IP address on the Fabric Interconnect management interface.
B.Firmware version mismatch between the server's CIMC and the Fabric Interconnect.
C.The chassis is not connected to the FI via a valid fabric cable.
D.The server's service profile is not associated.
AnswerB

CIMC firmware must match the FI's supported version for discovery to complete.

Why this answer

When a server is stuck in 'Discovery: In Progress' state and the chassis has been power-cycled with correct FEX fabric port configuration, the most likely cause is a firmware version mismatch between the server's Cisco Integrated Management Controller (CIMC) and the Fabric Interconnect (FI). During discovery, the FI attempts to inventory and manage the server via CIMC; if the firmware versions are incompatible, the discovery process cannot complete, leaving the server in a perpetual 'In Progress' state.

Exam trap

Cisco often tests the misconception that a server stuck in discovery is due to a physical connectivity issue (Option C) or a service profile association problem (Option D), when in fact the root cause is a firmware version mismatch that prevents the FI from completing the inventory handshake.

How to eliminate wrong answers

Option A is wrong because the Fabric Interconnect management interface IP address is used for out-of-band management access (e.g., SSH, GUI) and does not affect server discovery, which occurs over the fabric data path. Option C is wrong because the chassis is already connected to the FI via a valid fabric cable (as stated in the question), and power-cycling the chassis would have resolved any transient connectivity issues. Option D is wrong because a service profile association is required for the server to be operational, but the server must first complete discovery before it can be associated; being stuck in discovery prevents association, not the other way around.

Practice this question →
19
MCQeasy

Which feature in UCS Manager allows centralized management of firmware policies across multiple chassis without creating a separate policy for each chassis?

A.Maintenance Policy
B.Firmware Policy
C.Host Firmware Package
D.Adapter Policy
AnswerB

Can be shared across many service profiles.

Why this answer

B is correct because a Firmware Policy in UCS Manager allows you to define a single firmware version and package that can be applied to multiple chassis or service profiles. This centralized approach eliminates the need to create a separate firmware policy for each chassis, as the policy is simply associated with the desired chassis or service profile templates.

Exam trap

Cisco often tests the distinction between a Firmware Policy (which defines the firmware version) and a Host Firmware Package (which is applied to a server within a service profile), causing candidates to confuse the scope of each object.

How to eliminate wrong answers

Option A is wrong because a Maintenance Policy controls the reboot behavior (e.g., immediate or user-acknowledged) during firmware updates, not the firmware version or package selection. Option C is wrong because a Host Firmware Package is used to specify the firmware bundle for a server (compute node) within a service profile, not for centralized management across multiple chassis. Option D is wrong because an Adapter Policy configures the properties of the virtual interface card (VIC) adapter, such as failover and offload settings, and has no role in firmware version management.

Practice this question →
20
MCQeasy

A UCS administrator needs to deploy 20 identical servers with the same firmware, BIOS, and boot order. Which approach is the most efficient?

A.Use a UUID suffix pool to auto-generate identities.
B.Use a Cisco UCS Central 'Gold' template to deploy the servers.
C.Create a service profile template and then generate service profiles from it.
D.Create a service profile for each server manually.
AnswerC

Templates allow centralized management and quick deployment.

Why this answer

Creating a service profile template and then generating service profiles from it is the most efficient approach because it allows you to define the firmware, BIOS, and boot order once in a reusable template, then automatically create multiple service profiles with unique identities (e.g., UUID, MAC, WWN) for each of the 20 identical servers. This leverages Cisco UCS Manager's built-in template-to-instance workflow, ensuring consistency and reducing manual effort.

Exam trap

Cisco often tests the distinction between a service profile template (used to generate multiple instances) and a UUID suffix pool (a component that only handles identity generation), leading candidates to mistakenly choose the pool as a complete deployment solution.

How to eliminate wrong answers

Option A is wrong because a UUID suffix pool auto-generates only the UUID portion of a service profile's identity, but it does not address the need to deploy firmware, BIOS, and boot order settings across multiple servers; it is a component within a service profile, not a deployment method. Option B is wrong because Cisco UCS Central is a multi-domain management tool, not a mechanism for deploying individual server configurations within a single UCS domain; a 'Gold' template in UCS Central is used for policy-based configuration across domains, not for generating service profiles for local server deployment. Option D is wrong because creating a service profile for each server manually is inefficient and error-prone for 20 identical servers, as it requires repetitive configuration of the same firmware, BIOS, and boot order settings, defeating the purpose of automation.

Practice this question →
21
Multi-Selecthard

An engineer is configuring a UCS server for VMware ESXi. The service profile must support NPIV for virtual machine SAN connectivity. Which two conditions must be met? (Choose two.)

Select 2 answers
A.The WWPN must be unique per virtual machine
B.The vHBA must be associated with a VSAN
C.The vHBA must be set to 'Fabric: A' only
D.The vHBA must be set to 'Fabric: dual' mode
E.The vHBA must be created with a fabric failover policy
AnswersA, B

NPIV assigns unique WWPNs to each VM for SAN access.

Why this answer

Option A is correct because NPIV (N_Port ID Virtualization) requires each virtual machine to have a unique World Wide Port Name (WWPN) so that the SAN fabric can distinguish and manage each VM's storage traffic independently. This allows multiple virtual machines to share a single physical HBA while each appears as a separate initiator to the SAN.

Exam trap

Cisco often tests the misconception that NPIV requires a fabric failover policy or dual-fabric mode, when in fact NPIV only requires unique WWPNs and proper VSAN association, with failover handled at the fabric level or by the hypervisor.

Practice this question →
22
MCQhard

Refer to the exhibit. An engineer applies this QoS policy to a Cisco Nexus 9000 switch in a data center. After applying the policy, storage traffic (iSCSI) is experiencing high latency and occasional drops. The engineer verifies that the iSCSI traffic is not matching the 'BulkData' class. What is the most likely cause of the issue?

A.The policy-map does not specify a priority queue for latency-sensitive traffic.
B.The policy-map is applied at the system level, but iSCSI traffic is not classified under any class-map.
C.The bandwidth percent for class-default is too low, causing iSCSI to be starved.
D.The class-map 'BulkData' does not match the correct traffic because the match statement uses qos-group instead of dscp.
AnswerA

iSCSI requires low latency; without a priority queue, it competes with other traffic.

Why this answer

The correct answer is A because iSCSI is a latency-sensitive storage protocol that requires a strict priority queue to ensure low latency and minimal jitter. Without a priority queue configured in the policy-map, iSCSI traffic competes with other traffic classes on a best-effort basis, leading to high latency and drops even if it is not matching the 'BulkData' class.

Exam trap

Cisco often tests the misconception that simply classifying traffic into a class-map is sufficient, but the trap here is that without a priority queue, latency-sensitive traffic like iSCSI will still suffer from high latency and drops even if correctly classified.

How to eliminate wrong answers

Option B is wrong because the policy-map is applied at the system level, but iSCSI traffic not being classified under any class-map would cause it to fall into class-default, not directly cause high latency if bandwidth is properly allocated. Option C is wrong because the bandwidth percent for class-default being too low would affect all default traffic equally, but the issue is specifically with iSCSI latency and drops, not starvation. Option D is wrong because the class-map 'BulkData' uses a match statement that is irrelevant to iSCSI traffic; the issue is not about incorrect matching but the lack of a priority queue for latency-sensitive traffic.

Practice this question →
23
MCQmedium

You are a data center engineer at a financial company. The production environment uses UCS B-Series blades with fabric interconnects in a clustered configuration. One of the blades (blade 3) is running a critical trading application. The server is associated with a service profile that boots from SAN using a single HBA path. During a routine network upgrade, the storage administrator reports that LUN 0 on the primary storage array is no longer accessible from blade 3. The server is still powered on, but the application is unresponsive. You check UCS Manager and see that the vHBA for blade 3 is in an 'Unavailable' state. The fabric interconnect ports show no errors. The storage array logs show that the target port is active. Which action should you take to restore connectivity with minimal downtime?

A.Change the boot policy to use a secondary LUN on the same array
B.Unassign and reassign the vHBA's WWPN from the pool in the service profile
C.Reset the fabric interconnect to restore cluster state
D.Reboot the server to force re-initialization of the HBA
AnswerB

This forces the fabric to re-establish zoning and access

Why this answer

The vHBA being in an 'Unavailable' state while the fabric interconnect ports and storage target are healthy indicates a WWPN (World Wide Port Name) conflict or corruption at the fabric level. Unassigning and reassigning the vHBA's WWPN from the pool forces UCS Manager to generate a new WWPN and re-login to the SAN fabric, re-establishing the Fibre Channel session without requiring a server reboot or service profile re-association, minimizing downtime for the critical trading application.

Exam trap

Cisco often tests the misconception that a vHBA 'Unavailable' state requires a server reboot or fabric interconnect reset, when in fact the solution is to reassign the WWPN from the pool to resolve fabric login issues without disrupting the server's power state.

How to eliminate wrong answers

Option A is wrong because changing the boot policy to use a secondary LUN does not resolve the vHBA's 'Unavailable' state; the issue is at the HBA fabric login level, not the LUN path, and the application is already unresponsive due to lost connectivity. Option C is wrong because resetting the fabric interconnect would disrupt all blades and storage traffic in the cluster, causing widespread downtime, and the logs show no port errors or cluster state issues, so this is an unnecessary and destructive action. Option D is wrong because rebooting the server would force a re-initialization of the HBA, but it would still use the same problematic WWPN, likely resulting in the same 'Unavailable' state, and it would cause application downtime that can be avoided with a WWPN reassignment.

Practice this question →
24
Multi-Selecthard

Which TWO are valid methods to configure a Cisco UCS service profile for stateless computing? (Choose two.)

Select 2 answers
A.Create a service profile from a template
B.Use boot from SAN to store OS images
C.Assign persistent WWPNs to vHBAs
D.Configure local storage on the blade
E.Update the service profile template and re-apply to existing profiles
AnswersA, E

A derived template inherits settings that can be updated centrally.

Why this answer

Option A is correct because creating a service profile from a template is a core method for stateless computing in Cisco UCS. Stateless computing abstracts hardware identity (e.g., WWPNs, MAC addresses, UUIDs) from physical blades, allowing a service profile to be applied to any compatible blade without reconfiguration. Templates enable rapid, consistent deployment of these stateless profiles across multiple servers.

Exam trap

Cisco often tests the distinction between a method to configure a service profile (e.g., using a template) versus a specific attribute or feature within a profile (e.g., persistent WWPNs or boot from SAN), leading candidates to confuse configuration methods with profile properties.

Practice this question →
25
MCQhard

Refer to the exhibit. An engineer is creating a service profile template in Cisco UCSM. What is the effect of setting the vnet to 'VM_Network' for vNIC_A?

A.The VM_Network VLAN is a pre-defined FCoE VLAN for storage traffic.
B.The vNIC_A will be placed in VLAN 1 (default) if VM_Network does not exist.
C.The VM_Network VLAN will be created automatically as a standard VLAN.
D.The VM_Network VLAN must be previously defined in the global VLAN database.
AnswerD

UCS requires VLANs to be defined globally before they can be assigned to vNICs.

Why this answer

Option A is correct because UCS requires that any VLAN referenced in a vNIC must already exist in the global VLAN database. Option B is false because VLANs are not created automatically; they must be defined manually beforehand. Option C is false because if the VLAN does not exist, the vNIC will not come up.

Option D is false because VM_Network is a typical naming convention for data VLANs, not FCoE.

Practice this question →
26
MCQeasy

A network engineer is designing a Cisco HyperFlex cluster for a virtualized environment. The cluster will run VDI workloads. Which storage policy should be selected to ensure that all VMs have the highest possible performance while maintaining data redundancy?

A.Triple replication with RAID 5 parity
B.Erasure coding with deduplication
C.Dual replication with deduplication and compression
D.No replication with compression
AnswerC

Dual replication provides redundancy, and deduplication/compression reduce capacity, while caching maintains performance.

Why this answer

For VDI workloads in a Cisco HyperFlex cluster, the storage policy must balance performance and data redundancy. Dual replication with deduplication and compression provides the highest performance by using two copies of data (mirroring) for redundancy, while deduplication and compression reduce storage overhead without the write penalty of parity-based schemes. This avoids the performance degradation of RAID 5 parity or erasure coding, which are unsuitable for latency-sensitive VDI.

Exam trap

Cisco often tests the misconception that erasure coding or RAID parity is always better for space efficiency, but in VDI scenarios, the write penalty of these methods makes dual replication the correct choice for performance-sensitive workloads.

How to eliminate wrong answers

Option A is wrong because triple replication with RAID 5 parity introduces significant write overhead and latency due to parity calculations, which is detrimental to VDI performance. Option B is wrong because erasure coding, while space-efficient, imposes a high computational and I/O penalty on writes, making it unsuitable for the random write-heavy nature of VDI workloads. Option D is wrong because no replication provides zero data redundancy, violating the requirement for data protection in a production VDI environment.

Practice this question →
27
MCQmedium

An engineer needs to deploy a new UCS C-Series standalone server in a remote branch without local IT staff. Which technology allows remote firmware upgrade and hardware monitoring without requiring a dedicated management IP?

A.Cisco Integrated Management Controller (CIMC) GUI
B.UCS Manager
C.Data Center Network Manager (DCNM)
D.Cisco Intersight
AnswerD

Intersight can manage C-Series servers remotely via device connector.

Why this answer

Cisco Intersight is a cloud-based management platform that provides out-of-band management for UCS C-Series standalone servers without requiring a dedicated management IP address. It uses a device connector embedded in the CIMC to establish a secure connection to the Intersight cloud, enabling remote firmware upgrades, hardware monitoring, and lifecycle management over the internet. This eliminates the need for a separate management network or local IT staff at the remote branch.

Exam trap

Cisco often tests the distinction between traditional out-of-band management (CIMC GUI requiring a dedicated IP) and cloud-based management (Intersight using a device connector without a dedicated IP), leading candidates to incorrectly choose CIMC GUI for remote management scenarios.

How to eliminate wrong answers

Option A is wrong because the CIMC GUI requires a dedicated management IP address to be accessed locally or remotely, which contradicts the requirement of not needing a dedicated management IP. Option B is wrong because UCS Manager is designed for managing UCS B-Series blade servers and fabric interconnects in a centralized domain, not for standalone C-Series servers, and it also requires a dedicated management IP. Option C is wrong because Data Center Network Manager (DCNM) is a network management tool for Cisco Nexus switches and ACI fabrics, not for UCS server management or firmware upgrades.

Practice this question →
28
Multi-Selecteasy

A UCS administrator is configuring a service profile for a VMware ESXi host. Which TWO of the following configuration items must be included to enable Fibre Channel SAN boot?

Select 2 answers
A.QoS policy for vHBA
B.WWPN pool for vHBA
C.vNIC with MAC pool
D.FCoE VLAN configuration
E.SAN boot policy with target WWPN
AnswersB, E

A WWPN pool provides the WWPNs for the vHBA that connects to the SAN.

Why this answer

For Fibre Channel SAN boot on a UCS-managed VMware ESXi host, the service profile must include a WWPN pool for the vHBA (Option B) to assign unique World Wide Port Names, and a SAN boot policy specifying the target WWPN (Option E) to define the storage target from which the host boots. These two elements are essential because the vHBA requires a WWPN for fabric login, and the boot policy directs the host to the correct LUN on the SAN.

Exam trap

Cisco often tests the distinction between Fibre Channel SAN boot and FCoE SAN boot, leading candidates to incorrectly select FCoE VLAN configuration (Option D) when the question explicitly states 'Fibre Channel SAN boot' without mentioning FCoE.

Practice this question →
29
Multi-Selectmedium

A data center engineer is configuring VLANs in a Cisco UCS domain. Which TWO statements are true regarding VLAN configuration?

Select 2 answers
A.VLANs can be created directly within a service profile without prior global definition.
B.VLANs can be created only through the CLI of UCS Manager.
C.Service profiles can override the VLAN ID of a global VLAN definition.
D.Each vNIC must have a native VLAN specified for untagged traffic on that vNIC.
E.VLANs must be defined in the global VLAN database before they can be used in a service profile.
AnswersD, E

A native VLAN is required for untagged frames on a vNIC.

Why this answer

Option A is correct because VLANs must be defined in the global VLAN database before they can be used in service profiles. Option D is correct because each vNIC must have a native VLAN specified for untagged traffic. Option B is false because VLANs cannot be created directly in service profiles.

Option C is false because service profiles use VLANs from the global pool and cannot override the VLAN ID. Option E is false because VLANs can be created via both CLI and GUI.

Practice this question →
30
MCQhard

Your company integrates UCS B-Series blades with VMware vSphere using UCS Manager and vCenter. You have configured a UCS service profile with a boot policy that boots from SAN. The virtual infrastructure administrator reports that a new ESXi host (blade 6) fails to meet host profile compliance for the 'Boot Device' policy. The host profile requires the boot LUN to be set to 'VMware LUN' but the UCS boot policy uses a generic 'SAN Target' setting. The ESXi host boots and runs, but compliance checks fail. You cannot modify the host profile because it is managed by a separate team. Which action should you take to resolve the compliance failure while maintaining boot functionality?

A.Create a new vCenter cluster with a different host profile
B.Use a local disk boot policy and install ESXi locally
C.Request the host profile to be updated to accept generic SAN targets
D.Change the UCS boot policy to use the 'VMware LUN' target type and ensure the LUN is presented correctly
AnswerD

Aligns with host profile requirement

Why this answer

Option D is correct because the host profile compliance failure is caused by the UCS boot policy using a generic 'SAN Target' type instead of the 'VMware LUN' target type. By changing the boot policy to 'VMware LUN' and ensuring the correct LUN is presented, the ESXi host will boot from the same LUN but now the boot device name will match what the host profile expects, resolving the compliance check without affecting boot functionality.

Exam trap

Cisco often tests the distinction between 'functional boot' and 'compliance check'—candidates may assume that because the host boots fine, no change is needed, but the question explicitly requires resolving the compliance failure while maintaining boot functionality, meaning the boot policy must be adjusted to match the host profile's expected target type.

How to eliminate wrong answers

Option A is wrong because creating a new vCenter cluster with a different host profile does not address the root cause—the mismatch between the UCS boot policy and the existing host profile; it also introduces unnecessary administrative overhead and does not fix the compliance issue for the current host. Option B is wrong because using a local disk boot policy would require a complete reinstallation of ESXi and would change the boot method entirely, which is not required and would break the existing SAN boot configuration; the host profile still expects a specific boot LUN type, not local storage. Option C is wrong because the host profile is managed by a separate team and cannot be modified per the question constraints; requesting a change may be a valid long-term process but is not an immediate action the engineer can take to resolve the compliance failure.

Practice this question →
31
MCQmedium

An organization is deploying Cisco UCS and needs to ensure that server personality is maintained even after a new server is added to the chassis. Which policy should be configured to achieve this?

A.UUID Suffix Pool
B.Maintenance Policy
C.Boot Policy
D.Server Pool Policy
AnswerD

Server pool allows assigning a specific server to a profile, maintaining identity.

Why this answer

The Server Pool Policy is correct because it defines a logical grouping of servers that can be dynamically assigned to service profiles. When a new server is added to the chassis and matches the pool criteria, the policy ensures that the server automatically inherits the correct personality (e.g., UUID, WWN, MAC addresses) from the associated service profile template, maintaining consistency without manual intervention.

Exam trap

Cisco often tests the distinction between policies that manage identity (UUID Suffix Pool) versus policies that manage assignment (Server Pool Policy), leading candidates to confuse the UUID pool as the mechanism for maintaining personality when it is actually the server pool that drives the assignment and inheritance.

How to eliminate wrong answers

Option A is wrong because a UUID Suffix Pool only provides unique UUIDs for server identity but does not control server assignment or personality retention when a new server is added. Option B is wrong because a Maintenance Policy defines how the server handles firmware upgrades or reboots (e.g., user acknowledgment or immediate reboot), not server personality persistence. Option C is wrong because a Boot Policy specifies the boot order and boot parameters (e.g., SAN, local disk, network) but does not manage server assignment or personality inheritance.

Practice this question →
32
MCQeasy

A Cisco UCS C-Series rack server requires remote management with KVM and virtual media. Which feature must be enabled?

A.vMedia
B.CIMC
C.BIOS
D.SOL
AnswerB

CIMC is the base management interface that offers KVM and virtual media.

Why this answer

The Cisco Integrated Management Controller (CIMC) is the dedicated management interface on UCS C-Series rack servers that provides out-of-band remote management capabilities, including KVM console access and virtual media (vMedia) for mounting ISO images. Without CIMC enabled, these remote management features are unavailable, as they rely on its embedded web GUI, CLI, or API.

Exam trap

Cisco often tests the distinction between a feature (vMedia) and the platform that provides it (CIMC), leading candidates to select vMedia as the answer when the question asks which feature must be enabled to support both KVM and virtual media.

How to eliminate wrong answers

Option A is wrong because vMedia is a feature of CIMC that enables virtual media mounting (e.g., ISO, floppy), not a standalone management feature that must be enabled separately. Option C is wrong because the BIOS handles hardware initialization and boot settings, not remote KVM or virtual media services. Option D is wrong because SOL (Serial Over LAN) provides serial console redirection via IPMI, not KVM video or virtual media functionality.

Practice this question →
33
MCQhard

A UCS Manager administrator is deploying a service profile for a boot-from-SAN environment. The SAN switch is configured with NPV mode. The administrator notices that the WWPN of the vHBA in the service profile is not being recognized by the SAN switch. What is the most likely cause?

A.The WWPN pool has been exhausted and the server cannot obtain a new WWPN
B.The vHBA is not bound to a SAN pin-group
C.The vHBA speed is set to auto-negotiation but the SAN switch is set to a fixed speed
D.The upstream SAN switch has NPIV disabled
AnswerD

In NPV mode, the SAN switch requires NPIV on the upstream switch to register the initiator WWPNs.

Why this answer

In a boot-from-SAN environment with NPV mode on the SAN switch, the upstream switch must have NPIV (N_Port ID Virtualization) enabled to allow multiple FCIDs to be assigned to a single physical link. Without NPIV, the upstream switch rejects the WWPN of the vHBA because it cannot support the virtualized N_Port IDs required for the service profile's vHBA to log in. This is the most likely cause of the WWPN not being recognized.

Exam trap

Cisco often tests the distinction between NPV and NPIV, where candidates mistakenly think NPV alone enables virtualized logins, but NPIV must be explicitly enabled on the upstream switch for vHBA WWPNs to be recognized.

How to eliminate wrong answers

Option A is wrong because a WWPN pool exhaustion would prevent a new WWPN from being assigned, but the administrator notes the WWPN is not being recognized by the SAN switch, not that it is unavailable. Option B is wrong because pin-groups are used for fabric failover or path selection in UCS, not for WWPN recognition; a vHBA does not need to be bound to a pin-group to be recognized by the SAN switch. Option C is wrong because speed mismatch between the vHBA and SAN switch would cause link issues or performance degradation, not a failure of the SAN switch to recognize the WWPN; WWPN recognition is independent of negotiated speed.

Practice this question →
34
MCQhard

An engineer notices that a UCS server with a service profile using a QoS policy for FC traffic experiences excessive latency during heavy workloads. The Fibre Channel fabric is configured for lossless operation. Which design issue is most likely causing the latency?

A.The MTU on the Ethernet uplink from the FI is set to 1500 bytes.
B.The QoS policy for FC traffic does not allocate enough buffer for the no-drop class.
C.Fibre Channel buffer-to-buffer credit recovery is disabled on the upstream switch.
D.The vHBA is configured for 16 Gbps but the upstream switch port is 8 Gbps.
AnswerB

Insufficient buffer allocation in the no-drop class can cause pause frames and increased latency.

Why this answer

The excessive latency during heavy workloads in a lossless Fibre Channel fabric is most likely due to insufficient buffer allocation for the no-drop class in the QoS policy. In UCS, the no-drop class (typically class-fcoe) must have adequate buffer space to prevent frame drops that trigger retransmissions and latency. Without enough buffer, the switch cannot absorb bursts, leading to congestion and increased latency even though the fabric is lossless.

Exam trap

Cisco often tests the misconception that latency in a lossless fabric is caused by external factors like MTU or speed mismatches, rather than the internal QoS buffer allocation for the no-drop class, which is the critical design parameter for FC traffic in UCS.

How to eliminate wrong answers

Option A is wrong because the MTU on the Ethernet uplink from the FI being set to 1500 bytes would affect jumbo frame support for Ethernet traffic, but Fibre Channel over Ethernet (FCoE) traffic uses a separate encapsulation and is not directly impacted by the Ethernet MTU; the FCoE MTU is typically 2500 bytes and is handled independently. Option C is wrong because Fibre Channel buffer-to-buffer credit recovery is a mechanism to recover lost credits and is not directly related to QoS buffer allocation; disabling it could cause credit starvation but not the specific latency issue described. Option D is wrong because a speed mismatch between the vHBA (16 Gbps) and the upstream switch port (8 Gbps) would cause link negotiation to the lower speed, not excessive latency; the link would operate at 8 Gbps, which might reduce throughput but not inherently cause latency due to buffer exhaustion.

Practice this question →
35
MCQmedium

A UCS domain is configured with multiple service profile templates. An engineer wants to ensure that when a template is updated, all associated service profiles are automatically updated. Which property must be enabled in the template?

A.'Auto update'
B.'Update on deployment'
C.'Enforce consistency'
D.'Synchronize to templates'
AnswerB

When enabled, profiles derived from the template are automatically updated upon template changes.

Why this answer

The 'Update on deployment' property, when enabled in a service profile template, ensures that any changes made to the template are automatically applied to all associated service profiles during the next deployment or re-deployment. This is the correct mechanism in Cisco UCS Manager to propagate template updates to existing service profiles without manual intervention.

Exam trap

Cisco often tests the distinction between 'Update on deployment' and 'Enforce consistency', where candidates may confuse the automatic update mechanism with a compliance-checking policy, leading them to select the wrong option.

How to eliminate wrong answers

Option A is wrong because 'Auto update' is not a valid property in UCS service profile templates; it is a generic term that does not correspond to any specific UCS feature. Option C is wrong because 'Enforce consistency' is a policy used in UCS to validate configuration compliance, not to automatically update service profiles from a template. Option D is wrong because 'Synchronize to templates' is not a real property; the correct direction is from template to service profiles, and this option implies the reverse, which is not supported.

Practice this question →
36
Matchingmedium

Match each Cisco UCS component to its function.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Unified I/O and management for server chassis

Connects blade servers to fabric interconnects

Virtual interface card supporting multiple adapters

Out-of-band management controller for UCS servers

Enclosure that houses blade servers and IOMs

Why these pairings

These components form the building blocks of UCS infrastructure.

Practice this question →
37
Multi-Selectmedium

A company is planning to deploy Cisco Intersight to manage a hybrid environment including on-premises UCS domains and AWS EC2 instances. Which THREE of the following are required components for integrating AWS with Intersight?

Select 3 answers
A.An Intersight account with appropriate licenses
B.An Intersight Virtual Appliance deployed in AWS
C.A VPN tunnel between the on-premises network and AWS
D.An AWS IAM role with read-write access to EC2 and CloudFormation
E.Network connectivity from Intersight to the AWS public endpoints
AnswersA, D, E

An Intersight account is required to manage devices and use features.

Why this answer

Option A is correct because a valid Intersight account with the appropriate licenses (e.g., Intersight Essentials or Premier) is required to enable the AWS integration feature. Without the proper license tier, the Intersight account cannot access the cloud orchestration or management capabilities needed to connect and manage external cloud providers like AWS.

Exam trap

Cisco often tests the misconception that a virtual appliance or VPN tunnel is required for cloud provider integration, but Intersight uses direct API calls over the internet, making network connectivity to AWS public endpoints the only network requirement.

Practice this question →
38
MCQhard

During a UCS firmware upgrade, the upgrade fails on a few servers in a chassis. The administrators notice that the management plane is still responsive, but the data plane is disrupted. What is the most likely cause?

A.The secondary Fabric Interconnect did not synchronize the firmware image before the upgrade.
B.The boot policy was changed during maintenance.
C.The server memory is exhausted due to high traffic.
D.The service profiles were not updated after the upgrade.
AnswerA

Incomplete sync causes differing firmware versions between FIs, leading to data plane issues.

Why this answer

The most likely cause is that the secondary Fabric Interconnect did not synchronize the firmware image before the upgrade. In a UCS domain, firmware upgrades are typically performed in a hitless manner by first upgrading the secondary Fabric Interconnect, which requires the firmware image to be synchronized from the primary. If synchronization fails, the secondary may boot with an incompatible or missing firmware, causing data plane disruption while the management plane remains responsive because the primary still handles management traffic.

Exam trap

Cisco often tests the misconception that a failed upgrade always results in a complete loss of connectivity, but the trap here is that the management plane can remain operational even when the data plane is disrupted due to a firmware synchronization failure on the secondary Fabric Interconnect.

How to eliminate wrong answers

Option B is wrong because changing the boot policy during maintenance would affect the server's boot order or boot parameters, not cause a partial failure where management is up but data plane is down; boot policy changes do not directly impact firmware upgrade synchronization. Option C is wrong because server memory exhaustion due to high traffic would manifest as performance degradation or crashes, not a specific scenario where management plane is responsive and data plane is disrupted after a firmware upgrade; memory exhaustion is unrelated to firmware image synchronization. Option D is wrong because service profiles not being updated after the upgrade would cause configuration mismatches or policy application failures, but the immediate symptom of management plane up and data plane down points to a firmware image synchronization issue on the Fabric Interconnect, not a service profile update problem.

Practice this question →
39
MCQhard

A Cisco HyperFlex cluster is experiencing performance issues during peak hours. The cluster uses a 4-node all-flash configuration. The engineer notices that the vSphere DRS cluster is heavily imbalanced. Which HyperFlex feature should be used to improve performance by balancing the storage load across nodes?

A.Enable Storage DRS on the HyperFlex datastore
B.Enable the IOPS-based workload rebalancing feature
C.VM vMotion to move VMs to less busy nodes
D.Adjust the deduplication and compression settings to reduce write amplification
AnswerB

This feature automatically rebalances data across nodes based on IOPS, improving performance.

Why this answer

Option B is correct because the IOPS-based workload rebalancing feature in Cisco HyperFlex automatically redistributes storage I/O load across cluster nodes based on real-time IOPS metrics. This directly addresses the performance issue during peak hours by ensuring no single node becomes a storage bottleneck, which is the root cause of the vSphere DRS imbalance in a HyperFlex environment.

Exam trap

Cisco often tests the distinction between compute load balancing (vSphere DRS/VM vMotion) and storage I/O load balancing (HyperFlex IOPS rebalancing), leading candidates to mistakenly choose VM vMotion when the issue is storage-side, not compute-side, contention.

How to eliminate wrong answers

Option A is wrong because Storage DRS operates at the vSphere datastore level and manages VM placement across datastores, not the underlying HyperFlex storage node load; HyperFlex presents a single distributed datastore, making Storage DRS irrelevant for node-level I/O balancing. Option C is wrong because VM vMotion moves VMs between ESXi hosts to balance compute load, but it does not affect the storage I/O distribution across HyperFlex nodes, which is the actual performance bottleneck. Option D is wrong because adjusting deduplication and compression settings reduces write amplification and improves storage efficiency, but it does not dynamically rebalance existing I/O load across nodes during peak hours.

Practice this question →
40
Multi-Selectmedium

Which THREE of the following are valid UCS Manager RBAC roles?

Select 3 answers
A.Storage Administrator
B.Network Administrator
C.UCS Administrator
D.Operations Administrator
E.Server Administrator
AnswersB, C, E

Manages network-related configurations

Why this answer

Option B (Network Administrator) is correct because UCS Manager defines RBAC roles with specific privileges. The Network Administrator role is a built-in role that grants permissions to manage network-related configurations such as VLANs, VSANs, and QoS policies within the UCS domain.

Exam trap

Cisco often tests the distinction between default built-in roles and custom roles, and the trap here is that 'Storage Administrator' sounds plausible but is not a default role, while 'Operations Administrator' is a default role but is not one of the three correct answers in this specific question.

Practice this question →
41
MCQmedium

A data center administrator reports that traffic from a specific UCS server is not flowing through the expected Fabric Interconnect (FI) A. The pin group is configured, but traffic is still sent to FI B. What should the administrator check?

A.Verify that the server is associated with the correct service profile.
B.Reboot the Fabric Interconnect.
C.Check if the pin group is deleted.
D.Ensure the vNIC's fabric ID is set to match the pin group's preferred fabric.
AnswerD

The vNIC must have the fabric ID set to force traffic to the desired FI.

Why this answer

The pin group configuration determines which Fabric Interconnect a vNIC should use for upstream traffic. If the vNIC's fabric ID is not set to match the pin group's preferred fabric, the server will ignore the pin group and send traffic to the other FI. Option D is correct because the fabric ID mismatch causes the pin group to be ineffective, and verifying this alignment ensures traffic flows through the expected FI A.

Exam trap

Cisco often tests the subtle distinction between a pin group being configured and the vNIC's fabric ID being misaligned, leading candidates to assume the pin group is automatically applied without checking the vNIC-level fabric assignment.

How to eliminate wrong answers

Option A is wrong because the service profile association controls the server's identity and policies, not the specific fabric path selection for traffic; a correctly associated service profile can still have a vNIC fabric ID mismatch. Option B is wrong because rebooting the Fabric Interconnect is a disruptive action that does not address the configuration mismatch between the vNIC fabric ID and the pin group's preferred fabric. Option C is wrong because the pin group is confirmed to be configured; checking if it is deleted is irrelevant when the issue is that the vNIC is not honoring the existing pin group due to fabric ID mismatch.

Practice this question →
42
MCQmedium

A data center engineer is deploying a new application on Cisco UCS Manager. The application requires consistent low-latency access to storage. The engineer decides to use SAN boot from a Fibre Channel SAN. Which configuration change is necessary on the UCS service profile to enable SAN boot?

A.Enable VIF (Virtual Interface) on the vHBA
B.Configure a QoS policy for the vHBA
C.Set the vNIC to use dynamic MAC address
D.Assign a persistent WWPN to the vHBA
AnswerD

Persistent WWPN ensures the SAN target recognizes the server.

Why this answer

To enable SAN boot from a Fibre Channel SAN, the UCS service profile must assign a persistent WWPN to the vHBA. The WWPN is used by the Fibre Channel fabric to identify the initiator and to zone the storage LUNs; a persistent WWPN ensures that after a server reboot or vHBA reconfiguration, the same WWPN is presented to the SAN, allowing the boot LUN to remain accessible. Without a persistent WWPN, the vHBA would use a dynamically generated WWPN, which would break the SAN zoning and boot path.

Exam trap

Cisco often tests the distinction between vNIC (Ethernet) and vHBA (Fibre Channel) configurations, and the trap here is that candidates confuse MAC address persistence (for vNICs) with WWPN persistence (for vHBAs), leading them to incorrectly select Option C.

How to eliminate wrong answers

Option A is wrong because VIF (Virtual Interface) is a concept related to FCoE (Fibre Channel over Ethernet) and is not required for SAN boot over native Fibre Channel; enabling VIF on the vHBA is not a necessary configuration for SAN boot. Option B is wrong because a QoS policy for the vHBA controls traffic prioritization and bandwidth, but it does not affect the ability to boot from a SAN; QoS is optional and unrelated to SAN boot functionality. Option C is wrong because setting the vNIC to use a dynamic MAC address is relevant for Ethernet networking, not for Fibre Channel SAN boot; the vNIC is used for IP/Ethernet traffic, while SAN boot relies on the vHBA and its WWPN.

Practice this question →
43
MCQeasy

Which statement describes how firmware management works for UCS B-Series blade servers?

A.Firmware must be manually upgraded on each blade individually
B.Firmware is managed through host firmware packages in service profiles
C.Firmware is automatically updated via Cisco TAC
D.Firmware is stored on the fabric interconnect and loaded directly to the server
AnswerB

Host firmware packages define the firmware versions for each server

Why this answer

In Cisco UCS Manager, firmware for B-Series blade servers is managed through host firmware packages that are included in service profiles. These packages define the exact firmware versions for components like the BIOS, adapter, storage controller, and CIMC, and are automatically applied to the blade when the service profile is associated. This ensures consistent firmware levels across blades without manual intervention on each server.

Exam trap

Cisco often tests the misconception that firmware is applied directly from the fabric interconnect, when in fact it is staged locally on the blade and applied during reboot, and that manual per-blade updates are required in UCS Manager, which is incorrect due to the service profile abstraction.

How to eliminate wrong answers

Option A is wrong because firmware is not manually upgraded on each blade individually; UCS Manager automates firmware updates via service profile associations and host firmware packages. Option C is wrong because firmware is not automatically updated via Cisco TAC; TAC provides support but does not push firmware updates, and updates are initiated by the administrator through UCS Manager or Intersight. Option D is wrong because firmware is not stored on the fabric interconnect and loaded directly to the server; firmware images are stored in the UCS Manager repository and are applied to the blade's local storage or adapter memory during the boot process, not streamed directly from the FI.

Practice this question →
44
MCQeasy

A data center administrator needs to deploy a new blade server in a Cisco UCS chassis. The server must automatically inherit the correct service profile based on its slot location. Which feature should be configured?

A.Static service profile association
B.Qualifier-based service profile association
C.Service profile template with pool
D.Default service profile
AnswerB

Uses server attributes like slot ID to automatically map a profile, enabling zero-touch deployment.

Why this answer

Qualifier-based service profile association allows a service profile to be automatically applied to a blade server based on its slot location within the UCS chassis. This is achieved by configuring a qualifier that matches the chassis ID and slot number, enabling automatic inheritance without manual intervention.

Exam trap

The trap here is that candidates often confuse qualifier-based association with static association or service profile templates, mistakenly thinking that a template alone can automatically assign profiles based on location without a qualifier.

How to eliminate wrong answers

Option A is wrong because static service profile association requires manual assignment of a service profile to a specific server and does not support automatic inheritance based on slot location. Option C is wrong because a service profile template with pool is used for creating service profiles from a template with a pool of names or UUIDs, but it does not automatically associate profiles based on slot location. Option D is wrong because a default service profile is a fallback profile applied when no other profile is associated, but it is not designed to match specific slot locations for automatic inheritance.

Practice this question →
45
MCQhard

A large enterprise is using Cisco UCS Manager to manage a chassis with 8 B-Series blades. The environment uses a combination of Ethernet and Fibre Channel traffic. The UCS fabric interconnect (FI) is configured in end-host mode with two uplinks to the core network. Recently, the engineering team deployed a new service profile for a high-performance computing workload that requires 40Gbps Ethernet per vNIC and 16Gbps Fibre Channel per vHBA. The server has two vNICs and two vHBAs. After deployment, the server's OS shows only 10Gbps connectivity on each vNIC. The engineer checks UCS Manager and sees that the vNIC templates are set to '10 Gbps' and the vHBA templates are set to '16 Gbps' but the actual link speed for vNICs is only 10Gbps. The fabric interconnect ports are configured as 40Gbps uplinks. The engineer has verified that the server adapter supports 40Gbps. What is the most likely cause of the speed mismatch?

A.The fabric interconnect uplinks are configured as 40Gbps, but the port channel is not configured correctly, causing speed negotiation to fail.
B.The vNIC template used in the service profile specifies a requested speed of '10 Gbps' instead of '40 Gbps'.
C.The server's adapter policy is set to 'Windows' mode, which limits Ethernet speeds to 10Gbps.
D.The QoS policy applied to the vNIC limits the bandwidth to 10Gbps.
AnswerB

The vNIC template's speed setting determines the allocated speed; it must be set to 40Gbps.

Why this answer

The vNIC template in the service profile defines the requested speed for the virtual NIC. If the template is set to '10 Gbps', the UCS Manager will allocate only 10 Gbps of bandwidth per vNIC, regardless of the physical adapter's capability or the uplink speed. Since the engineer verified the adapter supports 40 Gbps and the uplinks are 40 Gbps, the mismatch is directly caused by the template configuration.

Exam trap

Cisco often tests the misconception that the physical adapter or uplink speed automatically determines the vNIC speed, when in fact the vNIC template's requested speed is the controlling parameter in UCS Manager.

How to eliminate wrong answers

Option A is wrong because the fabric interconnect uplinks are configured as 40 Gbps and the issue is not related to port channel misconfiguration; speed negotiation for vNICs is independent of uplink port channels. Option C is wrong because the server adapter policy (e.g., 'Windows' mode) does not limit Ethernet speeds to 10 Gbps; it affects driver behavior and failover settings, not link speed. Option D is wrong because a QoS policy applied to a vNIC can shape or limit bandwidth, but the question states the vNIC templates are set to '10 Gbps', and the OS shows 10 Gbps connectivity; QoS policies typically enforce maximum bandwidth after the link is established, not the negotiated link speed.

Practice this question →
46
MCQmedium

Refer to the exhibit. A UCS administrator applies a service profile with this boot policy to a blade. The blade boots from the SAN LUN successfully. However, after a reboot due to a firmware update, the blade boots from the local disk instead of the SAN. What is the most likely reason?

A.The WWPN of the SAN target is incorrect.
B.The SAN target LUN ID changed after the firmware update.
C.The boot order has local disk before the SAN target.
D.The local disk was not present at initial association.
AnswerC

Exhibit shows local-disk listed first.

Why this answer

The most likely reason is that the boot order in the service profile's boot policy lists the local disk before the SAN target. After a firmware update, the UCS Manager re-evaluates the boot policy, and if the local disk is present and has a higher priority, the blade will boot from it instead of the SAN LUN. The initial successful boot from SAN occurred because the local disk was not present at that time, but after the reboot, the local disk became available and took precedence.

Exam trap

The trap here is that candidates often assume a firmware update changes SAN parameters (like WWPN or LUN ID), but Cisco tests the concept that the boot order policy itself, not the SAN configuration, determines which device boots first when multiple bootable devices are present.

How to eliminate wrong answers

Option A is wrong because an incorrect WWPN of the SAN target would prevent any successful boot from the SAN LUN, not just after a reboot. Option B is wrong because a change in the SAN target LUN ID after a firmware update is unlikely and would cause a persistent boot failure, not a switch to local disk. Option D is wrong because the local disk not being present at initial association explains why the SAN boot worked initially, but it does not explain why the boot order policy itself would change; the boot order is static unless modified.

Practice this question →
47
MCQhard

A data center engineer is designing a UCS Manager solution that requires VLAN segmentation across multiple fabric interconnects. The network team requires that each VLAN is assigned a unique native VLAN ID per fabric. Which pool configuration supports this requirement?

A.Use derived VLAN pools based on chassis location
B.Create separate VLAN pools for each fabric with non-overlapping ranges
C.Create a single VLAN pool that includes all required VLANs
D.Configure VLANs directly in the service profile using inline pools
AnswerB

Separate pools enable unique native VLAN IDs per fabric

Why this answer

Option B is correct because UCS Manager allows separate VLAN pools to be assigned per fabric interconnect, enabling unique native VLAN IDs per fabric. By creating non-overlapping VLAN pools for each fabric, the engineer ensures that each fabric has its own native VLAN ID without conflict, meeting the requirement for VLAN segmentation across multiple fabric interconnects.

Exam trap

Cisco often tests the misconception that a single VLAN pool can be used for both fabrics, but the requirement for unique native VLAN IDs per fabric demands separate pools with non-overlapping ranges to avoid conflict.

How to eliminate wrong answers

Option A is wrong because derived VLAN pools based on chassis location do not provide per-fabric native VLAN differentiation; they are used for chassis-specific VLAN assignment, not for separating VLANs across fabrics. Option C is wrong because a single VLAN pool that includes all required VLANs would assign the same native VLAN ID to both fabrics, violating the requirement for unique native VLAN IDs per fabric. Option D is wrong because configuring VLANs directly in the service profile using inline pools does not allow per-fabric native VLAN assignment; inline pools are used for individual service profiles and cannot enforce separate native VLAN IDs across fabrics.

Practice this question →
48
MCQmedium

Refer to the exhibit. A UCS administrator has configured vNIC templates as shown. Both Fabric Interconnects have identical uplink configurations. The vNIC templates have 'Failover: Enabled'. However, when Fabric Interconnect A fails, servers using vNIC-A do not fail over to Fabric Interconnect B. What is the most likely cause?

A.A pin group is configured that forces traffic to Fabric Interconnect A.
B.The native VLAN (10) is not allowed on Fabric Interconnect B's trunk.
C.The uplink interfaces are configured with 'spanning-tree port type edge trunk', which blocks failover traffic.
D.The server's service profile does not include a secondary vNIC for Fabric B.
AnswerD

Failover requires a secondary vNIC on the other fabric in the same service profile.

Why this answer

Option D is correct because the server's service profile must include both a primary vNIC (for Fabric Interconnect A) and a secondary vNIC (for Fabric Interconnect B) to enable failover. The 'Failover: Enabled' setting on the vNIC template only allows the vNIC to use the other fabric's uplink if a secondary vNIC is explicitly defined in the service profile; without it, the vNIC is pinned to its original fabric and cannot fail over.

Exam trap

Cisco often tests the misconception that enabling 'Failover' on a vNIC template alone is sufficient for failover, when in reality a secondary vNIC must be explicitly added to the service profile to provide the alternate fabric path.

How to eliminate wrong answers

Option A is wrong because a pin group that forces traffic to Fabric Interconnect A would prevent failover, but the question states that vNIC templates have 'Failover: Enabled', and a pin group would override that setting only if explicitly configured; the scenario does not mention any pin group, so this is an unlikely cause. Option B is wrong because the native VLAN (10) not being allowed on Fabric Interconnect B's trunk would cause connectivity issues for VLAN 10 traffic, but it would not prevent the vNIC from failing over to Fabric B's uplinks; failover is a fabric-level path selection, not a VLAN-specific behavior. Option C is wrong because 'spanning-tree port type edge trunk' (PortFast trunk) does not block failover traffic; it enables faster convergence by skipping STP on the uplink ports, and failover traffic is not blocked by this configuration.

Practice this question →
49
MCQmedium

A data center administrator is troubleshooting slow storage performance on a UCS B-Series blade server. The server is connected to a Cisco UCS 6300 Series Fabric Interconnect and uses local SAS drives. The administrator checks the UCS Manager and sees that the storage adapter has a driver version that is not recommended. What is the most likely impact of using a non-recommended driver version?

A.Degraded storage performance or instability
B.Loss of redundancy on the fabric interconnect
C.Inability to boot the server
D.Increased security vulnerabilities
AnswerA

Non-recommended drivers are not validated and can cause performance issues or system instability.

Why this answer

Using a non-recommended driver version for the storage adapter in a UCS B-Series blade server can lead to degraded storage performance or system instability. Cisco validates specific driver versions for compatibility with the UCS 6300 Series Fabric Interconnect and local SAS drives; deviations may cause suboptimal I/O handling, increased latency, or unexpected errors. This is a common issue in compute environments where driver- firmware mismatches affect storage throughput.

Exam trap

Cisco often tests the distinction between a 'non-recommended' driver (which causes performance or stability issues) versus a 'non-supported' driver (which could cause boot failure or complete non-functionality), tempting candidates to overestimate the impact.

How to eliminate wrong answers

Option B is wrong because loss of redundancy on the fabric interconnect is typically caused by misconfigured port channels, link failures, or fabric-level issues, not by a storage adapter driver version. Option C is wrong because while a severely incompatible driver could prevent boot, the question specifies a 'non-recommended' driver, which usually causes performance issues rather than complete boot failure; UCS servers can still boot with non-optimal drivers. Option D is wrong because driver versions primarily affect functionality and performance, not security posture; security vulnerabilities are addressed through firmware and software patches, not driver version recommendations.

Practice this question →
50
MCQeasy

An enterprise requires that all virtual machines using a specific service profile must have the same MAC address pool. Which policy should be configured on the service profile template?

A.MAC Pool Policy
B.UUID Pool Policy
C.Server Pool Policy
D.WWPN Pool Policy
AnswerA

MAC pool defines the range and is attached to the vNIC in the profile.

Why this answer

A MAC Pool Policy is correct because it defines a range of MAC addresses that are dynamically assigned to virtual network adapters in a service profile. When multiple VMs use the same service profile template, configuring a MAC Pool Policy ensures all VMs derive their MAC addresses from the same pool, guaranteeing consistency and avoiding address conflicts across the cluster.

Exam trap

The trap here is that candidates confuse MAC Pool Policy with UUID Pool Policy, assuming both handle identity assignment, but only MAC Pool Policy controls the Ethernet address pool for virtual NICs.

How to eliminate wrong answers

Option B is wrong because a UUID Pool Policy assigns unique identifiers to virtual machines, not MAC addresses, and does not control network interface addressing. Option C is wrong because a Server Pool Policy manages physical server selection for service profile association, not MAC address assignment. Option D is wrong because a WWPN Pool Policy assigns World Wide Port Names for Fibre Channel adapters, not Ethernet MAC addresses.

Practice this question →
51
MCQhard

Refer to the exhibit. A UCS manager profile is configured with two vNICs on separate fabrics. The server is failing to communicate with the default gateway on VLAN 100. Both vNICs are up. What is the most likely issue?

A.The MAC pool is exhausted
B.The VLAN 100 is not defined on the fabric interconnects
C.The boot policy is missing
D.The server is using active-standby NIC teaming and the active vNIC is on a fabric that does not have the VLAN
AnswerB

If VLAN 100 is absent on the FIs, traffic cannot be forwarded to the gateway.

Why this answer

The most likely issue is that VLAN 100 is not defined on the fabric interconnects. In UCS Manager, even if the vNICs are up and the MAC pool is available, the server cannot communicate with the default gateway if the VLAN is not present on the fabric interconnect's VLAN database. The fabric interconnect must have VLAN 100 created and assigned to the appropriate uplink ports or port-channels for traffic to be forwarded.

Exam trap

Cisco often tests the misconception that a vNIC being 'up' implies full Layer 2 connectivity, when in fact the VLAN must be defined on the fabric interconnect for traffic to be switched.

How to eliminate wrong answers

Option A is wrong because a MAC pool exhaustion would prevent vNICs from being assigned a MAC address, but both vNICs are up, indicating MAC addresses are already assigned. Option C is wrong because the boot policy determines the boot order and storage connectivity, not Layer 2/3 network communication to a default gateway. Option D is wrong because active-standby NIC teaming (e.g., using MAC pinning or vPC) would still allow communication if the active vNIC is on the fabric with VLAN 100; the issue is that VLAN 100 is missing on both fabrics, not a teaming misconfiguration.

Practice this question →
52
MCQeasy

Refer to the exhibit. The blade server is unassociated. Which action is required to assign a service profile to this server?

A.Configure the server's BIOS settings
B.Create a service profile and associate it with the server
C.Create a boot policy
D.Create a vNIC template
AnswerB

Directly associates the server with a profile, enabling configuration.

Why this answer

A service profile defines the server identity, firmware, policies, and connectivity settings for a UCS blade server. When a server is unassociated, you must create a service profile and then associate it with the server to apply those configurations and bring the server into operation.

Exam trap

Cisco often tests the distinction between creating a component policy (like boot policy or vNIC template) versus creating and associating the service profile itself, leading candidates to mistake a sub-component for the primary action.

How to eliminate wrong answers

Option A is wrong because BIOS settings are configured within the service profile or BIOS policy, not as a standalone prerequisite for association. Option C is wrong because a boot policy is a component that can be included in a service profile, but creating one alone does not assign a service profile to the server. Option D is wrong because a vNIC template is used to define network interface properties within a service profile, but it is not the action required to associate a service profile with the server.

Practice this question →
53
Multi-Selecthard

Which THREE conditions must be met before a UCS Fabric Interconnect can be part of a port channel? (Select THREE.)

Select 3 answers
A.Ports should come from different FEX modules for redundancy.
B.All ports must be on the same side of the switch (either all uplink or all server-facing).
C.Ports should be configured as admin down until the port channel is formed.
D.The ports must belong to the same virtual port channel (vPC) domain.
E.All ports in the port channel must have the same speed and duplex settings.
AnswersB, D, E

Port channels cannot mix uplink and server ports.

Why this answer

Option B is correct because in a UCS Fabric Interconnect, a port channel can only be formed using ports that are all on the same side of the switch—either all uplink ports (connecting to the upstream network) or all server-facing ports (connecting to FEX or servers). Mixing uplink and server-facing ports in a single port channel is not supported due to the distinct forwarding behaviors and VLAN configurations applied to each port type.

Exam trap

Cisco often tests the misconception that port channel member ports can be from any combination of port types (e.g., uplink and server-facing), but the correct requirement is that they must all be on the same side of the switch to ensure consistent forwarding behavior.

Practice this question →
54
MCQmedium

An engineer is troubleshooting a UCS B-Series server that fails to boot from SAN. The SAN boot LUN is correctly zoned and presented. The service profile has WWPNs configured. What is a likely cause?

A.Server firmware mismatch
B.Missing vNIC template
C.VLAN mismatch
D.Incorrect boot policy order
AnswerD

The server will attempt boot devices in the order defined; if SAN is not first, it may fail.

Why this answer

The SAN boot LUN is correctly zoned and presented, and the WWPNs are configured in the service profile, so the connectivity and identity are set. However, if the boot policy order is incorrect (e.g., the SAN boot target is listed after a local disk or another boot device), the server will attempt to boot from the wrong device first and fail to boot from the SAN. The boot policy defines the sequence of boot devices, and a misconfigured order is a common cause of boot failures in UCS B-Series.

Exam trap

Cisco often tests the misconception that SAN boot failures are always due to zoning or WWPN misconfiguration, when in fact the boot policy order is a separate, critical setting that must be correctly configured in the service profile.

How to eliminate wrong answers

Option A is wrong because a server firmware mismatch would typically cause compatibility issues or boot failures at a lower level, but the question states the LUN is correctly zoned and presented, and the issue is specifically about boot order, not firmware version mismatch. Option B is wrong because a missing vNIC template would prevent the vNIC from being created in the service profile, but the service profile already has WWPNs configured, implying the vNIC is present. Option C is wrong because a VLAN mismatch would affect network connectivity after boot, not the ability to boot from SAN, which uses Fibre Channel (FC) zoning, not VLANs.

Practice this question →
55
MCQhard

A large enterprise runs a Cisco HyperFlex cluster with three nodes, managed through Intersight. After a planned maintenance window, the administrator notices that one of the nodes is in a 'Degraded' state and the cluster is running in 'Read-Only' mode. The administrator checks the Intersight dashboard and sees that the node's disk status shows 'Missing' for one of the SSDs. The administrator also notices that the node's IP address is reachable and the ESXi host is still operational. The administrator reviews the cluster health and sees no other alerts. What is the most likely root cause and the recommended action to restore full cluster health?

A.The SSD failed due to a hardware fault; the administrator should replace the SSD and then use Intersight to rebuild the node's disk group.
B.The node lost connectivity to the cluster's internal network; the administrator should check the network switches and restore the VLAN configuration.
C.The node's controller VM (stCVM) is not running; the administrator should reboot the node and wait for the CVM to start.
D.The cluster has split-brain due to a partition; the administrator should force a cluster consensus by shutting down the other nodes.
AnswerA

A failed SSD is a common cause of a missing disk. Replacing the SSD and rebuilding the disk group restores redundancy and cluster health.

Why this answer

A is correct because a missing SSD in a HyperFlex node triggers a 'Degraded' state and forces the cluster into 'Read-Only' mode to prevent data corruption. Since the node's IP is reachable and ESXi is operational, the issue is a hardware fault, not a network or CVM problem. Replacing the SSD and using Intersight to rebuild the disk group restores the node's storage capacity and cluster health.

Exam trap

The trap here is that candidates may assume a 'Degraded' state with reachable ESXi implies a network or CVM issue, but the specific 'Missing' disk status points directly to a hardware fault, not a software or connectivity problem.

How to eliminate wrong answers

Option B is wrong because the node's IP is reachable and ESXi is operational, indicating no network connectivity loss; a VLAN misconfiguration would cause unreachability, not a missing SSD status. Option C is wrong because if the stCVM were not running, the node would likely be unreachable or show a different alert, and the disk status would not specifically show 'Missing' for an SSD. Option D is wrong because split-brain occurs when nodes lose quorum, typically due to network partition, not a single missing SSD; forcing consensus by shutting down other nodes would cause data loss and is not a recommended recovery step.

Practice this question →
56
Multi-Selecteasy

Which three components are required to boot a UCS blade server from SAN? (Choose three.)

Select 3 answers
A.SAN boot target LUN
B.vHBA
C.Boot policy
D.iSCSI adapter
E.vNIC
AnswersA, B, C

The actual storage unit from which to boot.

Why this answer

A SAN boot target LUN is required because the UCS blade server needs a specific logical unit number (LUN) on the storage array from which to boot the operating system. Without a designated boot LUN, the server has no target storage device to load the OS from over the Fibre Channel (FC) or FCoE SAN fabric.

Exam trap

Cisco often tests the distinction between vNIC (LAN) and vHBA (SAN), so candidates mistakenly select vNIC for SAN boot, not realizing that storage traffic requires a dedicated HBA abstraction.

Practice this question →
57
MCQmedium

Refer to the exhibit. An administrator updates template-B but its associated profile SP2 shows 'unassigned'. The administrator wants SP2 to reflect the changes. What should be done first?

A.Disable and re-enable template-B
B.Wait for the automatic association to occur
C.Associate SP2 with template-B using the 'bind' operation
D.Rebind all profiles to template-B
AnswerC

Binding creates the link between profile and template.

Why this answer

In Cisco UCS Manager, a service profile (SP2) must be explicitly bound to a template (template-B) to inherit updates. The 'bind' operation associates the profile with the template, allowing changes made to the template to propagate to the profile. Simply disabling and re-enabling the template or waiting for automatic association does not establish this binding; the profile remains 'unassigned' until it is bound.

Exam trap

Cisco often tests the distinction between 'updating templates' and 'initial templates', where candidates mistakenly assume that simply enabling or refreshing a template will automatically update associated profiles, overlooking the explicit bind requirement.

How to eliminate wrong answers

Option A is wrong because disabling and re-enabling a template does not change the association state of a service profile; it only toggles the template's operational status without affecting the binding. Option B is wrong because Cisco UCS Manager does not automatically associate a service profile with a template; the administrator must manually perform a bind operation to link the profile to the template. Option D is wrong because rebinding all profiles to template-B is unnecessary and could disrupt other profiles; only SP2 needs to be bound to template-B to reflect the changes.

Practice this question →
58
MCQmedium

An engineer notices that after a reboot of one UCS fabric interconnect (FI-A), the server traffic fails over to FI-B but never fails back to FI-A even after FI-A is fully operational. Which configuration change would ensure automatic failback?

A.Change the 'Backup Link' policy to 'Active/Active'
B.Change the 'Backup Link' policy to 'Primary/Secondary'
C.Change the 'Backup Link' policy to 'Active/Standby'
D.Change the 'Backup Link' policy to 'Failover Only'
AnswerA

Active/Active mode allows automatic failback

Why this answer

The 'Backup Link' policy in UCS determines how uplink ports behave during failover and failback. Setting it to 'Active/Active' allows both FIs to actively forward traffic, and when the failed FI recovers, the server traffic automatically fails back because the policy does not designate a permanent primary or standby role. This ensures symmetric traffic flow without manual intervention.

Exam trap

Cisco often tests the misconception that 'Active/Standby' is a valid Backup Link policy, when in fact the only two options are 'Active/Active' and 'Primary/Secondary', and candidates confuse the failover behavior of the server vNIC policy with the uplink Backup Link policy.

How to eliminate wrong answers

Option B is wrong because 'Primary/Secondary' designates one FI as primary and the other as secondary, which prevents automatic failback after the primary recovers; traffic remains on the secondary until manual action is taken. Option C is wrong because 'Active/Standby' is not a valid UCS Backup Link policy; the correct term is 'Active/Active' or 'Primary/Secondary', and 'Active/Standby' would imply a standby role that blocks automatic failback. Option D is wrong because 'Failover Only' is not a valid UCS Backup Link policy; the actual options are 'Active/Active' and 'Primary/Secondary', and a 'Failover Only' concept would not allow failback at all.

Practice this question →
59
MCQhard

An organization deploys compute resources using both UCS B-Series blades and C-Series rack servers. The network uses Cisco ACI. Which approach ensures consistent connectivity policies across both compute types?

A.Use a single EPG with appropriate encapsulation for both
B.Create separate EPGs for blade and rack servers
C.It is not possible to have consistent policies between blade and rack
D.Use a physical domain for blades and a VMM domain for rack servers
AnswerA

Single EPG ensures consistent policy application

Why this answer

Option A is correct because Cisco ACI allows a single Endpoint Group (EPG) to span both UCS B-Series blades and C-Series rack servers by using the appropriate encapsulation (e.g., VLAN or VXLAN) and associating the EPG with both a physical domain (for blades connected via Fabric Interconnects) and a VMM domain (for rack servers managed by VMware vCenter). This ensures consistent connectivity policies, such as contracts and QoS, are applied uniformly across all compute types without requiring separate EPGs.

Exam trap

Cisco often tests the misconception that different compute types (blade vs. rack) require separate EPGs, when in fact a single EPG can span multiple domains to enforce consistent policies, and the trap here is assuming that physical and VMM domains are mutually exclusive rather than complementary.

How to eliminate wrong answers

Option B is wrong because creating separate EPGs for blade and rack servers would fragment policy enforcement, requiring duplicate contracts and filters, which contradicts the goal of consistent connectivity policies. Option C is wrong because it is entirely possible to have consistent policies between blade and rack servers using a single EPG with appropriate domain associations, as supported by Cisco ACI's unified policy model. Option D is wrong because using a physical domain for blades and a VMM domain for rack servers is a valid approach to associate the EPG with both compute types, but the statement incorrectly implies they must be used separately; in fact, both domains can be attached to the same EPG to achieve consistency.

Practice this question →
60
MCQeasy

Which best practice should be followed when creating a UCS service profile template for stateless computing?

A.Assign MAC and WWN addresses from pools
B.Use local storage on each server for boot images
C.Configure Windows Server NIC teaming for all vNICs
D.Define MAC addresses directly in the service profile
AnswerA

Pools enable auto-assignment and stateless operation

Why this answer

Stateless computing in UCS requires that all server identity information, such as MAC addresses and WWNs, be abstracted away from the hardware and assigned dynamically from pools. This allows the service profile to be applied to any compatible blade or rack server without manual reconfiguration, enabling rapid provisioning and seamless hardware replacement. Defining these addresses directly in the profile or using static assignments would break the stateless model by tying the profile to specific hardware.

Exam trap

Cisco often tests the misconception that stateless computing means you can hardcode identities like MAC addresses for consistency, when in fact the opposite is true—pools are essential to maintain the stateless abstraction.

How to eliminate wrong answers

Option B is wrong because stateless computing relies on centralized boot from SAN or network storage, not local storage, to ensure that server identity and data are independent of the physical hardware; using local storage would reintroduce statefulness. Option C is wrong because Windows Server NIC teaming is a guest OS-level configuration that should be handled separately from the UCS service profile, which manages vNIC failover via fabric failover or pinning at the infrastructure layer. Option D is wrong because defining MAC addresses directly in the service profile defeats the purpose of stateless computing by creating a hard dependency on specific addresses, preventing the profile from being reused across different servers without conflict.

Practice this question →
61
MCQmedium

Refer to the exhibit. The server in slot 2 is associated and working. A new server is inserted into slot 1, but after 30 minutes it remains in 'Unassigned' state. What is the most likely reason?

A.The service profile is already associated with another server.
B.The server is not powered on.
C.The server's CIMC firmware is not compatible with the Fabric Interconnect firmware.
D.The Fabric Interconnect ports are not configured as server ports.
AnswerC

Incompatibility can cause discovery to fail, leaving the slot unassigned.

Why this answer

The server in slot 1 remains in 'Unassigned' state because its CIMC firmware is incompatible with the Fabric Interconnect firmware. In Cisco UCS, the CIMC on each blade must match a supported firmware version for the Fabric Interconnect to discover and manage the server. When firmware versions are mismatched, the server cannot transition to the 'Associated' state and stays 'Unassigned'.

Exam trap

Cisco often tests the distinction between 'Unassigned' (server not discovered/manageable) and 'Unassociated' (server discovered but not bound to a service profile), leading candidates to incorrectly attribute the issue to service profile association or power state.

How to eliminate wrong answers

Option A is wrong because if the service profile were already associated with another server, the new server would show as 'Unassociated' (available for association) or would fail association, not remain 'Unassigned' — the 'Unassigned' state indicates the server is not yet discovered or manageable. Option B is wrong because a server not powered on would still be discovered by the Fabric Interconnect and appear in a 'Discovered' or 'Unassociated' state; power state does not prevent the server from being assigned a service profile. Option D is wrong because Fabric Interconnect ports configured as server ports are required for server connectivity, but if they were misconfigured, the existing server in slot 2 would also be affected and not working — the exhibit shows slot 2 is associated and working, so port configuration is correct.

Practice this question →
62
Multi-Selectmedium

Which THREE are benefits of using Cisco UCS Manager to manage compute resources? (Choose three.)

Select 3 answers
A.Centralized management of multiple chassis
B.Direct management of virtual machines
C.Policy-based provisioning to automate server deployment
D.Improved performance by disabling hardware features
E.Unified fabric for LAN and SAN traffic
AnswersA, C, E

UCS Manager manages up to 160 chassis.

Why this answer

Option A is correct because Cisco UCS Manager provides a single-pane-of-glass management interface that can centrally manage up to 160 chassis (including UCS 5108 and UCS 9508) in a single domain. This eliminates the need to configure each chassis individually, reducing operational overhead and ensuring consistent configuration across the entire compute infrastructure.

Exam trap

Cisco often tests the distinction between what UCS Manager directly manages (physical compute and fabric) versus what it integrates with (hypervisors for VMs), so candidates mistakenly think UCS Manager can manage VMs because of its integration with VMware vCenter.

Practice this question →
63
MCQeasy

An organization has deployed a Cisco UCS B-Series blade server with a Fabric Interconnect pair. The administrator is tasked with deploying a new server for a critical application. The administrator creates a service profile from an existing template that includes vNIC, vHBA, and storage policies. The blade is located in chassis 2, slot 1. The administrator attempts to associate the profile with this blade but fails with the error: 'No suitable compute resource available.' The administrator verifies that the blade's firmware is updated, that the blade is not already associated with another profile, and that it has sufficient memory and CPU. What is the most likely cause?

A.The blade's firmware version is incompatible with the service profile.
B.The blade is in the wrong chassis slot.
C.The server pool policy is not assigned to the service profile template.
D.The vNIC/vHBA policies in the service profile have invalid MAC/WWN assignments.
AnswerC

Without a server pool, UCS Manager cannot determine which blade to use for the association, leading to the 'No suitable compute resource available' error.

Why this answer

The error 'No suitable compute resource available' typically occurs when the service profile is configured to use a server pool, but no server pool policy is assigned to the service profile template. Without a server pool, the Fabric Interconnect cannot identify which blades are eligible for association, even if the blade itself is available and meets hardware requirements. Assigning a server pool policy to the template ensures that blades in the specified pool (e.g., chassis 2, slot 1) are considered as valid compute resources.

Exam trap

Cisco often tests the concept that 'No suitable compute resource available' is not about hardware faults or firmware mismatches but about the absence of a server pool policy in the service profile template, which candidates may overlook because they focus on verifying blade hardware readiness.

How to eliminate wrong answers

Option A is wrong because the administrator already verified that the blade's firmware is updated, and firmware incompatibility would typically generate a different error (e.g., 'Firmware version mismatch') rather than 'No suitable compute resource available.' Option B is wrong because the blade's location (chassis 2, slot 1) is explicitly specified in the service profile association attempt, and the error is not about physical slot constraints but about logical resource selection. Option D is wrong because invalid MAC/WWN assignments would cause a policy validation failure or association error related to network/storage configuration, not a 'no suitable compute resource' error, which is specifically about the blade not being found in the available resource pool.

Practice this question →
64
MCQhard

A UCS administrator notices that a server in a UCS domain is not booting from SAN after a firmware upgrade. The service profile shows the correct WWPN and boot policy. The SAN switch sees the initiator login. However, the storage array does not see any initiator attempts. What is the most likely issue?

A.The boot policy is missing the primary SAN target
B.The WWPN is duplicated on another initiator
C.The zone alias on the SAN switch does not match the initiator WWPN
D.The VSAN membership is incorrect on the fabric interconnect
AnswerC

The zone alias mismatch would allow login (since zoning is based on WWPN) but the storage may not see the initiator if zones are misconfigured.

Why this answer

The SAN switch sees the initiator login, but the storage array does not see any initiator attempts. This indicates that the Fibre Channel fabric is blocking the initiator's WWPN from reaching the storage target, typically because the zone configuration on the SAN switch does not include the initiator's WWPN or the zone alias does not match the actual WWPN. Since the service profile and boot policy are correct, and the VSAN membership is functional (the switch sees the login), the most likely issue is a zoning mismatch on the SAN switch.

Exam trap

Cisco often tests the distinction between fabric-level visibility (FLOGI success) and zone-level communication (PLOGI/PRLI failure) to trick candidates into assuming the issue is with the boot policy or VSAN membership rather than zoning.

How to eliminate wrong answers

Option A is wrong because the boot policy is confirmed correct in the question, and a missing primary SAN target would cause the server to fail to find the boot LUN, but the storage array would still see initiator attempts if zoning were correct. Option B is wrong because a duplicate WWPN would cause login conflicts or fabric segmentation, but the SAN switch sees the initiator login successfully, ruling out duplication. Option D is wrong because incorrect VSAN membership would prevent the fabric interconnect from seeing the initiator login at all, but the SAN switch does see the login, indicating VSAN membership is functional.

Practice this question →
65
Matchingmedium

Match each Cisco MDS FC switch feature to its purpose.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Virtual SAN for isolating Fibre Channel traffic

Access control between initiators and targets

Routing protocol for Fibre Channel fabric

Fibre Channel over IP for remote connectivity

Inter-VSAN routing for selective communication

Why these pairings

These features are key for managing Fibre Channel SANs.

Practice this question →
66
MCQmedium

A data center engineer is configuring a Cisco UCS C-Series server with a hardware RAID controller. The server will host a critical database. The RAID controller supports RAID 0, 1, 5, 6, and 10. Which RAID level should be chosen to provide the best combination of performance and fault tolerance?

A.RAID 10
B.RAID 6
C.RAID 5
D.RAID 0
AnswerA

RAID 10 combines mirroring and striping, offering both performance and fault tolerance.

Why this answer

RAID 10 (striping of mirrors) provides the best combination of performance and fault tolerance for a critical database workload. It offers high read/write performance through striping and full redundancy via mirroring, allowing up to one disk failure per mirrored pair without data loss. This is ideal for a Cisco UCS C-Series server with a hardware RAID controller where both I/O throughput and availability are paramount.

Exam trap

Cisco often tests the misconception that RAID 5 or RAID 6 offer 'good enough' performance for databases, but the trap is that parity-based RAIDs introduce significant write penalties that degrade transactional throughput, making RAID 10 the correct choice for critical database workloads.

How to eliminate wrong answers

Option B (RAID 6) is wrong because while it offers dual parity and can tolerate two disk failures, its write performance is significantly degraded due to double parity calculations, making it unsuitable for a performance-sensitive database. Option C (RAID 5) is wrong because its single parity provides lower fault tolerance and suffers from a write penalty during parity updates, which can bottleneck database transactions. Option D (RAID 0) is wrong because it offers no fault tolerance; any single disk failure results in complete data loss, which is unacceptable for a critical database.

Practice this question →
67
MCQmedium

A company is deploying a new Cisco UCS Mini with a single Fabric Interconnect 6324. They need to connect to an existing Fibre Channel SAN. Which action is required to enable Fibre Channel connectivity?

A.Enable NPV mode on the Fabric Interconnect to connect to the SAN.
B.Install a Fibre Channel module in the Fabric Interconnect.
C.Add a Cisco MDS 9148S Fibre Channel switch and connect it to the Fabric Interconnect via FC uplinks.
D.Configure the uplink Ethernet ports as unified ports to support Fibre Channel.
AnswerC

A dedicated FC switch provides SAN connectivity for UCS Mini.

Why this answer

The Cisco UCS Mini with a single Fabric Interconnect 6324 does not have native Fibre Channel ports; it only supports Ethernet uplinks. To connect to an existing Fibre Channel SAN, an external Fibre Channel switch (such as the Cisco MDS 9148S) must be added, and the Fabric Interconnect connects to it via FC uplinks, which are typically configured as unified ports. This allows the UCS Mini to leverage the MDS switch for Fibre Channel connectivity, as the 6324 itself cannot directly terminate Fibre Channel links.

Exam trap

Cisco often tests the misconception that the UCS Fabric Interconnect 6324 can directly connect to a Fibre Channel SAN by simply enabling NPV mode or using unified ports, but the key trap is that the 6324 lacks native Fibre Channel ports and requires an external Fibre Channel switch (like the MDS) to bridge the FCoE traffic to the FC SAN.

How to eliminate wrong answers

Option A is wrong because NPV (N_Port Virtualization) mode is used on a Fibre Channel switch to connect to an upstream SAN fabric, but the Fabric Interconnect 6324 does not have native Fibre Channel ports to run NPV; NPV is configured on the MDS switch, not the UCS Fabric Interconnect. Option B is wrong because the Fabric Interconnect 6324 does not support a Fibre Channel module; it only has fixed Ethernet ports and unified ports that can be configured for Fibre Channel, but no expansion module slot for FC. Option D is wrong because while unified ports can be configured on the 6324 to support Fibre Channel, they only provide connectivity to a downstream FCoE or FC device, not directly to a Fibre Channel SAN; the unified ports must be connected to an external Fibre Channel switch (like the MDS) to reach the SAN fabric.

Practice this question →
68
MCQhard

A Cisco UCS upgrade from release 3.1(1) to 4.0(4) is planned. The current release has a known issue that affects NVRAM backup. What is the best practice to avoid an outage during this upgrade?

A.Perform a cold reboot of all Fabric Interconnects before starting.
B.Upgrade all components simultaneously to reduce transition time.
C.Upgrade the firmware on the chassis first, then the Fabric Interconnects.
D.Upgrade to an intermediate release that is recommended for the upgrade path.
AnswerD

Most major upgrades require stepping through an intermediate release.

Why this answer

Option D is correct because Cisco UCS firmware upgrades must follow a supported upgrade path to avoid incompatibilities and known issues. Skipping directly from 3.1(1) to 4.0(4) is not supported; an intermediate release (e.g., 3.2(x) or 4.0(1)) is required to resolve the NVRAM backup issue and ensure a seamless upgrade without service disruption.

Exam trap

Cisco often tests the concept of supported upgrade paths and intermediate releases, trapping candidates who assume direct upgrades are always possible or that component order can be rearranged arbitrarily.

How to eliminate wrong answers

Option A is wrong because a cold reboot of all Fabric Interconnects before starting would cause an immediate outage, defeating the purpose of avoiding downtime; the upgrade process itself handles reboots gracefully. Option B is wrong because upgrading all components simultaneously violates Cisco's recommended sequential upgrade order (Fabric Interconnects first, then chassis IOMs, then servers) and increases the risk of configuration mismatches and extended downtime. Option C is wrong because the chassis firmware should be upgraded after the Fabric Interconnects, not before, as the Fabric Interconnects control the management plane and must be at a compatible version first.

Practice this question →
69
MCQmedium

A UCS administrator notices that a service profile associated with a vNIC template that uses 'fabric failover' is not failing over to the secondary Fabric Interconnect when the primary link goes down. The vNIC template is set to 'fabric failover' enabled, and both Fabric Interconnects are in the same VLAN. What is the most likely cause?

A.The 'Primary Fabric' setting is not defined in the vNIC template.
B.The server is pinned to the primary Fabric Interconnect via a pin group.
C.The MTU size on the secondary Fabric Interconnect is set to 1500 instead of 9000.
D.The 'MAC Address' policy is set to 'pool-based' instead of 'static'.
AnswerA

The primary fabric must be selected in the vNIC template for failover to function correctly.

Why this answer

When 'fabric failover' is enabled on a vNIC template, the UCS Manager requires the 'Primary Fabric' setting to be explicitly defined to determine which Fabric Interconnect (FI-A or FI-B) should be the active path. Without this setting, the system cannot properly orchestrate the failover behavior, causing the vNIC to remain pinned to the primary FI even when its link goes down. This is a common misconfiguration because the 'fabric failover' checkbox alone does not imply a primary fabric assignment.

Exam trap

Cisco often tests the misconception that enabling 'fabric failover' alone is sufficient for automatic failover, when in fact the 'Primary Fabric' field must also be explicitly configured to define the active path.

How to eliminate wrong answers

Option B is wrong because a pin group explicitly pins a server to a specific Fabric Interconnect, which would prevent failover by design; however, the question states the vNIC template uses 'fabric failover' enabled, and a pin group would override that setting, but the most likely cause is the missing 'Primary Fabric' definition, not the presence of a pin group. Option C is wrong because MTU size mismatch (1500 vs 9000) affects jumbo frame support and packet fragmentation, not the failover mechanism between Fabric Interconnects. Option D is wrong because the MAC Address policy (pool-based vs static) determines how MAC addresses are assigned to vNICs, but it has no impact on fabric failover behavior.

Practice this question →
70
MCQmedium

A data center engineer is using Cisco Intersight to manage a hybrid infrastructure that includes UCS servers and HyperFlex clusters. The engineer needs to deploy a new server profile to a UCS domain that is claimed in Intersight. The profile includes a firmware policy that specifies version 4.1(3c) for the motherboard and 5.0(3a) for the storage controller. The target server is a C-Series rack mount server currently running firmware version 4.0(2a) on the motherboard. After deploying the profile, the server goes into a 'Pending' state and does not become 'Selectable'. The engineer checks the UCS Manager and sees that the server is in 'Discovery Failed' state. The engineer has verified that network connectivity is fine and the CIMC is accessible. What should the engineer do to resolve this?

A.Ensure that the firmware policy in Intersight is consistent with the current firmware on the server.
B.Remove the server from Intersight inventory and re-claim it.
C.Reset the server's CIMC to factory defaults and re-discover it.
D.Update the firmware manually on the server using UCS Manager before deploying the profile.
AnswerD

Manually updating the firmware to a version compatible with the UCS domain will allow the server to be discovered, after which the profile can be applied.

Why this answer

Option D is correct because when a firmware policy in Intersight specifies a version that is not compatible with the current firmware on the server, the server may enter a 'Discovery Failed' state. In this scenario, the motherboard firmware must be updated to a version that supports the storage controller firmware 5.0(3a) before the profile can be applied. Manually updating the firmware via UCS Manager ensures the server meets the prerequisite firmware baseline, allowing Intersight to complete the deployment.

Exam trap

Cisco often tests the concept that firmware policies have dependency chains, and candidates mistakenly think that a simple re-claim or reset will fix a 'Discovery Failed' state, when in fact the root cause is an incompatible firmware version that must be manually updated first.

How to eliminate wrong answers

Option A is wrong because ensuring consistency between the firmware policy and the current firmware would defeat the purpose of the policy, which is to enforce a target version; the issue is not consistency but compatibility. Option B is wrong because removing and re-claiming the server would not resolve the underlying firmware incompatibility; it would only reset the inventory state without addressing the firmware version mismatch. Option C is wrong because resetting the CIMC to factory defaults would erase configuration but not change the firmware version; the server would still fail discovery due to the incompatible firmware.

Practice this question →
71
MCQeasy

Refer to the exhibit. The Fabric Interconnect cannot ping its default gateway. The management interface is configured and up. What is the most likely cause?

A.The default route is missing from the routing table.
B.The management VLAN is not allowed on the upstream switch.
C.The management interface is configured as DHCP instead of static.
D.The IP address is a duplicate on the network.
AnswerA

Without a default route, the FI cannot reach subnets beyond its own.

Why this answer

The Fabric Interconnect cannot ping its default gateway despite the management interface being up and configured, which indicates that the device lacks a route to reach the gateway subnet. A default route is required to forward traffic destined for networks not directly connected; without it, the Fabric Interconnect will drop packets to the gateway even if the interface is operational. This is the most likely cause because the exhibit shows no default route in the routing table, and the interface status confirms Layer 1 and Layer 2 connectivity.

Exam trap

Cisco often tests the distinction between interface-level connectivity (Layer 1/Layer 2) and routing (Layer 3), leading candidates to incorrectly blame VLAN pruning or IP conflicts when the real issue is a missing default route in the management VRF.

How to eliminate wrong answers

Option B is wrong because if the management VLAN were not allowed on the upstream switch, the interface would likely be in a down/down or err-disabled state, but the exhibit states the management interface is configured and up, indicating VLAN pruning is not the issue. Option C is wrong because the exhibit explicitly shows a static IP address configuration (e.g., IP address and subnet mask), so DHCP misconfiguration is not applicable. Option D is wrong because a duplicate IP address would cause intermittent connectivity or address conflict messages, but the interface would still be up and able to send ARP requests; the inability to ping the gateway points to a routing problem, not an IP conflict.

Practice this question →
72
MCQhard

An engineer is deploying a new UCS chassis with two Fabric Interconnects. The design requires that server traffic can fail over to the secondary FI if the primary FI fails, without requiring any changes to the server's network configuration. Which technology must be enabled on the uplink ports of the Fabric Interconnects to the upstream switches to ensure transparent failover of server traffic?

A.Configure a virtual PortChannel (vPC) between the Fabric Interconnects and upstream switches.
B.Apply QoS policies to prioritize failover traffic.
C.Enable pin groups with 'failover' mode on the server ports.
D.Implement Private VLANs on the uplink ports to isolate traffic.
AnswerC

Pin groups with failover mode allow the secondary FI to assume the primary's MAC and IP, enabling transparent failover.

Why this answer

Pin groups with 'failover' mode enable transparent server traffic failover by pinning server vNICs to a specific Fabric Interconnect (FI) and automatically repinning them to the secondary FI upon primary FI failure, without requiring any changes to the server's network configuration. This ensures that the server's MAC and IP addresses remain active on the secondary FI, maintaining connectivity without manual intervention.

Exam trap

Cisco often tests the distinction between upstream redundancy technologies (like vPC) and server-side failover mechanisms (like pin group failover mode), leading candidates to incorrectly choose vPC for transparent server failover when it only addresses link redundancy to the upstream network.

How to eliminate wrong answers

Option A is wrong because a virtual PortChannel (vPC) between Fabric Interconnects and upstream switches provides link-level redundancy and load balancing, but it does not handle server-side failover; vPC is an upstream switch technology, not a mechanism for transparent server failover between FIs. Option B is wrong because QoS policies prioritize traffic types but do not provide any failover mechanism; they are unrelated to transparent server failover. Option D is wrong because Private VLANs isolate traffic within a VLAN for security purposes and have no role in failover or repinning server traffic between Fabric Interconnects.

Practice this question →
73
Multi-Selecthard

Which THREE factors should be considered when determining the number of upstream Ethernet uplinks from a UCS Fabric Interconnect to the core network? (Choose THREE.)

Select 3 answers
A.Number of VLANs defined on the Fabric Interconnect.
B.Server CPU oversubscription ratio.
C.The number of vNICs per service profile and their bandwidth limits.
D.Total expected traffic from server blades.
E.Redundancy and high availability requirements.
AnswersC, D, E

More vNICs may require more uplinks for queuing.

Why this answer

Option C is correct because the number of vNICs per service profile and their bandwidth limits directly determine the aggregate traffic that must be carried by the upstream Ethernet uplinks. Each vNIC is assigned a specific bandwidth cap (e.g., via QoS policy or vNIC template), and the sum of these caps across all service profiles on a Fabric Interconnect dictates the minimum uplink capacity required to avoid oversubscription.

Exam trap

Cisco often tests the distinction between Layer 2 constructs (VLANs) and actual bandwidth consumption, leading candidates to incorrectly select the number of VLANs as a factor for uplink sizing.

Practice this question →
74
MCQhard

A company is deploying a Cisco UCS Mini in a remote office. They need to support both VMware vSphere and Microsoft Hyper-V on the same UCS domain. What is the best practice for deploying compute resources for both hypervisors?

A.Create separate service profile templates for each hypervisor
B.Use a single service profile but assign different VLANs for management traffic
C.Place each hypervisor in a separate UCS Organization within the same service profile template
D.Create a single service profile template and use different identity pools for each hypervisor
AnswerA

Separate templates enable boot order, firmware, and BIOS settings per hypervisor.

Why this answer

Separate service profile templates are required because VMware vSphere and Microsoft Hyper-V have different boot and storage configuration requirements. Each hypervisor needs its own boot policy (e.g., SAN boot vs. local disk), firmware settings, and potentially different vNIC/vHBA configurations. Using distinct templates ensures that each hypervisor's compute resources are correctly provisioned without conflicts.

Exam trap

Cisco often tests the misconception that VLANs or identity pools alone can differentiate hypervisor configurations, when in fact the core differences lie in boot and storage policies that require separate service profile templates.

How to eliminate wrong answers

Option B is wrong because a single service profile cannot accommodate the different boot policies, firmware versions, and storage configurations required by two distinct hypervisors; VLAN assignment for management traffic does not address these fundamental differences. Option C is wrong because UCS Organizations are used for administrative separation and RBAC, not to define different compute resource configurations within a single service profile template; a single template still applies the same policies to all servers. Option D is wrong because identity pools (e.g., UUID, MAC, WWN) only manage unique identifiers, not the boot order, firmware, or storage policies that differ between hypervisors; a single template with different pools still enforces the same configuration.

Practice this question →
75
MCQhard

Refer to the exhibit. A server with vNIC eth0 is experiencing packet drops on its Ethernet interface. The server is sending jumbo frames (MTU 9000) on VLAN 100. The QoS system class 'Class-Platinum' has an MTU of 9216 and is configured with 'Drop'. The vNIC is not assigned to any QoS policy. What is the most likely reason for the drops?

A.The vNIC is not mapped to a QoS policy, so it uses the default best-effort class which has an MTU of 1500 and drops jumbo frames.
B.The QoS system class for jumbo frames requires a 'No Drop' policy to avoid drops.
C.The server is sending frames larger than 9216 bytes.
D.The native VLAN setting on the vNIC causes the QoS system class to be ignored.
AnswerA

Without a QoS policy, the default class (often Bronze) applies, which has MTU 1500.

Why this answer

When a vNIC is not assigned to a QoS policy, it defaults to the best-effair class, which typically has an MTU of 1500 bytes. Since the server is sending jumbo frames (MTU 9000) on VLAN 100, these frames exceed the default MTU and are dropped at the Ethernet interface. The 'Class-Platinum' system class with MTU 9216 is irrelevant because the vNIC is not mapped to it.

Exam trap

Cisco often tests the misconception that a system class with a higher MTU (like Class-Platinum) automatically applies to all traffic, when in fact the vNIC must be explicitly mapped to that QoS policy to use it.

How to eliminate wrong answers

Option B is wrong because a 'No Drop' policy (e.g., using pause frames or priority flow control) is not required for jumbo frames; the issue is the MTU mismatch, not the drop/no-drop setting. Option C is wrong because the server is sending frames of MTU 9000, which is less than the system class MTU of 9216, so the frames are not oversized for the system class. Option D is wrong because the native VLAN setting does not cause the QoS system class to be ignored; the vNIC's lack of a QoS policy assignment is the direct cause of defaulting to the best-effort class.

Practice this question →
Page 1 of 2 · 104 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Dc Compute questions.

Start 20-question session