How do I prioritize domains in my spaced repetition system for a certification exam?
Allocate SRS card creation proportional to both exam domain weight and your personal knowledge gap. A domain worth 20% of the exam that you know well needs fewer cards than a domain worth 15% where you have significant gaps. The highest-priority domains are those where exam weight multiplied by knowledge gap is largest. Create more cards, with shorter initial intervals, for these high-priority domains.
Certification exams do not weight all domains equally. The CISSP distributes its questions across eight domains with weights ranging from 10% to 16%. The CompTIA Security+ covers six domains with weights from 12% to 23%. The PMP distributes across three domains with very different question proportions. The AWS Certified Solutions Architect divides its questions across five major service categories.
A spaced repetition system that treats all domains equally misallocates study effort. Spending identical SRS time on a 10%-weight domain and a 22%-weight domain is inefficient, regardless of how strong or weak you are in each.
This article describes how to build a domain-aware spaced repetition system that matches SRS effort to exam weight and personal gap analysis.
The Priority Matrix
Effective domain prioritization uses two axes:
- Exam domain weight: The percentage of exam questions from that domain (available from the certification body's exam content outline)
- Your personal gap: How much you need to learn vs. what you already know
Multiplying these two factors produces a priority score:
| Domain | Exam Weight | Personal Gap (0-10) | Priority Score |
|---|---|---|---|
| Domain A | 22% | 8 (significant gap) | 22 x 8 = 176 |
| Domain B | 18% | 3 (strong existing knowledge) | 18 x 3 = 54 |
| Domain C | 15% | 6 (moderate gap) | 15 x 6 = 90 |
| Domain D | 12% | 9 (large gap) | 12 x 9 = 108 |
| Domain E | 10% | 4 (modest gap) | 10 x 4 = 40 |
In this example, Domain A and Domain D are highest priority despite Domain D having a smaller exam weight than Domain B, because the gap in Domain D is larger.
Allocate SRS effort -- card creation time, daily review volume for that domain's deck -- proportional to priority scores.
Building Domain-Separated Decks
A single flat SRS deck prevents domain-specific prioritization. Domain-separated decks allow you to:
- Review high-priority domains more frequently
- Suspend low-priority cards temporarily when time is limited
- Assess retention strength by domain (which maps to practice exam performance by domain)
- Adjust review volume when practice exams reveal domain-specific weaknesses
Recommended deck structure in Anki:
Certification Name (parent deck)
Domain 1 - [Name] (20% weight)
Domain 2 - [Name] (18% weight)
Domain 3 - [Name] (15% weight)
...
Practice Exam Errors (any domain)
Final Review (high-failure cards from all domains)
The parent deck organizes; the sub-decks allow independent scheduling. Setting different daily review limits per sub-deck allocates more reviews to higher-priority domains.
Card Count Targets by Domain
As a general guideline for major certifications:
| Certification | Total Cards | Per Domain (typical) |
|---|---|---|
| CompTIA Security+ | 200-300 | 30-50 per domain |
| AWS Solutions Architect | 250-350 | 50-70 per service category |
| CISSP | 350-500 | 40-65 per domain |
| PMP | 200-300 | Weighted by process group |
| CCNA | 250-400 | 40-80 per topic area |
These are cards you create, not cards you find in pre-made decks. Pre-made decks often have 2-3x this volume with much lower quality per card. If you use a pre-made deck, apply a curation pass: suspend or delete cards that are:
- Too complex (multiple concepts per card)
- Not listed in the current exam objectives
- Testing trivia rather than exam-critical distinctions
- Duplicative of other cards in the deck
"Card curation is not laziness -- it is precision. A curated 300-card deck with 95% exam relevance outperforms an uncurated 1500-card deck with 60% exam relevance by reducing review burden while maintaining coverage of critical material." -- Applied learning principles from Kornell and Bjork, 2008
Tracking Domain Performance in SRS
Most SRS tools provide statistics that can guide domain prioritization:
In Anki: The Statistics view shows retention rate per deck. A domain deck with 85%+ retention rate is in good shape. A domain deck with retention below 70% needs more aggressive review (more frequent sessions, targeted card revision, supplementary reading).
Practice exam alignment: Compare your domain-by-domain SRS retention rates with your domain-by-domain practice exam scores. Mismatches reveal gaps in the SRS system:
- High SRS retention, low practice score: You are retaining definitions but not applying them. Add scenario application cards.
- Low SRS retention, high practice score: You have implicit understanding that your cards are not testing. Your cards may be too surface-level.
Dynamic Priority Adjustment During the Study Arc
Domain priorities should not be fixed at the start of the study arc. Adjust dynamically based on:
Practice exam domain scores: After each full-length practice exam, recalculate your gap score for each domain. A domain where you score 60% needs more SRS attention than one where you score 85%.
Approaching the exam: In the final 3 weeks, shift resources from your strongest domains to your weakest. The strongest domains can maintain with reduced review frequency; the weakest domains need increased review intensity.
Content coverage progress: If you have not yet read a domain's material, the domain cannot have SRS coverage. As you complete each domain's reading, immediately begin card creation and SRS review for that domain.
"The allocation of study resources to the domains with the largest weighted gaps is the single highest-impact scheduling decision a certification candidate makes. Getting this allocation right has more impact on exam performance than any single study technique." -- ISC2 candidate performance analysis, 2022
Avoiding Domain Overload
A common failure mode is creating too many cards for the first domain studied (usually the easiest or most interesting) and running out of capacity for later domains. This produces excellent retention for early domains and poor retention for later domains.
Guards against domain overload:
- Set a card creation budget per domain before starting (e.g., 50 cards maximum for Domain 1 regardless of how much material is there)
- Complete an initial pass through all domains before deep-diving into any single domain
- Track card counts per domain and reallocate if any domain is over-represented
- Prioritize breadth of coverage during building phase; depth during consolidation phase
Frequently Asked Questions
My certification does not publish exact domain weights. How do I estimate priority? Use the official exam objectives document -- the number of sub-objectives per domain is a rough proxy for question volume. Community resources, study group discussions, and third-party study guides often include estimated domain question counts based on historical exam feedback. Use these estimates cautiously but they provide a reasonable basis for priority allocation.
Should I create separate decks for each domain or just tag cards by domain? Both approaches work. Separate decks make it easier to set different daily review limits per domain. Tags within a single deck make it easier to run cross-domain filtered reviews (e.g., all "comparison" cards across all domains). Beginners should use sub-decks; experienced Anki users may prefer tags for flexibility.
What if two domains have similar priority scores -- how do I choose between them? When priority scores are similar, review both regularly and let practice exam performance be the tiebreaker. The domain where your practice questions are consistently weaker gets the higher SRS priority, regardless of the calculated score.
References
- Kornell, N., & Bjork, R.A. (2008). Learning concepts and categories: Is spacing the enemy of induction? Psychological Science, 19(6), 585-592.
- Cepeda, N.J., Pashler, H., Vul, E., Wixted, J.T., & Rohrer, D. (2006). Distributed practice in verbal recall tasks: A review and quantitative synthesis. Psychological Bulletin, 132(3), 354-380.
- Dunlosky, J., Rawson, K.A., Marsh, E.J., Nathan, M.J., & Willingham, D.T. (2013). Improving students' learning with effective learning techniques. Psychological Science in the Public Interest, 14(1), 4-58.
- Roediger, H.L., & Karpicke, J.D. (2006). Test-enhanced learning: Taking memory tests improves long-term retention. Psychological Science, 17(3), 249-255.
- ISC2. (2024). CISSP candidate information bulletin. International Information System Security Certification Consortium.
- Project Management Institute. (2023). PMP examination content outline. PMI.