TS-C study materials
TS-C study resources

TS-C (NCCT) case studies

TS-C · Put your knowledge to work in context.

TS-C is an exam code for a technical systems certification aimed at practitioners who plan, deploy, operate, and support technology infrastructure in production environments. It is written for people with hands-on exposure to the technology rather than for pure theorists: engineers, administrators, implementation consultants, and support staff who are expected to make design decisions and then live with the operational consequences. The TS-C case studies are 5 cases and about 4,155 words.

1

Sizing a Four-Node Expansion When the Averages Are Lying

A 40-person SaaS team runs a ticketing and reporting service on a five-node application cluster behind a load balancer. At the daily peak the fleet serves 120 requests per second, and fleet-average CPU at peak is 58%.

815 words, about 4 min
2

An Intermittent Morning Slowdown That No Alert Sees

Users open two to five tickets a week saying the customer portal "hangs" between 09:10 and 09:40, on two or three mornings out of five. Monitoring scrapes host CPU, memory, and disk every five minutes and stores five-minute averages; there is no per-request tracing, and APM head-sampling is set to 1%, with spans that start at the application handler.

805 words, about 4 min
3

Ninety Days to Attribute Every Administrative Action

An external auditor has flagged six items at a 60-person company. You have 90 days, 40 engineering hours, and no budget for new tooling.

876 words, about 4 min
4

The Fix That Drift Enforcement Will Revert at 02:00

Twelve identical web nodes are managed declaratively from a repository. A weekly drift scan runs Sundays at 02:00 with enforcement enabled, so any node that deviates from the repository is reverted at the next run.

803 words, about 4 min
5

A Backup Dashboard That Is 100% Green and Cannot Meet RTO

A 2 TB transactional database is backed up with a nightly incremental at 02:00 that takes 25 minutes and a weekly full on Sunday at 01:00 that takes 5 hours. Backups go to an offsite object store and are retained for 30 days.

856 words, about 4 min