CompTIA A+ Core 2 (220-1202) — the study guide

Exam Basics: Length, Time, and Delivery

The 220-1202 exam is delivered at a Pearson VUE testing center or via online proctoring. You'll face a mix of question types drawn from a pool, with a maximum number of questions and a fixed time limit that CompTIA sets and can adjust between exam versions, so always confirm the current numbers on CompTIA's official exam page before test day. The exam is scored on a scaled point system (not a raw percentage), and CompTIA publishes the passing scaled score for each exam code. You'll get your pass/fail result immediately after finishing, along with a score report broken down by domain, which is useful for planning a retake if needed.

• Delivered at a testing center or online proctored
• Time-limited, so pacing matters
• Scaled scoring, not raw percent correct
• Immediate pass/fail result at the end

Question Types You'll See

Core 2 is not just single-answer multiple choice. You'll also encounter multiple-response questions (choose two or more), drag-and-drop matching, and performance-based questions (PBQs) that simulate a real task, like configuring a setting in a mock operating system screen or dragging steps into the correct troubleshooting order. PBQs usually appear early in the exam and can take longer to complete. A smart strategy is to flag anything that stumps you, do your best, and move on rather than burning excessive time on one question, since every question counts the same toward your score.

• Multiple choice (single answer)
• Multiple response (select two or more)
• Drag-and-drop / matching
• Performance-based simulations (PBQs)

Domains and Weighting

CompTIA organizes Core 2 content into a handful of major domains, such as Operating Systems, Security, Software Troubleshooting, and Operational Procedures. Each domain carries a different percentage weight toward your final score, and CompTIA publishes these exact percentages in the official exam objectives document. Because the weighting can shift slightly between exam versions, don't memorize an old percentage from a previous Core 2 exam code as gospel. Instead, download the current 220-1202 exam objectives PDF from CompTIA's website and use the listed weights to decide how much time to spend studying each domain.

• Operating Systems
• Security
• Software Troubleshooting
• Operational Procedures
• Check CompTIA's official objectives PDF for exact current percentages

Retake Policy and Practical Tips

If you don't pass on your first attempt, CompTIA's retake policy generally requires a waiting period before you can sit the exam again, with different rules for a second failed attempt requiring a longer wait. Always check the current CompTIA candidate agreement for the specific waiting periods in effect. On test day, budget your time by periodically checking the on-screen clock, answer every question (there's no penalty for guessing), and use the mark-for-review feature to flag uncertain answers and revisit them if time allows.

• There is a mandatory wait before a first retake
• No penalty for guessing, so never leave a question blank
• Use mark-for-review to manage time wisely

Why Passive Studying Fails This Exam

Core 2 tests operating systems, security, software troubleshooting, and operational procedures with scenario-based questions. You'll be given a situation — a user's laptop is showing suspicious pop-ups, or a technician needs to document a change — and asked what to do first. Simply memorizing definitions from a glossary won't prepare you for that; you need to practice applying knowledge to situations. Active recall means testing yourself before you feel ready, closing the book and writing out what you remember, or explaining a concept out loud as if teaching a coworker. This struggle is what builds long-term memory. Rereading notes feels productive but creates a false sense of mastery because recognizing an answer is much easier than recalling it cold.

• Use flashcards or self-quizzes for terms like RDP, VPN, and malware types
• Explain concepts aloud in your own words — if you can't, you don't know it yet
• Revisit topics after a few days, not just once

Building a Study Schedule

Start by taking a practice assessment or skimming the exam objectives to find your weak domains. Core 2 covers Operating Systems, Security, Software Troubleshooting, and Operational Procedures — most candidates are strong in one or two and weak in others based on job experience. A help desk tech might be sharp on OS installs but shaky on documentation and change management procedures. Set a realistic timeline. Most working adults need several weeks of consistent short sessions rather than one long cram. Thirty to forty-five focused minutes daily beats a single four-hour weekend session, because spaced repetition over multiple days is what moves information into long-term memory.

• Identify weak domains first using a diagnostic quiz
• Schedule short daily sessions instead of rare marathon sessions
• Reserve the final week for full practice exams and reviewing missed questions

Getting the Most Out of This Course

Each module builds toward exam objectives in order, but you don't have to study strictly linearly — if security is your weak spot, prioritize that module. Read the lesson, study the diagram and key terms, then immediately attempt the check questions without peeking at answers first. Get something wrong? That's valuable — it shows exactly what to review. Use the workplace examples to anchor abstract concepts to real scenarios, since the actual exam is written the same way. Whenever possible, practice on a real or virtual machine: navigate Windows settings, run command-line tools, or configure a mobile device. Hands-on repetition cements knowledge far better than reading alone.