Courseiva

CCNA Dc Compute Questions

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

Practice these questionsExam hubAll questions
76
Multi-Selecteasy

A storage administrator reports that a Cisco UCS domain is not booting from the Fibre Channel SAN. The boot policy is correctly configured and the vHBA is associated. Which two alignment issues could cause this problem? (Choose two.)

Select 2 answers
A.The WWPN of the vHBA is not zoned on the SAN fabric.
B.The vHBA is assigned to an incorrect VSAN.
C.The Ethernet LAN is not configured on the FI.
D.The disk firmware on the server is outdated.
AnswersA, B

Proper WWPN zoning is critical for SAN boot.

Why this answer

Option A is correct because if the WWPN of the vHBA is not properly zoned on the SAN fabric, the Fibre Channel switch will not allow the server to log in to the target storage. Even with a correct boot policy and vHBA association, without zoning, the initiator cannot discover or communicate with the boot LUN, causing the boot to fail.

Exam trap

The trap here is that candidates often focus only on the UCS-side configuration (boot policy, vHBA association) and forget that SAN fabric-level settings like zoning and VSAN assignment are equally critical for Fibre Channel boot to succeed.

Practice this question →
77
MCQeasy

A startup company is deploying a new web application on UCS B-Series blades. They want to use PXE boot for rapid provisioning. The network team has configured a DHCP server and a PXE server on the same VLAN as the UCS service profiles. The system administrator creates a service profile for a blade and sets the boot policy to 'PXE' as the first boot device, and local disk as second. However, when the blade powers on, it boots from the local disk instead of PXE. The PXE server logs show no request from the blade's MAC address. The DHCP server logs show no activity. The fabric interconnect is configured with a default VLAN. What is the most likely cause?

A.The vNIC on the service profile is not configured with the correct native VLAN
B.The boot policy order lists local disk before PXE
C.The service profile is not properly associated with the blade
D.The fabric interconnect uplinks are not in trunk mode
AnswerA

Native VLAN mismatch prevents DHCP from reaching the server

Why this answer

Option A is correct because PXE boot requires the vNIC to have an untagged native VLAN that matches the PXE/DHCP subnet. If the native VLAN on the vNIC is different, DHCP requests are not forwarded. Option B wrong because PXE boot order is usually correct.

Option C wrong because it would cause different symptoms. Option D wrong because service profile association is fine.

Practice this question →
78
MCQeasy

An administrator needs to reset the CIMC password on a Cisco UCS C-Series server without physical access. Which method can be used?

A.Use the front panel reset button
B.Use UCS Manager
C.Use the CIMC XML API
D.Connect via serial console during boot
AnswerC

Allows remote management commands, including password change.

Why this answer

The CIMC XML API allows remote management of Cisco UCS C-Series servers, including password resets, without physical access. This API provides a programmatic interface to CIMC functions, enabling administrators to send authenticated XML requests over HTTPS to reset the CIMC password. Physical access is not required because the API operates over the network, making it the correct method for this scenario.

Exam trap

Cisco often tests the distinction between UCS Manager (for B-Series and integrated environments) and CIMC (for C-Series standalone servers), leading candidates to incorrectly assume UCS Manager can manage C-Series servers directly.

How to eliminate wrong answers

Option A is wrong because the front panel reset button requires physical access to the server, which the administrator does not have. Option B is wrong because UCS Manager manages UCS B-Series blade servers and fabric interconnects, not C-Series standalone servers; C-Series servers are managed directly via CIMC, not through UCS Manager. Option D is wrong because connecting via serial console during boot requires physical access to the server's serial port or a remote console solution that is not available without physical presence.

Practice this question →
79
Multi-Selectmedium

An engineer is configuring a Cisco UCS Manager deployment. The goal is to enforce the organization's security policy by limiting administrative access based on job roles. Which two actions should the engineer take? (Select two.)

Select 2 answers
A.Disable the default password policy for all local users.
B.Use the default maintenance policy for all service profiles.
C.Implement role-based access control using LDAP groups mapped to roles.
D.Configure RBAC by defining roles and assigning users to those roles.
E.Create a local user with the admin role and assign it to all service profiles.
AnswersC, D

Integrating with LDAP allows centralized management of user groups and roles, simplifying administration and security.

Why this answer

C is correct because integrating LDAP groups with RBAC allows the organization to enforce security policies by mapping directory groups to UCS roles, centralizing authentication and authorization. This approach ensures that administrative access is limited based on job roles without managing local users, aligning with the goal of role-based access control.

Exam trap

The trap here is that candidates often confuse RBAC with local user management or maintenance policies, assuming that disabling password defaults or using default policies somehow restricts access, when in fact RBAC requires explicit role definitions and user-to-role mappings.

Practice this question →
80
MCQhard

During a capacity planning review, an engineer notices that a UCS domain with 8 blades (each with 16 cores) is using 70% CPU average. The environment runs VDI workloads. Each VM requires 2 vCPUs and 4 GB RAM. The hypervisor uses 1:1 CPU oversubscription. How many additional VMs can be deployed before reaching 100% CPU utilization?

A.19
B.23
C.17
D.21
AnswerA

38 remaining vCPUs / 2 per VM = 19.

Why this answer

The UCS domain has 8 blades × 16 cores = 128 cores. With 1:1 CPU oversubscription, the hypervisor can allocate 128 vCPUs. Each VM requires 2 vCPUs, so the maximum VMs are 128 / 2 = 64.

Currently at 70% CPU, 0.70 × 128 = 89.6 vCPUs are used, meaning 89.6 / 2 = 44.8 VMs (round to 45 VMs). The remaining vCPUs are 128 - 89.6 = 38.4, allowing 38.4 / 2 = 19.2 additional VMs, so 19 VMs can be deployed before hitting 100% CPU utilization.

Exam trap

Cisco often tests the trap of confusing CPU utilization percentage with the number of vCPUs already allocated, leading candidates to incorrectly calculate remaining capacity by applying the percentage to the total VM count rather than to the total vCPU count.

How to eliminate wrong answers

Option B (23) is wrong because it incorrectly assumes a higher oversubscription ratio (e.g., 1.5:1) or miscalculates the remaining vCPUs. Option C (17) is wrong because it likely uses a lower total core count (e.g., 112 cores) or misapplies the 70% utilization to total VMs instead of vCPUs. Option D (21) is wrong because it might result from rounding errors or using 75% utilization instead of 70%.

Practice this question →
81
MCQhard

A UCS administrator is deploying a 3-node HyperFlex cluster with vSphere. Each node has a single vNIC for management and two vNICs for storage data traffic. During the cluster creation, the storage vNIC MTU must be configured. What is the recommended MTU value for the storage data vNICs in HyperFlex?

A.1500
B.9216
C.9000
D.4096
AnswerC

Recommended for HyperFlex storage data.

Why this answer

C is correct because HyperFlex storage data vNICs require jumbo frame support to optimize storage traffic performance. The recommended MTU value for these vNICs is 9000, which allows larger packet sizes and reduces CPU overhead for storage I/O operations. This value is consistent with Cisco's best practices for HyperFlex cluster deployments.

Exam trap

Cisco often tests the specific recommended MTU value of 9000 for HyperFlex storage vNICs, and the trap here is that candidates may confuse it with the maximum jumbo frame size of 9216 supported by some switches, or assume the standard 1500 MTU is sufficient for storage traffic.

How to eliminate wrong answers

Option A is wrong because an MTU of 1500 is the standard Ethernet MTU and does not support jumbo frames, which are necessary for efficient storage traffic in HyperFlex. Option B is wrong because 9216 is a common jumbo frame MTU value for some Cisco switches, but HyperFlex specifically recommends 9000, not 9216, for storage vNICs. Option D is wrong because 4096 is not a standard jumbo frame MTU value; it is too small to provide the benefits of jumbo frames and is not recommended by Cisco for HyperFlex storage data traffic.

Practice this question →
82
MCQmedium

An engineer has configured a service profile with a WWPN pool that has exhausted its assigned range. The server boots from SAN. What happens when the server is associated?

A.The server associates but fails to boot because no WWPN is assigned.
B.The administrator is prompted to manually enter a WWPN.
C.The association fails until new WWPNs are added to the pool.
D.The server associates with a temporary WWPN from the conflict-free range.
AnswerD

Correct behavior.

Why this answer

When a WWPN pool is exhausted, Cisco UCS automatically assigns a temporary WWPN from the conflict-free range (00:00:00:00:00:00 to 00:00:00:00:00:FF) to allow the server to associate and boot from SAN. This temporary WWPN is used only until a permanent WWPN becomes available from the pool, ensuring the server can still access storage during the interim period.

Exam trap

Cisco often tests the misconception that pool exhaustion causes association failure, but the correct behavior is that UCS uses a temporary WWPN from the conflict-free range to maintain boot-from-SAN functionality.

How to eliminate wrong answers

Option A is wrong because the server does associate and boot successfully using a temporary WWPN from the conflict-free range, not fail due to no WWPN assignment. Option B is wrong because Cisco UCS does not prompt for manual entry; it automatically assigns a temporary WWPN from the conflict-free range. Option C is wrong because the association does not fail; it proceeds with a temporary WWPN, and new WWPNs can be added to the pool later without disrupting the association.

Practice this question →
83
MCQmedium

A UCS administrator needs to update the firmware on a UCS 5108 chassis that contains eight B-Series blades. The firmware update must be performed with minimal downtime. Which update method should be used?

A.Fast-Impact update
B.Non-Impactful update with a forced reboot
C.User Acknowledged update with a maintenance policy that reboots blades sequentially
D.System-Impactful update with a single reboot
AnswerC

This method allows the administrator to control when blades reboot, minimizing downtime by staggering reboots.

Why this answer

Option C is correct because the User Acknowledged update method, combined with a maintenance policy that reboots blades sequentially, allows the firmware update to proceed blade by blade with minimal downtime. This approach ensures that only one blade is offline at a time, while the remaining blades continue to serve traffic, making it ideal for a chassis with eight B-Series blades where service continuity is critical.

Exam trap

Cisco often tests the distinction between 'User Acknowledged' and 'Non-Impactful' updates, trapping candidates who mistakenly think that a non-impactful update can include a forced reboot, when in fact any reboot makes the update impactful.

How to eliminate wrong answers

Option A is wrong because Fast-Impact update is designed for scenarios where immediate, disruptive updates are acceptable, not for minimizing downtime. Option B is wrong because Non-Impactful update with a forced reboot contradicts the definition of a non-impactful update, which should not require a reboot; a forced reboot would cause unnecessary downtime. Option D is wrong because System-Impactful update with a single reboot would take the entire chassis or all blades offline simultaneously, resulting in maximum downtime, which is the opposite of the requirement.

Practice this question →
84
MCQeasy

A UCS administrator needs to ensure that server boot order always starts from the local disk if available, and falls back to a SAN LUN if local disk fails. Which boot policy setting should be used?

A.Local Disk alone
B.SAN first, then Local Disk
C.SAN Boot Only
D.Local Disk first, then SAN
AnswerD

Matches the requirement.

Why this answer

Option D is correct because the UCS boot policy allows you to specify a boot order where the local disk is attempted first. If the local disk is unavailable or fails, the system automatically falls back to the next boot device in the list, which is the SAN LUN. This ensures high availability and aligns with the requirement to prefer local boot while providing a failover path.

Exam trap

Cisco often tests the misconception that 'SAN first, then Local Disk' provides a fallback to local disk, but the trap is that the order is reversed, causing the server to always boot from SAN first, which does not satisfy the requirement to prefer local disk when available.

How to eliminate wrong answers

Option A is wrong because 'Local Disk alone' provides no fallback if the local disk fails, leaving the server unable to boot. Option B is wrong because 'SAN first, then Local Disk' reverses the required order, causing the server to always attempt SAN boot before local disk, which does not meet the requirement to start from local disk if available. Option C is wrong because 'SAN Boot Only' forces boot exclusively from the SAN LUN with no option to boot from local disk, even if the local disk is functional.

Practice this question →
85
Drag & Dropmedium

Order the steps to configure FCoE on a Cisco Nexus switch with NPV mode.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order

Why this order

FCoE requires feature fcoe, VSAN mapping, VLAN config, NPV mode, and fabric login.

Practice this question →
86
Multi-Selecteasy

Which TWO are important considerations when using Cisco UCS Central for multi-domain management? (Select TWO.)

Select 2 answers
A.UCS Central requires separate licensing per managed server.
B.Global policies can be defined in UCS Central and applied per domain with local overrides.
C.All domains must have identical hardware and firmware versions.
D.UCS Central communicates with both Fabric Interconnects in each domain for redundancy.
E.Local UCS Manager policies are always overridden by UCS Central policies.
AnswersB, D

This is a key feature of UCS Central.

Why this answer

Option B is correct because Cisco UCS Central allows administrators to define global policies that can be applied across multiple UCS domains, while still permitting local overrides at the UCS Manager level. This hierarchical policy model provides centralized control without sacrificing the flexibility needed for domain-specific configurations, such as unique VLANs or boot policies.

Exam trap

Cisco often tests the misconception that UCS Central enforces strict homogeneity across domains, but the correct understanding is that it supports heterogeneous environments with flexible policy inheritance and local overrides.

Practice this question →
87
MCQmedium

Refer to the exhibit. An administrator notices the blade firmware is outdated. What is the recommended first step to update the blade firmware?

A.Upgrade the fabric interconnects first
B.Update each blade individually using the CIMC
C.Reboot all blades immediately
D.Create a firmware management policy to stage the update
AnswerD

Allows orchestrated update across all blades with minimal disruption.

Why this answer

Option D is correct because Cisco UCS Manager uses firmware management policies to stage firmware updates across blades in a controlled, non-disruptive manner. Staging the update allows the administrator to schedule the activation during a maintenance window, ensuring all blades receive the same firmware version consistently without immediate impact on production traffic.

Exam trap

The trap here is that candidates often assume a direct, immediate action like rebooting or manual updates is required, but Cisco tests the understanding that UCS Manager provides a policy-based staging mechanism to safely orchestrate firmware updates across multiple blades.

How to eliminate wrong answers

Option A is wrong because upgrading fabric interconnects first is not the recommended first step for blade firmware; fabric interconnect firmware updates are independent and should be coordinated but not necessarily performed before blade updates. Option B is wrong because updating each blade individually using the CIMC is inefficient, error-prone, and bypasses the centralized management capabilities of UCS Manager, which can automate and validate the update process. Option C is wrong because rebooting all blades immediately without staging the firmware could cause unexpected downtime and service disruption, and it does not address the need to actually update the firmware.

Practice this question →
88
MCQmedium

In a Cisco HyperFlex cluster, a new ESXi host is being added. The host is discovered, but the cluster health status shows 'Degraded'. What should be the first troubleshooting step?

A.Reboot the new ESXi host.
B.Verify that the new host's controller VM has the same firmware version as the cluster.
C.Check if the vCenter Server is in maintenance mode.
D.Delete and re-create the cluster.
AnswerB

Firmware consistency is critical for cluster stability.

Why this answer

When adding a new ESXi host to a Cisco HyperFlex cluster, the controller VM (CVM) firmware version must match the cluster's version. A mismatch causes the cluster health status to show 'Degraded' because the CVMs cannot properly synchronize storage operations. Verifying and aligning the firmware version is the first troubleshooting step, as it directly impacts cluster stability.

Exam trap

Cisco often tests the misconception that a 'Degraded' cluster health status is due to network or vCenter issues, when in fact it frequently stems from firmware or software version mismatches in the HyperFlex storage layer.

How to eliminate wrong answers

Option A is wrong because rebooting the new ESXi host will not resolve a firmware version mismatch; it only restarts services without addressing the root cause. Option C is wrong because vCenter Server maintenance mode affects vCenter operations, not HyperFlex cluster health; a host in maintenance mode would not cause a 'Degraded' status due to firmware mismatch. Option D is wrong because deleting and re-creating the cluster is an extreme, unnecessary step that would disrupt operations; the issue is isolated to the new host's CVM firmware, not the cluster configuration.

Practice this question →
89
MCQmedium

A company is deploying a new Cisco UCS Mini. They need to ensure that the chassis can be managed from either fabric interconnect. What configuration is required to achieve this?

A.Configure a private VLAN to isolate management traffic
B.Set the chassis to in-band management mode
C.Enable FC-Zoning on the fabric interconnects
D.Configure a management VLAN on both fabric interconnects and enable chassis management on that VLAN
AnswerD

This allows the chassis to be reachable from both FIs for management purposes.

Why this answer

Option D is correct because Cisco UCS Mini requires a dedicated management VLAN to be configured on both fabric interconnects, and chassis management must be enabled on that VLAN. This allows the chassis management controller (CMC) to be reachable from either FI, enabling active/standby management redundancy without relying on a single point of control.

Exam trap

The trap here is that candidates often confuse in-band management (Option B) with the required out-of-band management VLAN configuration, mistakenly thinking that using the data path is sufficient for redundant chassis management.

How to eliminate wrong answers

Option A is wrong because private VLANs are used to isolate traffic within a VLAN (e.g., for multi-tenant environments) and are not required for chassis management redundancy in UCS Mini. Option B is wrong because in-band management mode is used for managing the chassis through the data path (e.g., via a server's vNIC), not for enabling management from either fabric interconnect; the correct approach is out-of-band management via a dedicated management VLAN. Option C is wrong because FC-Zoning is a Fibre Channel storage networking concept used to control access in a SAN fabric and has no role in enabling chassis management from either FI.

Practice this question →
90
MCQhard

A UCS domain is experiencing intermittent storage connectivity. The storage admin confirms the SAN is properly zoned and the VSANs are configured. The UCS admin finds that the host interface (HBAs) are showing 'Link Down' intermittently. Which of the following is a likely cause?

A.Incompatible HBA firmware
B.Mismatched fabric failover policy
C.Incorrect Fibre Channel interface mode on the FI
D.Faulty SFP or cable
AnswerD

Physical layer issues often cause intermittent link flapping.

Why this answer

Intermittent 'Link Down' on HBAs, despite correct SAN zoning and VSAN configuration, strongly points to a physical-layer issue. Faulty SFPs or damaged cables cause intermittent link flaps, which manifest as sporadic HBA link-down events. This is the most common cause of such symptoms in UCS environments.

Exam trap

Cisco often tests the distinction between physical-layer issues (SFP/cable) and configuration or policy errors, tempting candidates to overthink with fabric failover or interface mode when the symptom is a simple link flap.

How to eliminate wrong answers

Option A is wrong because incompatible HBA firmware typically causes persistent driver errors or failure to log in to the fabric, not intermittent link flaps. Option B is wrong because mismatched fabric failover policy affects how traffic is redirected during a failure, not the physical link state of the HBA. Option C is wrong because incorrect Fibre Channel interface mode on the FI (e.g., End Host vs.

Switching mode) impacts upstream FLOGI behavior and zoning, not the point-to-point link status between the HBA and the FI.

Practice this question →
91
MCQhard

A UCS domain has two fabric interconnects in end-host mode. The engineer needs to implement a policy that ensures all traffic from a specific vNIC is load-balanced across both uplinks to the upstream switches. Which type of policy should be used?

A.Link aggregation policy
B.Pin group policy
C.QoS policy
D.Network control policy
AnswerB

Allows pinning a vNIC to specific uplinks or 'no-pin' for load balancing across all.

Why this answer

In a UCS domain with fabric interconnects in end-host mode, a Pin Group policy is used to explicitly map a vNIC's traffic to specific uplink ports, ensuring load balancing across the upstream switches. This policy overrides the default MAC-based hashing and allows the engineer to control traffic distribution, which is critical for consistent performance and redundancy.

Exam trap

Cisco often tests the distinction between Pin Group policies (which control per-vNIC traffic distribution) and Link Aggregation policies (which bundle ports), leading candidates to mistakenly choose the latter when the question emphasizes load balancing across individual uplinks rather than aggregated bandwidth.

How to eliminate wrong answers

Option A is wrong because a Link Aggregation policy (LACP) bundles multiple uplinks into a single logical link for increased bandwidth and redundancy, but it does not control per-vNIC traffic distribution across individual uplinks; it operates at the port-channel level. Option C is wrong because a QoS policy manages traffic prioritization and bandwidth allocation, not load balancing or path selection for a specific vNIC. Option D is wrong because a Network Control policy defines Layer 2 features like STP or LLDP, but it does not influence how vNIC traffic is pinned or load-balanced across uplinks.

Practice this question →
92
MCQmedium

A company recently deployed Cisco UCS B-Series blades with a single Fabric Interconnect. During a maintenance window, the Fabric Interconnect must be upgraded. Which action ensures minimal disruption to running workloads?

A.Disassociate service profiles from blades, upgrade the Fabric Interconnect, then re-associate the service profiles.
B.Use the UCS Manager GUI to migrate all service profiles to a second Fabric Interconnect.
C.Shut down all blades gracefully, upgrade the Fabric Interconnect, then power on blades.
D.Change the boot order of blades to boot from NFS image, then upgrade FI.
AnswerA

Blades continue running; only management connectivity is lost temporarily.

Why this answer

Option A is correct because disassociating service profiles from the blades detaches the logical configuration from the physical hardware, allowing the single Fabric Interconnect to be upgraded without affecting the running workloads. The blades continue to run their current operating system and applications, and once the upgrade is complete, re-associating the service profiles restores management connectivity without requiring a reboot or workload interruption.

Exam trap

Cisco often tests the misconception that shutting down blades or migrating to a second Fabric Interconnect is required, but the key is that disassociating service profiles decouples management from the running workload, enabling a non-disruptive upgrade on a single Fabric Interconnect.

How to eliminate wrong answers

Option B is wrong because migrating service profiles to a second Fabric Interconnect requires a second Fabric Interconnect to be present, but the scenario specifies a single Fabric Interconnect, making this option technically impossible. Option C is wrong because shutting down all blades gracefully causes a complete outage for all running workloads, which is not minimal disruption. Option D is wrong because changing the boot order to boot from an NFS image does not address the Fabric Interconnect upgrade; the blades still rely on the Fabric Interconnect for network connectivity, and the upgrade would disrupt that connectivity.

Practice this question →
93
MCQmedium

An engineer is designing a UCS Mini deployment for a remote office. The chassis will contain four blade servers. Each server needs two 10GbE connections for data and one 1GbE for management. What is the minimum number of fabric interconnects required?

A.One
B.Three
C.Four
D.Two
AnswerA

UCS Mini can operate with a single FI for up to four blades, meeting the requirement.

Why this answer

A single UCS Mini fabric interconnect (FI) can provide both data and management connectivity for up to eight blade servers in a single chassis. Each blade server requires two 10GbE data connections (from the integrated VIC) and one 1GbE management connection (from the Cisco Integrated Management Controller, or CIMC). The FI aggregates these connections internally, so one FI is sufficient for a four-server deployment, as UCS Mini supports a single FI configuration for non-redundant setups.

Exam trap

Cisco often tests the misconception that each blade server's management connection requires a separate physical port or that two FIs are always needed for any UCS deployment, but UCS Mini's integrated architecture allows a single FI to handle both data and management for up to eight blades.

How to eliminate wrong answers

Option B is wrong because three fabric interconnects are not supported in UCS Mini; the architecture only supports one or two FIs for redundancy. Option C is wrong because four fabric interconnects exceed the maximum supported in any UCS Mini configuration (max two). Option D is wrong because two fabric interconnects are only required for redundancy (e.g., for high availability or dual-homing), not for meeting the minimum connectivity needs of four blade servers; the question asks for the minimum number.

Practice this question →
94
Multi-Selectmedium

Which TWO statements about Cisco UCS service profiles are correct? (Choose TWO.)

Select 2 answers
A.Service profiles are only supported on B-Series blades.
B.Service profiles can include policies for firmware management.
C.A service profile can be associated with one server at a time.
D.Service profiles are tied to specific physical hardware.
E.A service profile does not include network identity settings such as MAC addresses.
AnswersB, C

Firmware policies can be included.

Why this answer

Option B is correct because Cisco UCS service profiles can include firmware management policies that specify the firmware versions to be applied to the associated server components, such as adaptors, BIOS, and storage controllers. This allows administrators to enforce consistent firmware levels across the infrastructure without manual intervention.

Exam trap

Cisco often tests the misconception that service profiles are hardware-specific or only apply to B-Series blades, when in fact they are designed to be hardware-agnostic and support both blade and rack server form factors.

Practice this question →
95
MCQmedium

A UCS B-Series blade server shows high CPU latency when processing network I/O. The engineer suspects a bottleneck in the I/O subsystem. Which metric in UCS Manager should be examined first?

A.vNIC utilization percentage
B.Fabric port error counts
C.Memory usage statistics
D.Power consumption per server
AnswerB

Errors cause retransmissions and latency

Why this answer

Fabric port error counts directly reflect physical-layer issues (e.g., CRC errors, alignment errors, link flaps) that cause retransmissions and backpressure, leading to high CPU latency on the blade server. In UCS Manager, these counters are the first place to check when suspecting an I/O subsystem bottleneck because they pinpoint problems in the fabric interconnect or cabling before examining higher-layer metrics.

Exam trap

Cisco often tests the distinction between utilization metrics (which show load) and error metrics (which show health), so candidates mistakenly pick vNIC utilization thinking high usage equals a bottleneck, when the real issue is physical-layer errors causing retransmissions.

How to eliminate wrong answers

Option A is wrong because vNIC utilization percentage measures throughput usage, not errors or latency; high utilization alone does not cause CPU latency unless accompanied by errors or congestion. Option C is wrong because memory usage statistics indicate system memory pressure, which can affect overall performance but is not specific to the I/O subsystem or network latency. Option D is wrong because power consumption per server relates to thermal or power capacity issues, not to network I/O latency or fabric errors.

Practice this question →
96
MCQeasy

An engineer is configuring a UCS server profile for a database application that requires low latency. The server will use a Cisco UCS VIC 1340 adapter. Which vNIC placement policy should be selected to minimize latency?

A.Assigned
B.Any
C.Default
D.Round-Robin
AnswerA

Assigned placement pins the vNIC to a specific adapter port, reducing latency.

Why this answer

The Assigned vNIC placement policy binds each vNIC to a specific physical port on the Cisco UCS VIC 1340 adapter, ensuring deterministic traffic flow and predictable latency. For low-latency database applications, this eliminates the variability introduced by dynamic placement, allowing the engineer to align vNICs with the most direct PCIe path to the CPU or memory.

Exam trap

Cisco often tests the misconception that Round-Robin provides load balancing for low latency, but the trap here is that Round-Robin optimizes for bandwidth distribution, not latency minimization, and the Assigned policy is the only one that guarantees fixed path placement for deterministic performance.

How to eliminate wrong answers

Option B (Any) is wrong because it allows the system to dynamically assign vNICs to any available physical port, which can introduce latency variation and suboptimal traffic distribution. Option C (Default) is wrong because it typically applies a system-defined policy that may not guarantee the deterministic placement required for low-latency workloads. Option D (Round-Robin) is wrong because it distributes vNICs sequentially across ports without considering latency sensitivity, potentially causing mismatched traffic patterns and increased jitter.

Practice this question →
97
MCQmedium

Refer to the exhibit. A UCS B-Series blade shows a failed power supply. The blade is currently running. Which action should the engineer take to replace the power supply without causing service disruption?

A.Replace the power supply only after the blade is isolated from the fabric.
B.Replace the failed power supply in the chassis without affecting the blade.
C.Shut down the blade, replace the power supply, then power on.
D.Replace the failed power supply while the blade remains powered on.
AnswerD

The blade has redundant power supplies; hot-swap is supported.

Why this answer

Option D is correct because UCS B-Series blades use a shared chassis power infrastructure with N+1 redundancy. The failed power supply can be hot-swapped while the blade remains powered on, as the remaining power supplies in the chassis will continue to provide power without interruption. No blade isolation or shutdown is required, as the chassis power subsystem is designed for concurrent maintenance.

Exam trap

Cisco often tests the misconception that a blade must be shut down or isolated before replacing a chassis-level component, but the key is understanding that UCS chassis power supplies are hot-swappable and redundant, so no blade-level action is needed.

How to eliminate wrong answers

Option A is wrong because isolating the blade from the fabric (disconnecting its virtual interfaces) is unnecessary for power supply replacement; the blade's power is independent of fabric connectivity. Option B is wrong because it implies the power supply can be replaced without any effect on the blade, but the correct procedure is to replace it while the blade is powered on, not just 'without affecting the blade' — the phrasing is misleading as the blade remains powered on during replacement. Option C is wrong because shutting down the blade is not required; the chassis power redundancy allows hot-swap of the power supply without powering down any blade.

Practice this question →
98
MCQhard

You manage a UCS domain with two fabric interconnects (FI-A and FI-B) in an cluster. The domain contains 8 blade servers. After a power failure, both FIs come back online, but the cluster experiences a split-brain situation where both FIs claim to be primary. The subordinate FI (FI-B) shows all blades as 'Discovery' state. You suspect configuration mismatch. You have console access to both FIs. Which recovery procedure should be performed to restore a stable cluster?

A.Reset both FIs to factory defaults and reconfigure from backup
B.Boot the FIs into the EFI shell and clear the flash
C.Perform a stateful switchover (SSO) on both FIs
D.On the subordinate FI (FI-B), enter the recovery mode and force a re-initialization, then reset the cluster
AnswerD

Standard UCS split-brain recovery procedure

Why this answer

Option D is correct because in a UCS split-brain scenario where the subordinate FI (FI-B) shows blades in 'Discovery' state due to a configuration mismatch, the proper recovery is to boot FI-B into recovery mode (using the 'recovery' boot option or pressing Ctrl+R at the appropriate prompt) and force a re-initialization, which resets its configuration to match the primary FI (FI-A). After re-initialization, resetting the cluster (via the 'cluster reset' command or equivalent) re-establishes the primary-subordinate relationship and synchronizes the configuration, restoring stable operation without affecting the primary FI's data or requiring a full factory reset.

Exam trap

Cisco often tests the misconception that a split-brain scenario requires a full factory reset or flash clearing, when in fact the targeted recovery of the subordinate FI via recovery mode and cluster reset is the correct, less destructive procedure.

How to eliminate wrong answers

Option A is wrong because resetting both FIs to factory defaults is overly destructive and unnecessary; it would lose all configuration on the primary FI (FI-A) and require a full backup restore, whereas the issue is isolated to the subordinate FI's configuration mismatch. Option B is wrong because booting into the EFI shell and clearing the flash is a low-level hardware recovery method typically used for unbootable FIs or firmware corruption, not for resolving a split-brain cluster state caused by configuration mismatch; it would erase all firmware and configuration, requiring a complete reimage. Option C is wrong because performing a stateful switchover (SSO) on both FIs is designed for planned maintenance or failover in a stable cluster, not for recovery from a split-brain scenario; SSO assumes both FIs are synchronized and operational, which they are not in this case.

Practice this question →
99
MCQmedium

A UCS B-Series blade server (blade 5) has been running a database application for months. Recently, the storage team upgraded the SAN firmware. Since then, the blade experiences intermittent 'SCSI command timeout' errors in the system logs. The application performance degrades periodically. You check the UCS Manager performance data and see that the vHBA statistics show a high number of 'Link Reset' events. The storage array logs show no errors. The fibre channel cables are new. Which step should you take to resolve the issue?

A.Delete and recreate the vHBA in the service profile
B.Replace the fibre channel cables between the IOM and storage
C.Update the HBA firmware on the blade to match the SAN compatibility matrix
D.Rezone the SAN fabric to use a different target port
AnswerC

Firmware mismatch after SAN upgrade is a common cause

Why this answer

Option C is correct because the SAN firmware upgrade likely introduced a change in the Fibre Channel protocol behavior (e.g., link initialization or error recovery) that is incompatible with the current HBA firmware on the blade. The high 'Link Reset' events indicate that the vHBA is repeatedly reinitializing the link, which directly causes SCSI command timeouts. Updating the HBA firmware to match the SAN compatibility matrix ensures the HBA can properly negotiate and interoperate with the upgraded SAN fabric, resolving the intermittent timeouts.

Exam trap

The trap here is that candidates assume physical cabling or zoning is the cause of link resets, but Cisco often tests the concept that firmware mismatches after a SAN upgrade can cause intermittent FC link issues without any physical layer faults.

How to eliminate wrong answers

Option A is wrong because deleting and recreating the vHBA would not address the underlying firmware incompatibility; it would only reset the vHBA configuration, which would likely result in the same link reset behavior. Option B is wrong because the fibre channel cables are new and the storage array logs show no errors, indicating the physical layer is not the issue. Option D is wrong because rezoning the SAN fabric to use a different target port would not fix the HBA-to-switch link reset problem; the issue is at the HBA level, not the zoning or target port selection.

Practice this question →
100
MCQmedium

A data center engineer notices that a UCS B-Series blade server is failing to boot from a SAN LUN that is correctly mapped to the server's WWPN. The SAN switch shows that the LUN is accessible and the zone is configured correctly. The UCS Manager shows the server's vNIC is associated with a vHBA that has the correct WWPN, but the server's BIOS does not list the Fibre Channel boot target. Which configuration is most likely missing?

A.The SAN connectivity policy is missing the Fibre Channel uplink pinning.
B.The vNIC/vHBA placement policy is incorrectly set to 'Express' mode.
C.A QoS policy is not applied to the vHBA.
D.The boot policy is not defined or not attached to the service profile.
AnswerD

UCS B-Series requires a boot policy to specify the boot order and target LUN.

Why this answer

The boot policy defines the boot order and parameters (such as the SAN LUN target WWPN and LUN ID) for the server. If the boot policy is not defined or not attached to the service profile, the UCS Manager will not program the BIOS with the Fibre Channel boot target information, even though the SAN zoning and vHBA WWPN are correct. Without this policy, the server's BIOS has no instruction to attempt a SAN boot, resulting in the failure described.

Exam trap

Cisco often tests the distinction between SAN connectivity (zoning, WWPN) and the boot policy configuration, trapping candidates who assume that correct zoning and vHBA setup alone are sufficient for SAN boot.

How to eliminate wrong answers

Option A is wrong because the SAN connectivity policy with Fibre Channel uplink pinning controls how uplinks are mapped to fabric interconnects for load balancing or failover, not the boot target configuration. Option B is wrong because the vNIC/vHBA placement policy set to 'Express' mode affects how virtual interfaces are placed on the mezzanine cards or adapters, but does not prevent the BIOS from seeing a Fibre Channel boot target. Option C is wrong because a QoS policy applied to a vHBA manages traffic prioritization and bandwidth limits, not the presence or absence of a boot LUN in the BIOS boot list.

Practice this question →
101
MCQhard

Refer to the exhibit. An engineer notices intermittent packet loss on interface Ethernet 1/1 of the Fabric Interconnect. Based on the transceiver statistics shown, which condition is the most likely cause?

A.The receive power is below the low warning threshold.
B.The supply voltage is out of range.
C.The transmit power is too low.
D.The transceiver temperature is too high.
AnswerA

-16.2 dBm is below Low Warning of -15.0 dBm, indicating potential cable or connector issue.

Why this answer

The exhibit shows that the receive power is -16.3 dBm, which is below the low warning threshold of -13.3 dBm. This indicates the incoming optical signal is too weak, causing intermittent packet loss due to bit errors or link flaps. The transceiver statistics confirm that the receive power is the only parameter breaching its threshold, making it the most likely cause.

Exam trap

Cisco often tests the distinction between warning and alarm thresholds, and candidates mistakenly assume any parameter outside a threshold causes the issue, but here only the receive power is below its warning threshold, while the other values are within normal ranges.

How to eliminate wrong answers

Option B is wrong because the supply voltage is 3.29 V, which is within the normal operating range (typically 3.1 V to 3.5 V for SFP+ optics), so it is not out of range. Option C is wrong because the transmit power is -2.4 dBm, which is above the low warning threshold of -5.3 dBm, indicating the transmitter is functioning correctly. Option D is wrong because the transceiver temperature is 42.5°C, which is well below the high warning threshold of 75°C, so overheating is not an issue.

Practice this question →
102
Drag & Dropmedium

Order the steps for troubleshooting a Fibre Channel link that is not coming up.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order

Why this order

Troubleshooting FC link starts with physical, then interface, VSAN/zoning, FLOGI, and logs.

Practice this question →
103
MCQeasy

A financial services company operates a Cisco UCS 6454 Fabric Interconnect cluster with two FI-A and FI-B, connected to multiple UCS B-Series blades. The environment uses UCS Manager 4.2(1a). Recently, the company migrated to a new storage array connected via Fibre Channel. The storage team configured 8 virtual SANs (VSANs) and created a new VSAN 400 for a critical application. After the migration, the application server running on a UCS blade cannot discover the storage LUNs. The server's vHBA is configured correctly with the proper WWPN, and the zone set is active on the SAN switches. The engineer checks the UCS Manager and sees that the vHBA is down. Which action should the engineer take to resolve the issue?

A.Upgrade UCS Manager to the latest version to fix a known bug.
B.Verify that the uplink Fibre Channel ports on the fabric interconnects are configured to allow VSAN 400.
C.Reboot the server blade to force re-discovery of the storage.
D.Recreate the vHBA in the service profile with a different WWPN.
AnswerB

The FC uplink ports must be members of the VSAN for traffic to pass.

Why this answer

Option B is correct because the vHBA being down indicates no Fibre Channel connectivity. The most likely cause is that the FC uplink ports on the fabric interconnects are not configured to allow VSAN 400. Option A is not appropriate because rebooting the server does not address the underlying connectivity issue.

Option C is unnecessary and would require re-zoning. Option D is an escalation step not justified without evidence of a bug.

Practice this question →
104
MCQhard

Refer to the exhibit. A UCS domain shows a 'Major' NVRAM backup failure alarm in Intersight. What is the best immediate action?

A.Attempt a manual NVRAM configuration backup from the primary Fabric Interconnect to the secondary.
B.Perform a factory reset on both Fabric Interconnects.
C.Reboot the primary Fabric Interconnect.
D.Reclaim the UCS domain from Intersight and register again.
AnswerA

Manual backup can jumpstart the failed backup process and clear the alarm.

Why this answer

A 'Major' NVRAM backup failure alarm in Intersight indicates that the automatic periodic backup of the UCS domain's configuration from the primary Fabric Interconnect (FI) to the secondary FI has failed. The best immediate action is to attempt a manual NVRAM configuration backup from the primary FI to the secondary, as this directly addresses the backup failure without disrupting domain operations or requiring re-registration.

Exam trap

Cisco often tests the distinction between a configuration backup failure and a hardware or connectivity failure, leading candidates to choose disruptive actions like rebooting or factory resetting when a simple manual backup retry is the correct first step.

How to eliminate wrong answers

Option B is wrong because performing a factory reset on both Fabric Interconnects is a drastic, destructive action that would erase all configuration and cause significant downtime, which is unnecessary for a backup failure that can be resolved manually. Option C is wrong because rebooting the primary Fabric Interconnect would disrupt traffic and may not resolve the backup failure; the issue is likely with the backup process or connectivity, not the FI's operational state. Option D is wrong because reclaiming the UCS domain from Intersight and registering again would remove the domain from management and require re-establishing connectivity, which is an overreaction for a backup failure that can be addressed with a manual backup attempt.

Practice this question →
← PreviousPage 2 of 2 · 104 questions total

Ready to test yourself?

Try a timed practice session using only Dc Compute questions.

Start 20-question session