A+ Core 1 220-1201 Final Review

This page is for the point when Core 1 topics are already familiar. It compresses the exam into the distinctions that are easy to blur together: connection type versus capability, DNS versus DHCP, access point versus router, M.2 form factor versus storage interface, RAID versus backup, cloud service model versus deployment model, and symptom versus likely cause.

If a section feels new rather than familiar, return to the Core 1 study guide or the matching Quick Review.

1. How to use this final review

Read once without trying to memorize every sentence. Stop when you hesitate and explain the distinction in your own words.

A useful final pass is:

• Name the device, protocol, connector, or service from its job rather than appearance alone.
• For compatibility questions, check physical fit, interface, generation, power, firmware, and software support.
• For network questions, separate local link, addressing, gateway, DNS, and the remote service.
• For troubleshooting, use the symptom to choose the subsystem before choosing the replacement part.
• For printer questions, separate job-delivery problems from output-quality problems.
• Finish with a fresh Core 1 practice set.

2. Core 1 exam map

Troubleshooting is the largest domain, but it depends on the first four. You cannot diagnose the wrong technology accurately.

3. Mobile Devices

Separate hardware, connectivity, and management

A mobile symptom should first point you toward the right category.

• Battery will not hold charge: battery health before storage or DNS.
• Device will not charge: cable, adapter, port, battery, debris, charging circuitry.
• Wi-Fi works but Bluetooth accessory will not pair: Bluetooth state, pairing, range, device support.
• Only corporate mail stops synchronizing: account, application, service, policy, or sync setting before replacing wireless hardware.
• Setting cannot be changed on a managed device: Mobile Device Management (MDM) policy may own it.

A swollen battery is a safety issue. Stop normal use and charging and follow the organization's handling procedure.

Know connection types by purpose

• USB/USB-C: data, power, peripherals, displays, or docks depending on supported capabilities.
• Bluetooth: short-range peripherals and device-to-device communication.
• Near-field Communication (NFC): very short-range tap-style communication.
• Wi-Fi: wireless local-network access.
• Cellular: carrier-based wide-area access.
• Hotspot/tethering: one device shares its connection with another.

USB-C describes the connector. It does not guarantee one fixed charging level, display mode, or data speed.

4. Networking

Attach services to jobs

Numbers matter, but jobs matter more.

• DNS: names to addresses and other DNS records. IP works but names fail is a DNS clue.
• DHCP: automatic IP configuration. A 169.254.x.x address on Windows commonly points toward failed normal DHCP configuration or local connectivity.
• HTTPS: encrypted web traffic.
• SMB: common Windows-style file and printer sharing.
• SSH: secure command-line remote administration.
• RDP: remote graphical Windows access.

Use the Ports and Protocols Reference for the exact common ports.

Separate network devices by job

A typical home router can combine several of these roles in one box. The exam can still ask which function solves the problem.

Wireless decisions

Remember the tradeoff rather than a single "best" band:

• 2.4 GHz generally offers better reach and wall penetration but has less spectrum and more common interference.
• 5 GHz generally offers more channel capacity with less reach through obstacles.
• 6 GHz adds more spectrum for compatible devices but does not create backward compatibility for older radios.

If one room has poor Wi-Fi while nearby wired devices are normal, investigate coverage, interference, placement, and radio conditions before changing DNS.

Network troubleshooting ladder

A useful order is:

1. Is the adapter/radio connected?
2. Does the client have appropriate IP configuration?
3. Can it reach the default gateway?
4. Can it reach a remote IP address?
5. Does name resolution work?
6. Does the required application/service work?

Each successful step narrows the next one.

5. Hardware

Compatibility is a stack

Check:

1. Physical connector or form factor
2. Electrical/power requirements
3. Interface and generation
4. Platform/firmware support
5. Driver/operating-system support
6. Capacity and workload requirement

A part can fit and still be incompatible.

Memory

• Desktop systems commonly use DIMMs; laptops commonly use SODIMMs.
• DDR generations are not interchangeable.
• Capacity and speed depend on platform support.
• Error-Correcting Code (ECC) memory needs compatible platform support.
• Multi-channel operation depends on supported placement/configuration.

Storage

• HDD: moving parts, common when capacity and cost matter.
• SSD: flash storage, no mechanical seek time.
• SATA: storage interface used by HDDs and SSDs.
• NVMe: solid-state storage protocol commonly using PCI Express.
• M.2: physical form factor, not a synonym for NVMe.

RAID can improve availability or performance depending on the level. RAID is not a substitute for backup.

Motherboard, CPU, expansion, and power

Match socket, chipset/platform, firmware, memory, board/case form factor, expansion slots, storage support, cooling, and required power connectors.

For a PSU, check form factor, wattage, connectors, input requirements, and workload. More wattage does not fix the wrong connector or form factor.

Printer technologies

A print job that never arrives is a connectivity/queue/driver problem until evidence says otherwise. A page that arrives with repeating defects is already past the network path.

6. Virtualization and Cloud Computing

Virtualization

• Virtual machine: software-defined computer with assigned CPU, memory, storage, and networking resources.
• Hypervisor: platform that creates and runs VMs.
• Container: isolates applications while sharing more of the host operating-system layer than a full VM.
• Virtual Desktop Infrastructure (VDI): delivers centrally hosted desktop environments to users.

A VM still needs enough host CPU, memory, storage, and networking resources. Virtualization does not create capacity from nothing.

Cloud service models

• IaaS: customer manages more of the guest systems and applications.
• PaaS: provider manages more of the runtime/platform.
• SaaS: provider operates the application; customer still manages appropriate use, identities, data, and tenant settings.

Cloud deployment models

Private, public, community, and hybrid describe how cloud environments are provisioned and combined. Public cloud does not mean customer data should be public.

Useful cloud characteristics include on-demand provisioning, broad network access, resource pooling, rapid elasticity, and measured service.

7. Hardware and Network Troubleshooting

Symptom before solution

For storage, preserve data when failure is plausible. For batteries, overheating, or electrical problems, safety outranks keeping the device running.

A known-good substitute is strong evidence when used carefully. If another cable fixes the problem, that is more useful than replacing the motherboard because it is one of the answer choices.

8. Core 1 decision rules

BEST hardware answer

Choose the component that meets the stated requirement and is compatible with the system. Newer or faster is not automatically better.

FIRST troubleshooting action

Prefer a safe observation or test that can distinguish plausible causes. Do not begin with the most destructive or expensive option when a simpler check can narrow the fault.

Wireless versus internet

Being connected to Wi-Fi only proves the local radio association. Internet access also depends on IP configuration, gateway/upstream access, DNS for names, and the destination service.

Backup versus redundancy

Redundancy helps keep a service or storage set available after certain component failures. Backup preserves recoverable copies for failures redundancy cannot solve.

Connector versus capability

USB-C, M.2, and other physical formats do not each imply one universal capability. Check the supported standard or interface.

9. Final readiness checklist

You are ready for another Core 1 practice set when you can explain these without relying on recognition alone:

• [ ] Mobile hardware symptom versus setting/policy problem
• [ ] USB-C, Bluetooth, NFC, Wi-Fi, cellular, hotspot/tethering by purpose
• [ ] DNS versus DHCP versus gateway failure
• [ ] Switch, router, access point, firewall, and provider handoff by job
• [ ] 2.4/5/6 GHz tradeoffs at A+ depth
• [ ] Common network services and why a single-service failure differs from total connectivity loss
• [ ] DIMM versus SODIMM and DDR-generation compatibility
• [ ] HDD versus SSD, SATA versus NVMe, M.2 form factor versus interface
• [ ] RAID availability versus backup recovery
• [ ] CPU/socket/chipset/firmware/memory/power compatibility
• [ ] PSU wattage, form factor, and connector requirements
• [ ] Laser, inkjet, thermal, and impact use/maintenance clues
• [ ] VM, hypervisor, container, and VDI distinctions
• [ ] IaaS/PaaS/SaaS and private/public/community/hybrid cloud
• [ ] No-power versus no-POST versus load-related restart clues
• [ ] Drive detection/health/RAID evidence
• [ ] Display signal-path checks
• [ ] Network troubleshooting from association through DNS/application
• [ ] Printer communication versus output-quality faults
• [ ] Why each wrong answer solves a different subsystem or layer

If several items are still slow, use the matching A+ Quick Reviews before taking another Core 1 practice session.

10. Official references

• CompTIA A+ certification page