CompTIA A+ Core 1 questions often present several technically possible answers and ask which one best fits the user’s constraint. The current 220-1201 V15 blueprint rewards this kind of judgment because 28% of the exam is Hardware and Network Troubleshooting and much of the remaining material is scenario based. A support technician must choose a compatible, safe, proportionate fix rather than the most expensive or feature-rich option.
The scenarios below stay inside Core 1’s current Mobile Devices, Networking, Hardware, Virtualization and Cloud Computing, and Troubleshooting domains. They are study examples, not claims about live exam items.
Scenario one: a desktop needs faster storage but has no free SATA bay
If the motherboard has an available M.2 slot that supports NVMe, an M.2 NVMe SSD can improve storage performance without requiring a 2.5-inch bay. If the slot supports only SATA M.2, buying a PCIe/NVMe drive may be physically similar but electrically incompatible.
The decision should begin with motherboard support and interface, not with the highest advertised drive speed.
Scenario two: a laptop is slow but memory is already sufficient
Check storage, CPU/thermal behavior, startup load, and whether the system uses a mechanical hard drive before adding more RAM. A memory upgrade does little if the actual bottleneck is a failing HDD, thermal throttling, or background software.
Core 1 troubleshooting works best when one observed symptom leads to evidence rather than a favorite upgrade.
Scenario three: a user can connect to Wi-Fi but websites fail by name
Verify IP address, gateway, and DNS. If the client can reach an IP address but not a hostname, DNS is a stronger suspect than wireless authentication. If the client has an APIPA address, DHCP failed earlier in the path.
A basic IPv4 and subnetting model makes these distinctions much easier under exam pressure.
Scenario four: a home office needs reliable video calls
Choose the least congested supported Wi-Fi band and channel, place the access point appropriately, and prefer wired Ethernet for the most critical workstation when practical. Increasing internet speed will not fix local interference or a weak signal.
Trade-offs include range, throughput, wall penetration, channel congestion, and device capability across 2.4, 5, and 6 GHz.
Scenario five: a small business printer is reachable but jobs never print
Check the print queue, driver, selected printer, print-server/share state, and permissions before opening the printer for mechanical service. If the queue clears and the device reports a paper jam or consumable problem, move to the hardware path.
Printer support is a good example of separating software/network state from physical output mechanisms.
Scenario six: a workstation randomly powers off during gaming
Investigate temperature, PSU capacity/connectors, GPU/CPU load, fans, heatsinks, and power delivery. Replacing the motherboard first is premature if the shutdown occurs only under sustained load.
A thermal or power constraint can imitate a component defect, so check evidence such as temperature and event timing before swapping expensive parts.
Scenario seven: a company wants isolated test software on one PC
A local virtual machine or sandbox may be a better fit than buying dedicated hardware. If the requirement is lightweight application isolation, containers may be appropriate; if a full guest OS is needed, a VM is the stronger model.
A virtualization and cloud foundation helps candidates distinguish local virtualization from remote cloud consumption and VDI.
Scenario eight: a phone battery is visibly swollen
Stop normal use and follow safe handling or service procedures. Do not keep charging, compress the battery, or continue troubleshooting as though it were an ordinary runtime problem.
Safety is a real support constraint. The correct technical action can be to stop work, isolate the risk, and escalate.
Scenario nine: a new graphics card fits the PCIe slot but the PC is unstable
Check PSU wattage and required auxiliary power connectors, case clearance, cooling, firmware, and driver support. Physical slot compatibility is necessary but not sufficient.
Hardware decisions often involve several compatibility layers at once: electrical, mechanical, thermal, firmware, and software.
Scenario ten: a cloud app is slow but local internet tests look healthy
Separate local endpoint/network evidence from remote service behavior. Check whether other users are affected, whether the SaaS provider reports an outage, and whether latency appears only for one application.
Scenario eleven: a desktop powers on, fans spin, but there is no display after a memory upgrade. Recheck DIMM seating, supported memory type, recommended slot population, and whether the system completes POST. If the old memory restores operation, compatibility or installation is more likely than a failed monitor. The technician should isolate the change that immediately preceded the symptom.
Scenario twelve: a user asks for a RAID level with both redundancy and better read performance for four drives. RAID 10 may fit better than RAID 0 because it preserves redundancy, while RAID 5 may trade write behavior and fault tolerance differently. The correct choice depends on usable capacity, failure tolerance, and performance—not a rule that one RAID level is always “best.”
Scenario thirteen: a new wireless access point supports 6 GHz, but many users have older clients. A 6 GHz-only deployment would strand unsupported devices. A mixed design may need 2.4/5 GHz alongside 6 GHz. Compatibility with client radios matters as much as the newest wireless standard.
Scenario fourteen: a user cannot connect a USB-C monitor even though the cable fits. Confirm whether the laptop’s USB-C port supports DisplayPort alternate mode or Thunderbolt/video output. Connector shape alone does not guarantee data, charging, and video capabilities. This is a classic Core 1 trade-off between physical fit and protocol capability.
Scenario fifteen: a small office wants file sharing, backups, and remote collaboration. A local NAS may give fast LAN access and ownership, while cloud storage may simplify remote access and synchronization. The correct support recommendation depends on internet reliability, collaboration need, data sensitivity, availability, and management effort.
Scenario sixteen: a printer produces faint output. For a laser printer, toner level, drum, transfer, fuser, and environmental conditions may matter. For an inkjet printer, cartridge level, printhead clogging, or alignment is more likely. The printer technology determines which maintenance path is appropriate.
Scenario seventeen: a laptop connects through a dock but loses Ethernet whenever the dock is disconnected. That behavior may be expected rather than a fault. The technician should distinguish a device design limitation from a malfunction and offer the user an alternative connection method if mobility requires it.
Scenario eighteen: an application needs more CPU but the host is a VM with constrained virtual resources. Adding physical RAM to the workstation may not help if the VM is capped at one vCPU. Check the hypervisor allocation and host headroom before recommending physical upgrades.
Scenario nineteen: a user reports “the network drops every few minutes,” and switch logs show port flapping. Inspect cable, connector, NIC, switch port, power-saving behavior, and physical damage before changing DNS or IP configuration. Port flapping is a link-layer symptom, so higher-layer configuration is the wrong starting point.
Scenario twenty: a laptop charges slowly through USB-C. Check charger wattage, cable rating, port capability, docking-station power budget, and whether the system is under heavy load. USB-C is a connector family with several power/data capabilities, so “USB-C charger” does not guarantee full-speed charging.
Scenario twenty-one: a user wants an external SSD for backups and asks for the fastest interface. The technician should consider the drive, enclosure, host port, cable, and backup workload. Buying a fast NVMe enclosure provides little benefit if the host only supports a slower USB mode.
Scenario twenty-two: a SOHO router’s DHCP pool is exhausted. Expanding the scope may solve the immediate symptom, but first check for stale leases, unexpected devices, or an overly small design. The trade-off is between quick capacity relief and understanding whether unauthorized or misconfigured clients are consuming addresses.
Scenario twenty-three: a remote worker has excellent internet speed but poor video-call quality at certain times. Check jitter, packet loss, Wi-Fi congestion, competing uploads, and router placement. Raw bandwidth is only one network-quality measure. Real-time applications are sensitive to delay variation and loss.
Scenario twenty-four: a phone’s cellular data works but corporate applications fail. The problem may be MDM policy, VPN, identity, certificate, or application configuration rather than the cellular radio. Mobile support increasingly involves managed-service dependencies, not just hardware.
Across Core 1 scenarios, a useful rule is to prefer the smallest evidence-driven change that satisfies the requirement safely. Compatibility, user impact, recoverability, cost, and safety are constraints. The exam’s strongest distractors are often technically possible actions that are broader, riskier, or aimed at the wrong layer.
Scenario twenty-five: a user needs a second display but the laptop has one HDMI port already in use. A USB-C dock or DisplayPort-capable USB-C adapter may be appropriate if the port supports video. A cheap USB hub without display capability will not solve the problem. The technician should match the expansion device to the signal requirement rather than connector appearance.
Scenario twenty-six: a printer is shared through a print server, but only one user cannot print. Check that user’s queue, driver, permissions, and network reachability before restarting the printer for everyone. A single-user blast radius strongly suggests client or authorization context rather than a mechanical fault affecting all users.
Scenario twenty-seven: an SSD reports S.M.A.R.T. warnings but the system still boots. Back up important data promptly and plan replacement. Waiting for total failure creates unnecessary risk, while attempting unrelated performance tuning ignores the health evidence already available.
Scenario twenty-eight: a desktop cannot join the office network after being moved to a new desk. Check link light, patch cable, wall jack, switch port/VLAN, and DHCP before reconfiguring the NIC manually. The physical move is the strongest clue, so start with the changed layer.
Scenario twenty-nine: a virtual machine cannot start because host memory is exhausted. Reducing guest allocation, shutting down unused VMs, or adding host RAM can solve the resource constraint. Changing the guest OS network settings does not address the hypervisor scheduling problem.
Scenario thirty: a user requests RAID 0 because they heard it is fastest, but the workstation stores irreplaceable project data. The technician should explain the lack of redundancy and recommend a design that balances performance with recoverability. The user’s stated preference is not always the same as the actual requirement.
These trade-offs illustrate the practical nature of A+. Core 1 rarely rewards “maximum specification” thinking. The best support answer normally satisfies compatibility, user need, safety, availability, cost, and the evidence available from the symptom. That mindset is more transferable than memorizing one recommended part for every category.
The current A+ 1200-series update reflects modern support environments where a user’s task can depend on local hardware, home networking, identity, and remote cloud services simultaneously. Good Core 1 judgment is choosing the layer that actually owns the constraint.