C-CATODSW study materials
C-CATODSW study resources

C-CATODSW study plan

C-CATODSW · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Technology

  • Map the AWS global infrastructure model by writing a one-page note that defines regions, availability zones, edge locations, and how they relate to fault tolerance and latency.

  • Classify at least 20 core AWS services into compute, storage, networking, database, and management categories in a personal reference table.

  • Explain the shared responsibility boundary for three different service models (IaaS, PaaS, and managed SaaS-like services) in your own words.

  • Set up a free-tier account and navigate the management console to locate billing, IAM, and the service search bar without guidance.

Your checkpoint

A categorized service reference table covering at least 20 services with one-line purposes and a written infrastructure glossary.

Week 2

Technology

  • Compare the compute options (virtual servers, containers, serverless functions, and managed platform runtimes) and write selection criteria for each.

  • Describe how object storage, block storage, and file storage differ and give a realistic use case for each.

  • Trace a request path from a user through DNS, a content delivery network, and a load balancer to an application tier.

  • Sketch a three-tier architecture on paper that separates public, application, and data subnets.

Your checkpoint

A hand-drawn or digital architecture diagram of a three-tier web application with every component labeled and justified in a companion paragraph.

Week 3

Technology

  • Distinguish relational, key-value, document, and in-memory data stores and match each to a workload pattern.

  • Summarize the trade-offs among availability, durability, and cost for managed database replication and backup options.

  • Explain how elasticity and auto-scaling policies respond to demand changes, including scale-out versus scale-up.

  • Identify which services support decoupled, event-driven designs and describe one queue-based workflow end to end.

Your checkpoint

A one-page decision guide that maps five workload scenarios to a recommended database and compute combination with reasons.

Week 4

Security and Compliance

  • Define the identity and access management building blocks (users, groups, roles, policies) and write a policy that grants least-privilege read access to one storage bucket.

  • Explain the difference between identity-based and resource-based policies and when each applies.

  • List the mechanisms for protecting data at rest and in transit and state which are enabled by default versus opt-in.

  • Describe how logging, auditing, and monitoring services work together to detect unauthorized activity.

Your checkpoint

A written least-privilege policy example with a paragraph explaining each statement and the risk it mitigates.

Week 5

Security and Compliance

  • Break down the shared responsibility model for a managed database, a serverless function, and a virtual machine, listing who owns what in each case.

  • Summarize the categories of compliance programs and how to determine which apply to a given workload.

  • Explain how network isolation constructs (virtual networks, security groups, and network access control lists) differ in scope and statefulness.

  • Describe encryption key management concepts including key rotation and separation of duties for key administration.

Your checkpoint

A comparison matrix of the shared responsibility split across three service models, plus a 150-word summary of compliance considerations.

Week 6

Security and Compliance & Cloud Concepts

  • Identify common threat vectors against cloud workloads and map each to at least one mitigating control.

  • Explain the principle of least privilege as applied to both human and machine identities, with an example of each.

  • Define the core cloud economics concepts: capital versus operational expenditure, economies of scale, and total cost of ownership.

  • Describe the pillars of a well-architected framework and give one design question per pillar.

Your checkpoint

A threat-to-control mapping table with at least eight rows and a short cloud economics summary contrasting on-premises and cloud spending.

Week 7

Billing and Pricing & Cloud Concepts

  • Distinguish the major pricing models (on-demand, reserved capacity, spot, and savings plans) and state when each is appropriate.

  • Explain how data transfer, storage tiers, and request counts each contribute to a monthly bill.

  • Calculate an estimated monthly cost for a small two-tier application using published pricing inputs and show your arithmetic.

  • Describe cost governance practices such as budgets, tagging, and rightsizing, and explain how each reduces spend.

Your checkpoint

An itemized cost estimate worksheet for a sample workload with a written recommendation for at least two cost optimizations.

Week 8

Cloud Concepts & Security and Compliance & Technology & Billing and Pricing

  • Review every domain's weak spots by re-reading your own notes and flagging the five concepts you still cannot explain aloud.

  • Explain each flagged concept out loud in under two minutes without notes, then rewrite any that falter.

  • Complete a timed 60-question mixed practice set and categorize every miss by domain.

  • Build a one-page final review sheet of formulas, comparisons, and responsibility boundaries to consult in the last 24 hours.

Your checkpoint

A scored practice exam log with per-domain accuracy percentages and a one-page final review sheet.

Milestones

Week 2: Can you name and categorize at least 20 AWS services and explain the global infrastructure model from memory?

Week 4: Can you write a valid least-privilege policy from scratch and explain identity-based versus resource-based policies without notes?

Week 6: Can you correctly assign ownership under the shared responsibility model for three service types and map five threats to controls?

Week 8: Score at least 80 percent on the timed mixed practice set with no domain below 70 percent accuracy.