Printable referenceCurrent-track reviewIndependent study resource

A+ Core 1 cram sheet and exam-day checklist

A dense final-review reference for hardware, networking, mobile devices, cloud and virtualization, and the troubleshooting decisions that tie the current Core 1 track together.

This is an independently authored study aid, not official CompTIA material. It does not contain recalled, leaked, copied, or live-exam questions and is not affiliated with or endorsed by CompTIA.

Back to A+ Core 1 study guideTake the free practice test
Current reviewed track

Check the maintained exam record before final review.

Exam identity, timing, scoring, domain weighting, recommended experience, and the next review date are rendered from Zeph Tech's certification registry. The quick-reference material below focuses on durable reasoning and troubleshooting patterns rather than copying volatile logistics throughout the page.

Active

  • Exam: 220-1201
  • Version: V15
  • Questions: Maximum of 90 questions
  • Item types: multiple-choice, performance-based
  • Time: 90 minutes
  • Passing score: 675 on a 100–900 scale
  • Recommended background: 12 months of hands-on experience in an IT support specialist job role
  • Renewal: Three-year CompTIA Continuing Education cycle

Last verified: 2026-09-25

Next review: 2026-10-25

Official certification page · Official exam objectives

Published domain weighting

  • Mobile Devices13%
  • Networking23%
  • Hardware25%
  • Virtualization and Cloud Computing11%
  • Hardware and Network Troubleshooting28%

Mobile-device reminders

  • Power first: verify charger, cable, port, negotiated power, battery state, and physical damage before assuming an operating-system problem.
  • Display path: distinguish backlight, panel, cable, graphics output, external display, and software symptoms.
  • Wireless: separate cellular, Wi-Fi, Bluetooth, NFC, hotspot, and synchronization problems by scope and radio state.
  • Management: profiles, permissions, MDM policy, biometrics, remote wipe, and application controls can explain behavior that looks like a hardware fault.
  • Integrated design: mobile components are often not field-replaceable; preserve data and confirm service procedures before disassembly.

Networking mental model

  • Prove the path: link → address → gateway → remote IP → DNS → application.
  • DHCP: supplies host configuration; an unexpected self-assigned address suggests the client did not obtain a usable lease.
  • DNS: translates names; prove raw IP reachability before blaming name resolution.
  • Switching vs routing: switches forward within a local network; routers move traffic between networks.
  • Wireless: signal strength, channel use, interference, band, authentication, roaming, density, and upstream capacity all matter.
  • Ports are clues: associate common services with purpose, but do not treat a port number as proof of the application actually running.

Hardware and storage

  • Compatibility beats appearance: form factor, socket, generation, interface, power, firmware, and motherboard support must align.
  • Memory: use the board manual for supported type, speed, capacity, and slot population; reseating is not a substitute for compatibility.
  • Storage: distinguish interface, protocol, form factor, partitioning, filesystem, firmware visibility, and boot configuration.
  • Power: intermittent resets can involve PSU capacity, connectors, heat, shorts, batteries, or unstable mains power.
  • Cooling: airflow, thermal interface, fan operation, obstruction, and ambient conditions can create performance and stability symptoms.

Virtualization and cloud

  • Layers: guest, hypervisor, host, storage, virtual network, and upstream infrastructure can fail independently.
  • Snapshots are not backups: use tested backups for durable recovery and snapshots for controlled short-term state management.
  • Resource contention: oversubscribed CPU, memory, storage, or network resources can make a healthy guest perform poorly.
  • Cloud responsibility: identify what the provider operates and what the customer still owns—identity, data, configuration, endpoints, and access remain important.
  • VDI: separate endpoint connectivity, authentication, broker/service health, virtual desktop state, and application issues.

Troubleshooting sequence

  • Define the symptom: who, what, when, scope, recent change, error message, and business impact.
  • Start safely: check simple physical and configuration causes before destructive actions.
  • Change one thing: a controlled test is more useful than several simultaneous fixes.
  • Verify the workflow: prove the user's original task works, not merely that the component you touched looks healthy.
  • Document: symptom, evidence, cause when known, action, result, and follow-up.

Hardware troubleshooting: follow symptoms to the failing layer

Core 1 hardware questions become easier when you stop treating components as vocabulary and connect each one to observable symptoms. A system that powers on but does not complete startup has a different fault tree from a system with no power at all. A drive detected by firmware but unavailable to the operating system suggests a different layer from a drive that the firmware cannot see. A laptop that works on an external display but not the internal panel points toward a different set of components than a machine with no video anywhere.

When compatibility is involved, use authoritative specifications rather than assumptions. An M.2 form factor can carry different storage interfaces. Memory modules that physically fit may still differ by generation, voltage, supported speed, rank, or motherboard rules. CPU replacement can require the correct socket, chipset support, firmware, thermal solution, and power delivery. On the exam and in real support, the safest answer often depends on checking the platform documentation before purchasing or forcing a component.

Power and heat deserve special attention because they create intermittent symptoms that resemble software problems. Unexpected shutdowns under load, performance throttling, noisy fans, or instability after hardware upgrades should trigger checks of airflow, dust, fan operation, thermal contact, power capacity, connectors, and environmental conditions. Do not jump straight to reinstalling an operating system when the evidence follows load or temperature.

Networking review: isolate the failure instead of saying the internet is down

Use a repeatable network ladder. Confirm the physical or wireless link, inspect addressing, verify the local gateway, test a known remote IP address, test name resolution, then test the intended application. Each step removes categories of causes. A client can have excellent Wi-Fi signal and still fail because DHCP, routing, DNS, authentication, captive portal, firewall policy, or the upstream provider is broken.

Understand the role of each common device even when a small-office appliance combines them. Switching, routing, wireless access, firewall policy, DHCP, DNS resolution, NAT, modem or provider handoff, and authentication solve different problems. Draw the packet path in your head. If a workstation cannot reach a local printer, the problem may never involve the internet gateway. If it reaches remote IPs but not hostnames, DNS deserves attention before replacing the network adapter.

For wireless scenarios, compare symptoms with environmental context. Congestion, co-channel interference, non-Wi-Fi interference, client density, weak signal, roaming behavior, band steering, authentication failures, and poor access-point placement can all feel like 'slow Wi-Fi.' The best next action is usually the one that measures the suspected layer rather than blindly increasing transmit power or replacing equipment.

Core 1 final-review drill: make every answer produce evidence

Take a missed practice question and write the smallest safe test that would distinguish the leading explanations. If a desktop does not boot, identify what observation separates power, POST, storage detection, boot configuration, and operating-system loading. If a user cannot reach a website, identify what separates link, local addressing, routing, DNS, and the application. This habit makes troubleshooting questions much more predictable because you are choosing an evidence-producing action rather than a dramatic repair.

Then practice verification. After any proposed fix, describe how you would prove the original problem is resolved. A replaced cable is not verified because the link light appears; test the user's actual network task. A new drive is not verified because firmware sees it; confirm the intended boot or storage workflow. A charger is not verified because its LED is on; confirm stable charging under the expected power profile. Verification keeps the troubleshooting method grounded in outcomes.

Finish by reviewing your weak areas as categories: compatibility knowledge, network-layer isolation, hardware symptom interpretation, cloud responsibility, or troubleshooting order. Spend the final study block on the category that repeatedly causes uncertainty rather than rereading every term. The cram sheet is most useful when it helps you retrieve a decision framework under pressure.

Exam-day method

Use the qualifiers and constraints before reaching for a memorized answer.

  • Read the command word first: FIRST, NEXT, BEST, MOST likely, and LEAST change the decision you are being asked to make.
  • Identify the objective and the constraint before evaluating products or commands. Several answers may be technically possible while only one fits the scope, evidence, safety, availability, or least-privilege requirement.
  • When two options seem correct, prefer the one that creates useful evidence, preserves reversibility, reduces unnecessary impact, and addresses the stated layer of the problem.
  • Do not use a practice percentage as a pass prediction. Treat missed or guessed questions as pointers to weak concepts and decision patterns, then verify the current objectives with the certification owner.
  • For performance-based thinking, practice the workflow rather than memorizing a screenshot: establish state, choose a safe action, interpret the result, and verify that the original requirement is now satisfied.

Use this cram sheet after full study and hands-on practice. CompTIA's current certification page and objectives remain the authority when any exam fact changes.