← All articles

CompTIA A+

CompTIA A+ Core 1 vs Core 2: The Real Difference

CompTIA A+Core 1Core 2exam objectivesstudy plan

Photo by Pok Rie on Pexels

CompTIA A+ has two exams you must pass: Core 1 (220-1101) and Core 2 (220-1102). Core 1 focuses on devices, hardware, networking, and cloud basics. Core 2 targets operating systems, security, and procedures. You can take them in any order, but your background should guide the sequence for the fastest, most confident pass.

What each exam covers

Core 1 at a glance: devices, hardware, and connectivity

Core 1 is hands-on with physical tech and user endpoints. Expect to identify components, choose the right connectors, and resolve device and network issues quickly.

• Mobile devices: Configure mobile email, hotspot and tethering settings, display and security options, and common accessories.
• Hardware: Install RAM, storage, power supplies, and peripherals; interpret motherboard form factors and connectors; choose RAID levels; handle printers and imaging devices.
• Networking: Compare ports and protocols, SOHO router features, IP addressing, DHCP and DNS basics, and Wi-Fi standards; set up small networks and troubleshoot connectivity.
• Virtualization and cloud: Spin up client-side VMs, allocate CPU and memory, capture snapshots, and understand basic cloud models relevant to end users.
• Hardware and network troubleshooting: Use a structured approach to no-power, no-boot, overheating, and slow performance issues; diagnose wired and wireless problems.

What success looks like on Core 1: You recognize the right cable or port by sight, pick the best storage for a scenario, and can methodically troubleshoot device and network symptoms under time pressure.

Core 2 at a glance: operating systems, security, and procedures

Core 2 is about making systems usable, secure, and supportable in production.

• Operating systems: Install and configure Windows editions and features, manage users and groups, work with services, and handle updates; understand macOS and Linux basics and common commands.
• Security: Implement least privilege, account management, passwords and MFA, workstation hardening, physical security, secure browsing and email, and social engineering awareness.
• Software troubleshooting: Fix app crashes, OS boot issues, spooler errors, browser hijacking, and performance problems using logs, safe mode, and recovery options.
• Operational procedures: Safety, professionalism, documentation, change management, backups, disaster recovery concepts, and communication with users.

What success looks like on Core 2: You can secure a workstation, repair OS problems without data loss, and follow procedures that keep systems stable and users supported.

Format, scoring, and question types

Exam structure you can expect

Both Core 1 and Core 2 share a similar structure, with differences in what scenarios you see.

• Codes: Core 1 is 220-1101. Core 2 is 220-1102.
• Time and length: Up to 90 minutes per exam with a maximum of 90 questions.
• Question types: Multiple-choice single and multiple response, drag-and-drop matching, and performance-based questions (PBQs) that simulate real tasks.
• Scoring: Scaled 100 to 900. Core 1 requires a 675 to pass. Core 2 requires a 700 to pass.

What PBQs feel like

PBQs mirror help desk and bench tech workflows. You might cable a SOHO network, place components on a motherboard diagram, set Windows permissions, or triage a malware-infected PC. The key is process: identify the goal, note constraints, execute cleanly, verify results.

Pro tip: PBQs often appear early. Manage your time by scoring quick wins first, flagging complex PBQs, and returning after banking points. Practicing PBQ-style items pays off disproportionately. You can drill realistic scenarios with our practice exams and preview PBQ-style tasks in the free preview.

Which should you take first?

Start where your experience is strongest

You can pass in any order, but sequence affects momentum.

• If you are hands-on with hardware and home labs: Take Core 1 first. You will bank a quick win and build confidence.
• If your job is service desk or you are strong with Windows and troubleshooting users: Take Core 2 first, since OS and security will feel familiar.
• If you are new to IT: Start with Core 1. Tangible hardware and port-protocol mapping provide anchors that make Core 2 concepts easier later.

Consider topic dependencies

• Core 1 networking makes Core 2 security clearer. Understanding ports, protocols, and Wi-Fi helps when hardening systems and diagnosing malware traffic.
• Core 2 operational procedures make Core 1 troubleshooting safer. ESD, documentation, and change control reduce rework when you are swapping hardware.

Blend timelines with your goals

If you target a near-term help desk role, completing Core 2 early can showcase OS and support skills in interviews. If you want bench repair or on-site technician work, leading with Core 1 signals hardware fluency. Either way, plan both within a tight window so knowledge cross-pollinates.

Study plans that work for Core 1 and Core 2

Build a focused, objective-driven roadmap

• Map every domain objective to study tasks, labs, and practice questions. Check them off as you gain demonstrable skill.
• Use short, daily sessions of 45 to 75 minutes with one weekly longer block for labs and PBQs.

Core 1 study moves

• Hardware labs: Install RAM, mount SSDs, connect SATA and NVMe, and interpret BIOS settings. Practice printer maintenance and driver installs.
• Network drills: Crimp or test a cable, configure a SOHO router, change SSID and security settings, and troubleshoot DHCP or DNS issues.
• Visual flashcards: Ports, cables, connectors, and form factors respond well to image-based recall.
• PBQ practice: Simulate cabling a small office, allocating VM resources, or arranging components on a diagram. Pair each PBQ with a short post-mortem to capture lessons.

Core 2 study moves

• Windows workflows: Create users and groups, set NTFS permissions, manage services, use Event Viewer, and tune startup apps.
• Security hygiene: Enable MFA, set account lockout policies, harden browsers, and practice safe mode malware remediation.
• Cross-OS familiarity: Run a Linux VM to practice navigation and file operations; know common macOS settings and recovery options.
• PBQ practice: Given a scenario, repair a broken boot, apply least privilege, or configure backups with verification.

Test-taking tactics for both exams

• Master the troubleshooting process: Identify, hypothesize, test, verify, document. Use it as a mental checklist.
• Time management: Aim for two passes. First pass answers sure things and easy PBQs. Second pass handles flagged items with deeper analysis.
• Elimination discipline: Remove clearly wrong options to raise odds. Watch for distractors that violate the scenario constraints.

Want structured, exam-like practice with explanations and PBQs? Rappelia offers scenario-rich sets mapped to every objective. Try the free preview to see how breakdowns and memory tips accelerate recall, then scale up with our practice exams to lock in exam readiness.

Overlaps, traps, and real-world scenarios

Where content overlaps

• Networking appears in both: Core 1 tests configuration and connectivity; Core 2 leans on secure use, permissions, and OS-level network tools.
• Command line shows up twice: Core 1 benefits from ipconfig and ping for connectivity; Core 2 expands into taskkill, sfc, dism, and Linux basics.
• Virtualization supports both: Client VMs begin in Core 1; Core 2 applies them for testing, containment, and recovery.

Common traps to avoid

• Memorization without context: Ports, cables, and commands stick better when tied to a scenario and a why. Always ask what failure a tool fixes.
• Skipping PBQs: Many candidates under-practice PBQs and get surprised by multi-step tasks. Build muscle memory by solving realistic labs.
• Ignoring operational procedures: Rushing hardware swaps without ESD or documentation creates new problems. Procedures are scored because they matter in production.
• Not reading the stem: A single constraint like budget, legacy compatibility, or compliance can flip the correct answer. Underline or mentally note constraints.

Translate prep into job-ready skill

Structure your practice as mini help desk tickets:

• Symptom: User cannot print to the network printer.
• Diagnose: Check connectivity, printer queue, device status, and permissions.
• Fix: Restart the spooler, clear stuck jobs, reinstall the driver, or re-add the TCP/IP port.
• Verify and document: Confirm a test page, note the cause, and record the change.

This mindset turns objectives into workflows you can replicate during PBQs and on the job.

Key takeaways

• Core 1 centers on devices, hardware, and networking; Core 2 targets operating systems, security, and procedures.
• Both exams share format and PBQs, but Core 2 has a higher passing score and more OS-security scenarios.
• Choose the order based on your strengths, then schedule the second exam soon after to maintain momentum.
• Practice PBQs deliberately and tie memorization to scenarios for durable recall.
• A structured plan with labs, timed drills, and post-mortems accelerates first-try passes.

Ready to turn planning into passing? Explore Rappelia's objective-mapped drills and PBQs. Start with the free preview, then commit to our practice exams when you are ready to simulate test day and close knowledge gaps.