PCAM study guide
PCAM · Work through your exam, one topic at a time.
The Professional Cloud Architect Master (PCAM) is an advanced, vendor-neutral credential aimed at architects who already design cloud estates and now need to prove they can do so at scale, under governance, and with defensible trade-offs. It suits lead architects, platform and landing-zone owners, and senior consultants who translate business requirements into multi-account or multi-project topologies, then defend those decisions to security, finance, and engineering stakeholders. The PCAM study guide has 8 sections and about 3,670 words.
01Cloud Architecture Design and Planning
This domain tests whether you can turn a business ask into a defensible design: capturing non-functional requirements, mapping them to architecture patterns, and documenting the trade-offs you accepted. Scenarios usually give you constraints - budget, latency, residency, a legacy dependency - and score whether your response honours all of them, not whether you named the newest service.
455 words, about 2 min02Cloud Infrastructure and Networking
This domain covers VPC topology, IP planning, routing, hybrid connectivity, and how traffic actually leaves your environment. Questions typically present a topology that works at small scale and ask what breaks at ten times the size, or hand you a host count and check whether you can size subnets correctly.
482 words, about 2 min03Security, Identity, and Compliance
This domain tests identity as the primary control plane, encryption and key custody, guardrails versus approval gates, and how you produce audit evidence without rebuilding controls per workload. Expect scenarios about a compromised credential, a public bucket, or an auditor asking who accessed what and when.
466 words, about 2 min04Data Management and Storage Architecture
This domain covers selecting storage by access pattern, planning lifecycle and retention, and protecting data against deletion as well as disaster. Items often hinge on arithmetic: a large dataset with rare access, a retention obligation, and a budget that rules out the obvious choice.
479 words, about 2 min05Application Modernization and Migration
This domain covers portfolio assessment, the migration strategies (the R's), wave planning, modernization patterns, and the mechanics of cutover. Scenarios usually impose a deadline, a legacy dependency, and a zero-downtime constraint, then check whether your plan is incremental and reversible.
447 words, about 2 min06Reliability, Resilience, and Disaster Recovery
This domain covers service level objectives and error budgets, failure-domain analysis, the DR pattern ladder, and - critically - how you prove any of it works. Scenarios typically state an RTO and RPO with a budget constraint and expect you to pick the cheapest pattern that satisfies both.
457 words, about 2 min07Cost Optimization and Performance Engineering
This domain treats cost as an engineering metric with unit economics, and performance as a design decision that usually lowers cost. Items ask you to interpret a bill, choose commitment instruments correctly, or explain why a stable workload still costs too much.
443 words, about 2 min08Operations, Automation, and Governance
This domain covers how changes reach production safely, how you know the system is healthy, and how an organization stays compliant as it scales. Items describe a team wanting more deployment autonomy or a drift incident and ask what control actually prevents the failure.
441 words, about 2 min