Q1. A user reports that their workstation's performance has degraded significantly over the past week. Applications launch slowly, and file transfers are taking an unusually long time. The workstation is a desktop, approximately three years old. You have confirmed that there are no active malware infections and that the operating system is fully patched. The Task Manager shows normal CPU and RAM utilization.
-
Check the read/write speeds of the primary storage device. ✓ Correct
-
Replace the network interface card (NIC) with a faster model.
-
Upgrade the CPU to a newer, higher-clocked processor.
-
Install an additional 8GB of RAM.
Why: The symptoms described (slow application launches, slow file transfers) strongly indicate a bottleneck in the storage subsystem, especially since CPU and RAM utilization are normal and malware is ruled out. Checking the read/write speeds of the primary storage device (HDD or SSD) is the most direct way to diagnose this. Replacing the NIC is irrelevant if local file operations are slow. Upgrading the CPU or adding RAM would only help if those components were the bottleneck, which is not indicated by normal utilization levels.
Q2. A user reports that their computer is randomly freezing, requiring a hard reboot. This started occurring after they installed a new, high-end gaming graphics card. The system was stable before the installation. All drivers for the new card have been installed from the manufacturer's website, and the operating system is up to date. The power supply unit (PSU) is rated at 650W, and the manufacturer's recommended PSU for the graphics card is 600W.
-
Check the PCIe slot for physical damage.
-
Verify that the graphics card is receiving adequate power through its auxiliary connectors. ✓ Correct
-
Reduce the resolution and graphical settings in the games the user plays.
-
Underclock the graphics card using the manufacturer's utility.
Why: The symptoms appeared immediately after installing a new, power-hungry graphics card, and the system was stable before. While the PSU wattage meets the minimum recommendation, high-end cards can have transient power spikes. The MOST likely cause is insufficient or unstable power delivery to the graphics card itself, often through dedicated PCIe power connectors. Checking these connections ensures the card is getting the power it needs. Inspecting the PCIe slot is a good step, but less probable than a power delivery issue. Reducing game settings or underclocking are workarounds, not troubleshooting steps to identify the root cause of instability, which points to a potential hardware resource (power) issue.
Q3. A user is experiencing extreme lag and stuttering when running virtual machines (VMs) on their workstation, even with only one VM active. The workstation has 32GB of RAM and a modern multi-core CPU. The VMs are stored on a separate, fast SSD. The host operating system is Windows 10 Pro. You have confirmed that the host OS is not experiencing performance issues when not running VMs.
-
Increase the page file size on the host operating system.
-
Check the virtual machine's network configuration for conflicts.
-
Allocate more CPU cores to the virtual machine.
-
Ensure virtualization technology (VT-x/AMD-V) is enabled in the BIOS/UEFI. ✓ Correct
Why: Modern virtualization software relies heavily on hardware-assisted virtualization features (Intel VT-x or AMD-V) for optimal performance. If this feature is disabled in the BIOS/UEFI, the hypervisor will resort to software-based emulation, leading to severe performance degradation. While increasing the page file or allocating more CPU cores might offer marginal improvements, they won't overcome the fundamental performance penalty of lacking hardware virtualization. Checking VM network configuration is unlikely to cause system-wide VM performance issues unless there's a specific network-bound application within the VM, which isn't implied here.
Q4. A user is experiencing intermittent internet connectivity drops while working from home. They are using a laptop connected via Wi-Fi to their home router. Other devices on the same network do not seem to be experiencing the same issues. The user has already tried restarting the router and the laptop.
-
Replace the router's firmware with a custom third-party version.
-
Test the laptop's connectivity using a wired Ethernet connection. ✓ Correct
-
Manually assign a static IP address to the laptop.
-
Change the Wi-Fi channel on the router.
Why: Since other devices on the network are functioning correctly, the issue is likely isolated to the user's laptop or its specific wireless connection. The most efficient way to differentiate between a Wi-Fi specific problem on the laptop and a broader connectivity issue is to test with a wired Ethernet connection. If the wired connection is stable, the problem is confirmed to be with the laptop's Wi-Fi adapter, drivers, or its connection to the router. Replacing firmware or changing Wi-Fi channels address potential router issues, which are less likely given other devices are fine. Manually assigning a static IP is unlikely to resolve intermittent drops unless it's related to DHCP conflicts, which is less common for intermittent drops.
Q5. A user reports that their monitor occasionally displays strange artifacts, such as flickering lines and incorrect colors. They are using a DisplayPort connection to a desktop computer. The issue is intermittent and seems to happen more frequently when playing graphics-intensive games. The monitor itself has been tested and works correctly when connected to another computer.
-
Replace the DisplayPort cable with a certified High Speed cable. ✓ Correct
-
Update the audio drivers on the computer.
-
Install a new CMOS battery on the motherboard.
-
Check the power supply wattage is sufficient for the graphics card.
Why: Artifacts like flickering lines and incorrect colors, especially during graphics-intensive tasks and when using DisplayPort, strongly point to a signal integrity issue with the cable. A faulty, low-quality, or damaged DisplayPort cable can struggle to transmit the high bandwidth required, leading to intermittent visual anomalies. Testing the monitor on another computer rules out the monitor itself. While ensuring sufficient power for the graphics card is crucial for stability, it typically manifests as system crashes or shutdowns, not intermittent visual artifacts. Updating audio drivers and replacing the CMOS battery are irrelevant to video signal transmission issues.
Q6. A user is complaining that their computer takes several minutes to boot up, and applications frequently become unresponsive shortly after starting. They mention that the system has been running slower for about a month. You have confirmed there is no malware, all system drivers are up to date, and there is sufficient free space on the hard drive. The system's BIOS reports the hard drive as detected and healthy.
-
Check the S.M.A.R.T. status of the hard drive. ✓ Correct
-
Perform a clean installation of the operating system.
-
Defragment the hard drive.
-
Increase the amount of RAM installed in the computer.
Why: Slow boot times and unresponsiveness in applications, especially after a period of degradation, often indicate a failing hard drive, even if it's detected by the BIOS. S.M.A.R.T. (Self-Monitoring, Analysis, and Reporting Technology) status provides detailed health metrics that can predict imminent drive failure. While defragmenting might offer a temporary boost on older HDDs, it won't fix underlying hardware issues. A clean OS installation is a drastic step and should only be considered after confirming the hardware is sound. Increasing RAM might help with multitasking or memory-intensive applications, but it's less likely to be the primary cause of slow boot and general unresponsiveness if storage is the bottleneck.
Q7. A workstation connected via Ethernet is intermittently losing network connectivity. When connectivity is lost, the network adapter status shows 'Network cable unplugged.' However, the user confirms the cable is securely connected at both ends. What is the FIRST troubleshooting step to isolate the issue?
-
Replace the network interface card (NIC)
-
Test the network cable with a cable tester ✓ Correct
-
Reinstall the network adapter driver
-
Check the IP address configuration on the workstation
Why: The symptom 'Network cable unplugged' reported by the OS, despite the user's confirmation of secure connections, strongly suggests a potential issue with the physical cable itself. Testing the cable with a cable tester is the most direct and efficient FIRST step to rule out or confirm a faulty cable. Replacing the NIC, reinstalling the driver, or checking IP configuration are later steps if the cable is confirmed to be good, as they address issues beyond the physical layer indicated by the 'cable unplugged' status.
Q8. A server experiencing frequent hard drive failures has been equipped with new, identical hard drives. After configuring them in a RAID 1 array and initiating the rebuild process, the rebuild fails intermittently. System logs show repeated 'I/O error' messages originating from the RAID controller. What is the MOST likely cause?
-
Faulty RAID controller ✓ Correct
-
Incorrect RAID level configuration
-
Driver conflict for the storage controller
-
Insufficient power supply to the hard drives
Why: Repeated I/O errors originating from the RAID controller during a rebuild, especially after replacing drives, strongly indicates a problem with the controller itself. The controller is responsible for managing the drives and the RAID array operations. While insufficient power or driver conflicts could cause issues, the specific log messages pointing to the controller's I/O operations make it the MOST likely culprit. Incorrect RAID level configuration would typically prevent the array from being built or functioning at all, rather than causing intermittent rebuild failures with I/O errors.
Q9. A user reports that their workstation is making a loud, rhythmic clicking noise during startup, and the operating system fails to load, displaying a 'Boot Device Not Found' error. The computer is a standard desktop with a single SATA hard drive. What is the MOST likely cause of this issue?
-
Failing hard disk drive (HDD) ✓ Correct
-
Loose RAM module
-
Overheating CPU
-
Corrupted operating system boot sector
Why: The rhythmic clicking noise combined with a 'Boot Device Not Found' error is a classic symptom of a failing mechanical hard disk drive (HDD). The clicking often indicates issues with the read/write heads or platter. While a loose RAM module can cause boot failures, it typically presents with POST beep codes or no display, not clicking. An overheating CPU usually leads to system shutdowns or throttling, and a corrupted boot sector would likely result in a different error message or a boot loop, without the distinct mechanical clicking sound.
Q10. A technician replaces a faulty stick of RAM in a workstation. On the next boot, the system powers on, fans spin, but there is no video output and the motherboard emits a repeating pattern of one long beep followed by two short beeps. The technician confirms the monitor and cable are good on another machine. What is the MOST likely cause?
-
The newly seated RAM module is not fully inserted or is incompatible ✓ Correct
-
The CPU has overheated and thermal throttling has disabled video
-
The power supply cannot deliver enough wattage to the GPU
-
The CMOS battery has died, clearing the boot device order
Why: A repeating beep pattern immediately after a RAM swap, with power but no POST video, points directly to a memory-related POST failure—commonly a module not fully seated or incompatible, which the beep code signals. A CPU overheat would typically allow POST to complete before thermal shutdown and would not produce a memory beep code. Insufficient PSU wattage generally causes reboots or failure to power on, not a specific memory beep pattern. A dead CMOS battery causes date/time resets and configuration loss but still permits POST with video, so it does not fit this evidence.