C-CATODSW case studies
C-CATODSW · Put your knowledge to work in context.
The AWS Certified Cloud Practitioner is an entry-level credential for people who want to demonstrate foundational fluency with the AWS cloud: what the core services do, how the shared responsibility model splits duties between AWS and the customer, and how billing and support work. It suits career changers, sales and product staff, project managers, and anyone in a technical-adjacent role who needs to talk credibly about cloud concepts without building workloads. The C-CATODSW case studies are 5 cases and about 2,437 words.
1Right-Sizing a Burstable Instance for a Spiky Reporting Job
A team runs a nightly reporting job on a single burstable compute instance (2 vCPU, 4 GiB) in a public cloud. The job runs from 01:00 to 01:40 and pushes CPU to 100% of the baseline for the entire window; the rest of the day the instance sits near 5% CPU.
558 words, about 3 min2Cross-Account Access for a Shared Logging Bucket
A company has three application accounts (App-A, App-B, App-C) and one central security account. Each app account writes audit logs to a bucket owned by the security account.
548 words, about 3 min3Reserved Capacity vs On-Demand for a Predictable but Growing Workload
A SaaS company runs a steady-state API tier of 20 identical instances 24/7. Usage has grown 8% per quarter for six quarters and is expected to keep growing, but the growth is uneven across regions.
451 words, about 2 min4Multi-Region Failover with a Data Residency Constraint
A healthcare-adjacent startup must keep primary customer data in one country (Region A) by regulation, but wants a disaster-recovery posture. Leadership proposes active-active across Region A and Region B in another country, with synchronous replication, claiming 'five nines and no data loss.' The database is a single-writer relational store; synchronous cross-border replication would add roughly 120 ms round-trip latency to every write.
428 words, about 2 min5Tagging Strategy to Make Cost Allocation Defensible
A company with 40 accounts and 12 product teams discovers that 38% of its monthly cloud bill (about 190,000 of 500,000) cannot be attributed to a team. Investigation shows inconsistent tag keys ( team , Team , owner-team ), resources created by automation that skip tags, and shared services (networking, logging) with no clear owner.
452 words, about 2 min