TR-C study plan

Define the core terminology of the TR-C body of knowledge in your own words and map each term to the domain where it is assessed

Diagram the end-to-end architecture of a reference deployment, labeling every component and the data flow between them

Identify the five configuration surfaces you will be tested on and list the default value and valid range for each

Complete one hands-on build of a minimal working configuration from a blank starting point without consulting notes

Configure each of the primary components in a lab environment and record the exact steps and settings used

Reproduce three common configuration patterns (single-node, clustered, and federated) and note where they diverge

Break and then fix your own configuration three times, documenting the symptom, root cause, and fix for each

Write configuration snippets for the ten settings most likely to appear in scenario questions

Translate a written set of business requirements into a component and sizing design with explicit assumptions

Compare two design alternatives against cost, availability, and operational complexity, and justify a selection

Validate your design against capacity and scaling limits by computing expected load against documented thresholds

Peer-review your own design as if you were the examiner and list every gap you cannot defend

Produce a migration and rollout plan with phases, rollback points, and dependency ordering

Explain the core concepts behind each design decision you made, citing the underlying principle rather than the product feature

Answer 30 practice scenario questions in domains 1-3 and log every wrong answer with a corrected explanation

Re-derive the design constraints from first principles without looking at your week 3 document

Execute the routine operational tasks of a full lifecycle (provision, patch, back up, restore, decommission) in your lab

Write the standard operating procedures for the five most frequent operational activities, each with pre-checks and verification steps

Perform a restore from backup and measure actual recovery time against your stated objective

Document an escalation path and the operational metrics you would report weekly to a manager

Instrument your lab with the key health, performance, and capacity signals and confirm each one reports correctly

Inject five distinct faults and diagnose each using only the telemetry you configured, recording time-to-diagnosis

Build a triage decision tree that maps observed symptoms to the most likely causes and next diagnostic step

Distinguish monitoring signals that indicate imminent failure from those that indicate active failure

Map the security and compliance controls in the exam scope to concrete configuration settings in your lab and verify each is enforced

Design a least-privilege access model with roles, and test that an under-privileged account is correctly denied

Write a governance checklist covering change control, audit logging, and data retention, and audit your own lab against it

Resolve three troubleshooting scenarios that involve a security or compliance dimension rather than a pure performance fault

Take two full-length timed practice exams and score each by domain to identify residual weak areas

Re-study only the two lowest-scoring domains, using your own week 1-7 deliverables as the source material

Rehearse explanations aloud for the twenty concepts you found hardest, until each is fluent in under 60 seconds

Assemble a one-page pre-exam review sheet containing only facts you have personally verified in the lab