CompTIA A+ Core 1 (V15) Exam Guide — Master Hardware, Networking & Troubleshooting

CompTIA A+ Core 1 (V15) is the foundational exam in the two-part A+ certification pathway designed to launch and validate an IT support career. This guide breaks down what the Core 1 (220-1201) exam covers, how it maps to real-world help-desk and technical-support roles, and practical study strategies to get you exam-ready. If you want work as an IT support specialist, help desk technician, or prepare for advanced certs like Network+ and Security+, Core 1 is where you start.

Why CompTIA A+ Core 1 (V15) matters — career and skills overview

A+ Core 1 targets the essential, hands-on skills employers expect from entry-level technical support staff: installing and maintaining hardware, configuring SOHO networks, supporting mobile devices, and diagnosing connectivity problems. Passing Core 1 and Core 2 proves you can perform day-to-day troubleshooting and sets the stage for career growth into systems administration, network support, or cybersecurity roles.

Exam objectives at a glance (what the test focuses on)

CompTIA publishes weighted objective domains for Core 1. V15 centers on four main areas:

Mobile devices (≈13%) — Installing and configuring mobile components and wireless accessories, managing sync and connectivity settings, and resolving device-level hardware and connectivity faults.
Networking (≈23%) — Understanding protocols and ports, building small office/home office (SOHO) networks, VPN basics, and using diagnostic tools like cable testers and Wi-Fi analyzers.
Hardware (≈25%) — Installing CPUs, RAM, storage, and peripherals; selecting cables and connectors (HDMI, Ethernet, USB); and configuring motherboards, power supplies, and cooling.
Virtualization & cloud computing (≈11%) — Grasping hypervisors, virtual machines, and cloud service models (IaaS, PaaS, SaaS).
Hardware and network troubleshooting (≈28%) — Applying systematic troubleshooting processes with multimeters, loopback plugs, and other tools to isolate and resolve hardware and connectivity issues.

These percentages reflect how much of the exam each domain covers, so prioritize study time accordingly.

Mobile devices: practical tasks and keywords

Mobile-device support is more than swapping batteries. Expect to:

Install and test cameras, antennas, and docking stations.
Configure Bluetooth, NFC, and USB accessories.
Troubleshoot syncing issues, cellular data, and Wi-Fi connectivity.
Study related keywords: mobile device repair, device provisioning, mobile OS settings, accessory pairing.

Networking essentials: SOHO, protocols, ports

Networking questions test both theory and hands-on setup skills:

Identify common ports and protocols (TCP/UDP, HTTP/HTTPS, DNS, DHCP).
Configure IP addressing, DHCP, NAT, and basic VPNs for SOHO environments.
Use crimpers, cable testers, and Wi-Fi analyzers to diagnose physical and wireless issues.
Key search terms: subnetting basics, router configuration, VPN setup, Wi-Fi troubleshooting.

Hardware deep-dive: installation and maintenance

Hardware objectives simulate real technician tasks:

Install and configure RAM, CPUs, and storage arrays.
Select correct cables and connectors for peripherals.
Understand motherboard form factors, power ratings, and cooling best practices.
Practical labs are vital — practice component swaps and BIOS configuration on real or virtual machines.

Virtualization & cloud: core concepts to know

Expect conceptual questions about:

Differences between hypervisors and virtual machines.
Desktop virtualization scenarios.
Cloud deployment models: IaaS, PaaS, SaaS, and when each fits.
Hands-on exposure with virtual machine software (VMware, VirtualBox) helps cement the ideas.

Troubleshooting: a methodical approach

Troubleshooting is a major portion of Core 1. Learn to:

Use a structured troubleshooting methodology: identify, hypothesize, test, implement, verify, and document.
Operate tools: multimeters for power checks, cable testers for network continuity, and loopback plugs for port testing.
Prioritize safety and escalation when hardware shows signs of failure.
Keywords to practice: diagnostic flowchart, root-cause analysis, hardware diagnostics.

Exam logistics — what to expect on test day

Exam code: 220-1201 (Core 1, V15).
Launch date: March 25, 2025 (V15 release).
Questions: Up to 90 items mixing multiple-choice (single and multiple response), drag-and-drop, and performance-based tasks.
Duration: 90 minutes.
Passing score: 675 on a 900-point scale.
Language: English.
Recommended experience: About 12 months in a hands-on IT support role.
Typical retirement: CompTIA exams are often supported for roughly three years after release (estimate: V15 retire ~2028).
DoD 8140-approved roles: Technical support specialist, system administrator, cyber defense infrastructure support specialist.

Skills you’ll gain (real, on-the-job benefits)

By preparing for Core 1 you’ll learn to:

Install, configure, and maintain desktop, laptop, and mobile hardware.
Build and secure SOHO networks and troubleshoot connectivity.
Use virtualization and cloud concepts to support modern deployments.
Apply diagnostic tools and processes to resolve hardware, network, and peripheral issues.

Study strategy & resources — get exam-ready

Hands-on practice: Assemble a small lab with spare components or use virtualization to simulate hardware and networks.
Practice exams: Take timed practice tests that include performance-based items.
Official objectives: Study the CompTIA exam objectives and focus on weighted domains.
Work experience: If possible, gain 12 months of support experience or shadow a help-desk technician.
Study bundles: Combine a course (online or instructor-led), labs, and question banks for balanced preparation.

Final note — mapping certification to career growth

CompTIA A+ Core 1 (V15) builds the technical muscle you need for entry-level IT roles and forms a solid foundation for higher-level certifications like Network+ and Security+. Treat the exam as a skills credential: practice deliberately, focus on troubleshooting workflows, and reinforce learning with real hardware and simulated networks.

Ready to start? Map your study plan to the percentages above, build a small lab, and practice performance-based problems until troubleshooting becomes second nature. Good luck — you’ve got this.