server-hardware-installation-management practice questions

The replacement disk is assigned a different drive letter in the OS

Why it fails: Drive letter assignment is an OS-level configuration and does not affect the RAID array status at the controller level.

The RAID controller firmware is outdated

Why it fails: Outdated firmware would likely cause more general issues, not specifically a single replacement disk failure after rebuild.

The replacement disk is missing a partition table

Why it fails: RAID arrays operate at the disk level, not partition level. A missing partition table would not cause the array to stay degraded.

The power supply voltage to the processor

Why it fails: Incorrect voltage could cause instability but is less common than fan failure for temperature warnings.

The ambient temperature of the data center

Why it fails: Ambient temperature affects all components, but the warning is specific to processor 1, pointing to a localized cooling issue.

The thermal paste between the heatsink and processor

Why it fails: While poor thermal paste can cause high temperatures, a sudden threshold exceedance is more likely due to fan failure.

Add two 8 GB DDR4-2400 modules to channel B

Why it fails: Incorrect. Mismatched speeds (2400 vs 2666) will cause the system to run at the lower speed, reducing performance.

Add one 8 GB DDR4-2666 module to DIMM_B1

Why it fails: Incorrect. While it adds capacity, the single module on channel B will not enable dual-channel operation; performance will be single-channel.

Add one 16 GB DDR4-2666 module to DIMM_B1

Why it fails: Incorrect. This would create an imbalance in capacity between channels, potentially reducing performance to single-channel mode.

The ambient temperature sensor in the data center is reporting incorrectly and the actual temperature is higher.

Why it fails: Handheld thermometer confirms 20°C; other servers in same rack are fine, so ambient is normal.

The internal fans are not operating at full speed due to a failed fan controller.

Why it fails: Fans are verified spinning, and a fan controller failure would likely cause constant overheating or sensor errors, not just peak hours.

The file server's power supply is failing and causing voltage drops that affect fan performance.

Why it fails: A failing PSU typically causes power-related errors or system instability, not specific CPU thermal events; fans are verified operational.

Disable ECC in the firmware to prevent the module from reporting errors.

Why it fails: Disabling ECC would mask the error but would still leave the faulty module in place, increasing the risk of data corruption.

Reseat the DIMM in slot B2 and run a memory diagnostic test.

Why it fails: Reseating may temporarily fix a poor connection, but ECC errors usually indicate a failing DIMM that should be replaced.

Increase the DRAM voltage slightly in the BIOS/UEFI to improve stability.

Why it fails: Overvolting can damage components and is not a standard remediation for ECC errors; besides, the modules are all identical and within spec.

The power supplies were not hot‑swappable

Why it fails: Even non‑hot‑swappable PSUs should continue to power the server if the second unit fails; hot‑swap only means you can replace without shutting down.

The failed power supply had a higher wattage rating than the remaining one

Why it fails: If both had been running, a minor wattage difference typically does not cause immediate shutdown.

The power supplies were from different manufacturers

Why it fails: As long as the power supplies meet the same electrical and mechanical specifications, different vendors rarely cause such behavior.

Test the system with a known-good CPU.

Why it fails: A green PSU LED confirms standby voltage only, not that the power-good signal or main rails reach the motherboard; a failed CPU would not stop fans spinning entirely. Swapping the CPU suits diagnosing POST failures with fan activity, not a dead board. Reseating power connectors or testing a known-good PSU addresses this scenario.

Reset the server's configuration via the CMOS jumper.

Why it fails: A power outage might reset CMOS, but the symptom of no power at all (no fan spin) points to a physical power issue, not a configuration problem.

Replace the power supply.

Why it fails: A green PSU LED confirms standby voltage is present, so the fault lies downstream — likely the motherboard or power button circuit. Replacing the PSU addresses the one component already indicating normal operation. Swapping a PSU is the right step when its LED is dark or amber, or when it fails a multimeter voltage check under load.

Rebuilding

Why it fails: Rebuilding status would show a progress percentage and a 'recovering' state. The output shows no such activity.

Healthy

Why it fails: A healthy array would show all devices active and no 'degraded' state. Here, a drive is missing.

Failed

Why it fails: A failed array would have a state of 'failed' and insufficient active devices to remain operational. This array is still functional.

Run a full backup and then replace the drive

Why it fails: While backups are vital, the immediate priority is to replace the failing drive to maintain array redundancy.

Rebuild the array to include the hot spare

Why it fails: A hot spare is only automatically integrated upon actual drive failure; you cannot force a rebuild using a hot spare for a drive that is still present but predicting failure.

Continue monitoring; the drive is still functional

Why it fails: The predictive failure indicates imminent failure; waiting could lead to data loss or extended downtime.

Update the NIC drivers to the latest version

Why it fails: Driver updates are important for stability but are less likely to be the direct cause of uneven LACP throughput if the team is functional.

Verify the MTU settings on the NICs and switch

Why it fails: MTU mismatches usually cause packet fragmentation or connectivity issues, not specifically a 2Gbps limitation on a 4Gbps team.

Check for Spanning Tree Protocol blockages

Why it fails: Spanning Tree would block individual ports, preventing them from participating in the LAG, which would reduce total available links, not simply limit throughput per link.

Reseat all memory modules and clean the DIMM slots

Why it fails: Reseating is a basic troubleshooting step, but multiple passes of MemTest86+ with no errors suggest the electrical connections are sound.

Replace the hard drives with solid-state drives (SSDs)

Why it fails: SSDs would improve I/O performance and reduce power draw slightly, but they would not correct the underlying power instability that is causing ECC memory errors.

Replace the motherboard, as the memory controller is likely failing

Why it fails: No evidence points to a motherboard memory controller failure; MemTest86+ passes, and corrected errors can be caused by power fluctuations.

Update the server's firmware and device drivers to the latest versions.

Why it fails: MCE errors are typically hardware faults. While firmware/driver updates are good practice, they are unlikely to resolve a hardware MCE and delay the actual repair.

Disable the faulty CPU core in the BIOS and continue monitoring.

Why it fails: Disabling a core is a workaround, not a fix. It reduces processing capacity and does not address the underlying hardware fault that could affect other components.

Replace the CPU with a known-good unit immediately.

Why it fails: Without diagnostic confirmation, you may replace a functional CPU while ignoring a motherboard or socket issue, leading to continued errors.

Replace one drive at a time with a larger SAS drive and allow the array to rebuild.

Why it fails: Replacing drives one at a time in a RAID 1 array with larger drives does not increase capacity because the array size is limited by the smallest drive in the mirror. It also introduces risk during rebuilds and does not utilize the empty bays for expansion. This approach is suitable for replacing failed drives, not for capacity expansion.

Back up the data, delete the existing array, install four new larger drives, and create a RAID 5 array.

Why it fails: This approach requires significant downtime and does not leverage the existing drives. While it achieves capacity and redundancy, it is more disruptive and costly than an online migration. The scenario specifies minimizing downtime, so a full rebuild with new drives is unnecessary when the existing drives can be reused.

Add two additional SAS drives and create a separate RAID 1 array, then span the volumes.

Why it fails: Creating a separate RAID 1 array and spanning volumes does not provide a single logical volume with combined capacity; spanning (or JBOD) concatenates arrays but offers no redundancy across the span. If one array fails, data across the span may be lost. This does not meet the requirement for increased capacity with maintained redundancy in a single array.

The power supplies are operating in a load-balanced or active/active configuration.

Why it fails: While load balancing can distribute power draw, it is not a requirement for stable operation. Many servers run in active/passive mode where one supply provides all power and the other is standby. The intermittent reboots are more likely due to power insufficiency or faulty supplies, not the load-balancing mode.

The power supplies are connected to the same PDU for load balancing.

Why it fails: Connecting both power supplies to the same PDU defeats redundancy; a PDU failure would take down both supplies. Best practice is to connect each supply to a separate PDU on different circuits. This configuration does not address intermittent reboots; it only ensures power diversity, which is already implied by the scenario.

The power supply firmware is up to date.

Why it fails: Firmware updates can resolve bugs, but intermittent reboots under heavy load are more commonly caused by hardware power issues such as insufficient wattage or faulty connections. Firmware is a secondary consideration after verifying power capacity and physical connections.

Perform a full backup of the database.

Why it fails: While backups are important, the server is running a critical database and must remain online. The faulty drive is part of a RAID array, so the array is likely still operational and redundant. A backup is a good practice, but the immediate first step is to ensure the replacement drive is compatible and then hot-swap it. Backing up could take time and may not be necessary if the array is healthy.

Power down the server to safely replace the drive.

Why it fails: The server must remain online, so powering down is not an option. Additionally, the drive is hot-swappable, meaning it can be replaced without shutting down the system. Powering down would cause unnecessary downtime and disrupt the critical database, violating the requirement to keep the server online.

Delete the failed drive from the RAID configuration.

Why it fails: Deleting the failed drive from the RAID configuration is not a standard procedure; the controller typically marks the drive as failed and the technician physically replaces it. Deleting the drive logically could damage the array configuration. The correct process is to remove the physical drive and insert a compatible replacement, allowing the controller to rebuild.

Tool-less rails that clip directly into the square holes

Why it fails: Tool-less rails are designed for racks with round holes or specific square-hole profiles that accept the rail's locking mechanism. Since cage nuts are already installed, the square holes are occupied and the tool-less clips will not seat properly, risking an unstable installation.

Tool-less rails after removing the cage nuts

Why it fails: Removing cage nuts is unnecessary and could damage the rack or leave loose hardware. Tool-less rails may still not fit properly because the square holes are designed for cage nuts, and the rails might require specific hole shapes. This adds risk without benefit.

Tooled rails with self-tapping screws directly into the square holes

Why it fails: Self-tapping screws into square holes will not hold securely and can strip the holes, damaging the rack. Cage nuts exist precisely to provide threaded mounting points; bypassing them compromises the installation and may void the rack warranty.

Connect the backplane to the RAID controller using a standard SATA data cable.

Why it fails: A standard SATA data cable carries one lane and cannot aggregate the multiple drive channels that a 2U backplane presents. The backplane connector is physically different from a SATA connector, so the cable would not attach. Using SATA cabling here would fail to expose the NVMe U.2 drives to the RAID controller and is not a supported installation method.

Connect the backplane to the RAID controller using an external SAS cable routed through a PCIe slot bracket.

Why it fails: External SAS cabling is used to attach external disk enclosures, not an internal backplane inside the same chassis. Routing a cable through a PCIe bracket would be unnecessary and would not match the internal backplane connector. The internal backplane must be cabled directly to the controller with the proper internal high-density cable to make all drives visible.

Connect each drive directly to a SATA port on the motherboard.

Why it fails: SATA ports on the motherboard are intended for onboard SATA drives and cannot present NVMe U.2 drives to a RAID controller. The backplane carries multiple drives over a single high-density connector, so individual SATA cables are not used. This approach would leave the RAID controller without drive visibility and defeat the purpose of the add-in card in this 2U chassis.

Power down the server and physically inspect the drive bays for damage

Why it fails: Hot-swap drives are designed to be added without powering down the server, and the scenario implies a production environment where uptime matters. Powering down would cause an outage and is not required for hot-swap installation. While inspection is good practice, it does not protect data integrity as directly as a verified backup, and it is not the first step.

Update the RAID controller firmware to the latest version

Why it fails: Firmware updates are sometimes recommended before adding drives, but without a verified backup, a failed update could leave the server unbootable and the array inaccessible. The scenario states no prior failures, so an unnecessary firmware change introduces risk. A backup must precede any firmware change, making this option premature as the first action.

Run a consistency check on the existing RAID 10 array

Why it fails: A consistency check verifies parity or mirror integrity, but RAID 10 has no parity, and the check does not safeguard against data loss from the physical act of adding drives. It is a maintenance task that can be performed later. The immediate priority before touching hardware is ensuring a recoverable backup, not verifying the current array state.

The memory modules are ECC RDIMMs and the motherboard only supports UDIMMs

Why it fails: If the board only supported unbuffered UDIMMs, registered DIMMs would generally fail to train and the system would usually refuse to boot or report no memory at all. Detecting exactly half the installed capacity points to a slot population issue rather than a registered-versus-unbuffered incompatibility.

The BIOS memory remap feature is disabled, hiding memory above 4GB

Why it fails: Memory remapping affects the region above the 4GB boundary and is relevant to 32-bit address space conflicts, not to a 64GB configuration reporting 32GB. With 64GB installed, the missing 32GB is far too large to be explained by remap settings, which points instead to improperly populated channels.

The RDIMMs are not on the motherboard's qualified vendor list

Why it fails: A memory module that is not on the qualified vendor list may cause instability or fail to train at rated speed, but it would not typically halve the detected capacity or selectively drop two modules. The reported 32GB suggests a population-order or channel-mapping problem rather than a compatibility rejection of all four identical modules.

The availability of an empty memory slot for caching

Why it fails: PCIe SSDs do not require an empty memory slot for caching; they are self-contained. Some caching software may use system memory, but that is not a hardware requirement for the SSD itself. This is not a necessary verification.

The server's RAID controller cache battery status

Why it fails: The RAID controller cache battery is unrelated to the installation of a PCIe SSD. A PCIe SSD is typically used as a direct-attached storage device or for caching, not connected through the RAID controller. Battery status does not affect the SSD installation.

The server's power supply wattage and available power connectors

Why it fails: While power is important, PCIe SSDs typically draw power from the PCIe slot itself and do not require additional power connectors. The power supply wattage is unlikely to be a limiting factor unless the server is already near capacity, but this is not a primary verification for PCIe SSD installation.