TCTCN study plan
TCTCN · Give each week a clear focus.
8 weeks · About 7 hours per week
Implementation, Configuration, and Operations (unverified placeholder)
Map the Domain 3 task outline into a checklist of every configuration item you must be able to perform unaided
Build a working lab environment that mirrors the implementation scenarios described in the domain objectives
Configure at least three end-to-end setups from a blank state, timing each one
Record every command and setting that required a lookup into a personal syntax cheat sheet
Your checkpoint
A lab build log with timestamps for three complete end-to-end configurations plus a one-page command/cheat sheet
Implementation, Configuration, and Operations (unverified placeholder)
Execute the operational lifecycle tasks (deploy, verify, monitor, back up, restore) in the lab without notes
Write step-by-step runbooks for the five highest-risk operational procedures
Inject three deliberate faults and document the detection and recovery path for each
Compare your runbooks against the domain objectives and close every gap you find
Your checkpoint
Five validated runbooks plus a fault-injection log showing detection time and recovery steps for three failures
Architecture, Design, and Planning (unverified placeholder)
Draft a reference architecture that satisfies a stated set of capacity, availability, and growth requirements
Justify each design decision in writing against at least one alternative you rejected
Translate the reference architecture into a sizing worksheet with explicit inputs and outputs
List every assumption that would invalidate the design and how you would test it
Your checkpoint
A 3-5 page design document with a sizing worksheet and an alternatives-considered section
Architecture, Design, and Planning (unverified placeholder) & Fundamentals and Core Concepts (unverified placeholder)
Review the design document against Domain 1 core concepts and label each requirement it depends on
Identify and rewrite any design decision that contradicts a foundational concept
Create a one-page glossary linking each core concept to the design element that uses it
Score yourself on 40 mixed Domain 1 and 2 practice items and tabulate results by objective
Your checkpoint
A revised design document with a concept-to-design traceability table and a scored 40-item diagnostic with a ranked weak-area list
Fundamentals and Core Concepts (unverified placeholder)
Define every Domain 1 term in your own words without consulting notes, then correct the definitions you missed
Build a concept map connecting the fundamental models, components, and their interactions
Explain each core concept out loud in under 90 seconds as if briefing a new colleague
Convert every concept you could not explain into an active-recall card and drill them to 90 percent recall
Your checkpoint
A finished concept map plus a 60-card active-recall deck with a logged drill score of at least 90 percent
Security, Compliance, and Troubleshooting (unverified placeholder)
Map each security, compliance, and control requirement in Domain 4 to the specific mechanism that satisfies it
Configure the relevant access-control, logging, and audit settings in the lab and capture the resulting evidence
Audit your Domain 3 lab build against your control matrix and remediate every finding
Summarize the shared-responsibility boundaries that apply to the scenarios in the objectives
Your checkpoint
A completed control matrix with lab evidence attached for each control and a remediation log from the audit
Security, Compliance, and Troubleshooting (unverified placeholder) & Implementation, Configuration, and Operations (unverified placeholder)
Diagnose ten troubleshooting scenarios from symptoms alone, writing the hypothesis before touching the system
Time your mean time to isolate for each scenario and record it
Practice the logging, escalation, and evidence-preservation steps that apply to security-related incidents
Re-run the three earlier fault injections and confirm your runbooks now resolve them faster
Your checkpoint
A troubleshooting journal covering ten scenarios with recorded isolation times and before/after runbook timings
Fundamentals and Core Concepts (unverified placeholder) & Architecture, Design, and Planning (unverified placeholder) & Implementation, Configuration, and Operations (unverified placeholder) & Security, Compliance, and Troubleshooting (unverified placeholder)
Complete two full-length timed practice exams under test-day conditions
Analyze every missed item to root cause (knowledge gap, misread, or process error) rather than just the correct answer
Re-drill only the objectives that scored below 75 percent until each clears that threshold
Rehearse the exam-day logistics: timing checkpoints, review strategy, and flag-and-return rules
Your checkpoint
Two timed practice exam score reports with a root-cause analysis sheet and a remediation log showing every sub-75 percent objective re-tested above threshold
Milestones
Week 2: Perform three core Domain 3 configurations from memory in a fresh lab and pass your own runbook walkthrough without referencing external material
Week 4: Score at least 70 percent on the 40-item Domain 1 and 2 diagnostic with no objective below 50 percent
Week 6: Every control in the Domain 4 matrix has attached lab evidence and the Domain 3 lab audit shows zero open findings
Week 8: Score at least 85 percent on both full-length timed practice exams with no domain below 75 percent