TS-C study materials
TS-C study resources

TS-C (NCCT) study plan

TS-C · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Foundational Concepts and Terminology & Planning, Design, and Configuration

  • Define every foundational term in Domain 1 in your own words and group them into a concept map of at least 25 nodes

  • Distinguish between commonly confused term pairs and write one contrast sentence for each pair

  • Identify the inputs and outputs of the planning and design lifecycle and list them in sequence

  • Draft a one-page glossary cross-referencing each Domain 1 term to the Domain 2 activity where it is used

Your checkpoint

A 25+ term concept map plus a one-page glossary with at least 10 explicit term-pair contrasts

Week 2

Planning, Design, and Configuration

  • Translate three sample business requirements into design constraints and record the trade-offs you accepted

  • Sequence a configuration workflow end to end and annotate each step with its prerequisite and rollback action

  • Compare at least three design alternatives against cost, capacity, and risk criteria in a decision table

  • Explain aloud, without notes, why a chosen configuration satisfies each stated requirement

Your checkpoint

A design decision record covering three alternatives with scored criteria and a justified recommendation

Week 3

Implementation and Deployment

  • Execute each core implementation procedure at least twice in a lab or sandbox environment

  • Write a numbered deployment runbook with verification checkpoints after every irreversible step

  • Diagnose and correct at least three deliberately introduced configuration errors during deployment

  • Document the minimum viable deployment path versus the full-featured path and state when each applies

Your checkpoint

A tested deployment runbook with post-step verification checks and three logged error/fix pairs

Week 4

Implementation and Deployment & Operations, Maintenance, and Troubleshooting

  • Perform a full deployment from a clean starting state using only your runbook, and time it

  • Build a troubleshooting decision tree that maps observable symptoms to likely causes for at least eight failure modes

  • Apply the decision tree to three injected faults and record the time to resolution for each

  • Convert every slow step and every runbook ambiguity you found into a concrete correction

Your checkpoint

A revised runbook plus an eight-branch troubleshooting tree validated against three injected faults

Week 5

Operations, Maintenance, and Troubleshooting

  • Classify routine maintenance tasks by frequency and impact, and schedule them into a weekly and monthly cadence

  • Interpret monitoring and log output to isolate the root cause in at least five practice scenarios

  • Write escalation criteria that define when an issue stops being routine and requires additional resources

  • Practise explaining a diagnosis to a non-technical stakeholder in under two minutes

Your checkpoint

A maintenance calendar plus five written incident analyses with root cause, evidence, and fix

Week 6

Security, Compliance, and Governance

  • Map each control in the security and governance framework to a concrete configuration setting you can verify

  • Perform an access review and justify every granted role against the principle of least privilege

  • Identify the compliance obligations that apply to a sample deployment and list the evidence each one requires

  • Draft audit-ready evidence records for at least six controls

Your checkpoint

A control-to-configuration matrix with six evidence records and one completed access review

Week 7

Operations, Maintenance, and Troubleshooting & Security, Compliance, and Governance

  • Resolve a set of mixed troubleshooting and governance scenarios by stating which domain governs and why

  • Audit your week 4 deployment runbook against the week 6 controls and patch every gap found

  • Rehearse the weakest two domains under timed conditions and score your own answers

  • Correct every item you missed by writing the underlying rule rather than the answer

Your checkpoint

A patched runbook meeting all mapped controls plus a scored weakness log with written rules for each miss

Week 8

Foundational Concepts and Terminology & Planning, Design, and Configuration & Implementation and Deployment & Operations, Maintenance, and Troubleshooting & Security, Compliance, and Governance

  • Sit two full-length timed practice assessments and record per-domain accuracy

  • Rank the five domains by accuracy and re-drill the two lowest until each exceeds your target score

  • Recite core definitions and decision criteria from memory in a rapid self-quiz

  • Finalise a one-page pre-exam reference sheet limited to items you have repeatedly missed

Your checkpoint

Two scored practice attempts with a per-domain accuracy table and a one-page final review sheet

Milestones

Week 2: Can define all Domain 1 terms from memory and justify a design decision against three alternatives without notes

Week 4: Complete a clean deployment from the runbook alone and diagnose three injected faults using the troubleshooting tree

Week 6: Map every listed security and governance control to a verifiable configuration setting and produce evidence for six of them

Week 8: Score at or above target in all five domains on two timed full-length practice assessments