Exam Domains & Study Strategy

Core 1 (220-1201) Domain Breakdown

Core 1 has five domains. The V15 weights shifted slightly from the retired version - networking grew, mobile shrank - so study from current numbers:

Core 1 study priority

Troubleshooting (28%) and Hardware (25%) together are 53% of Core 1 - spend over half your time there. Networking (23%) is next, then Mobile (13%) and Virtualization/Cloud (11%). Memorize the common ports: 80 (HTTP), 443 (HTTPS), 22 (SSH), 3389 (RDP), 53 (DNS), 25/587 (SMTP), 143 (IMAP), 445 (SMB).

Core 2 (220-1202) Domain Breakdown

Core 2 study priority

Operating Systems and Security are tied at 28% and dominate the exam. Operational Procedures (21%) is the most under-studied domain - it covers easy points on ticketing, MSDS/safety, and the difference between full, incremental, and differential backups. Software Troubleshooting (23%) overlaps heavily with the OS domain.

The Three Question Formats

1. Multiple-choice - one correct answer, or "Choose TWO/THREE." Read the count carefully; selecting one on a Choose-two question scores zero.
2. Drag-and-drop - match ports to protocols, order steps, or categorize components.
3. Performance-based questions (PBQs) - simulated environments where you complete a task: partition a drive in Disk Management, configure a SOHO router, set NTFS permissions, or run a ping/ipconfig sequence. PBQs usually appear first and are heavily weighted.

Pro tip: If a PBQ stalls you, flag it and move on to multiple-choice. Banking the quick points first protects your time; return to PBQs at the end.

CompTIA's Troubleshooting Methodology (a Competency Standard)

The V15 Core 1 objectives print the troubleshooting methodology as a "competency standard", not as a formal objective: CompTIA says the methodology itself will not be tested, while troubleshooting within the job role context stays a focus. Learn the six steps as the way to work through troubleshooting scenarios, not as a list to recite:

1. Identify the problem.
2. Establish a theory of probable cause (question the obvious); research the knowledge base/internet, if applicable.
3. Test the theory to determine the cause.
4. Establish a plan of action to resolve the problem and implement the solution.
5. Verify full system functionality and, if applicable, implement preventive measures.
6. Document findings/lessons learned, actions, and outcomes.

Trap: In a troubleshooting scenario, question the user and check the obvious before you swap parts. "Replace the RAM" before any theory has been tested jumps straight to a step-4 fix.

Recommended 8-Week Study Plan (per exam)

Exam-Day Tips

• Arrive/log in early (15 minutes before start).
• Flag PBQs, do multiple-choice, then return.
• Watch qualifiers: BEST, MOST likely, FIRST, NEXT.
• Eliminate to two options when unsure - 50% beats guessing blind.
• Pace: ~1 minute per item, never more than 2 on one question.
• Trust consistent practice-exam scores (aim for 85%+ before booking).

High-Yield Facts to Memorize Cold

These appear repeatedly and are pure recall - bank the points:

How the Two Sections Connect

Core 1 troubleshooting (28%) and Core 2 software troubleshooting (23%) are both scenario-based troubleshooting domains, and the same six-step method above works for both, so learning it once pays off on both exams. Likewise the Networking domain (Core 1) feeds the Security domain (Core 2): you cannot reason about firewalls, VPNs, or port-based attacks without knowing the ports table. Study the methodology and ports early - they are the connective tissue of the whole certification.