Professional Cloud Architect: architecture and operations
Prepare for Professional Cloud Architect through architecture, data, networking, security, migration, and operations: eight lessons and 58 explained decisions.
Objectives and progression
Eight lessons, 50 questions, and eight fictional cases cover all six domains through technical and business decisions. Internal assessment of 32 decisions in 60 minutes using course items. Initial coverage without executable labs or exhaustive treatment of every product and objective. Based on Google’s currently linked standard guide, inspected 2026-09-30; edition date not stated. Approximate weights: 25/17.5/17.5/15/12.5/12.5. Standard exam: 50–60 items in 120 minutes, in English or Japanese. Renewal has a different format. A public numerical passing threshold is unconfirmed.
Audience: Cloud architects, engineers, technical managers, and APS professionals involved in migrations and RUN.
Prerequisites: Networking, IAM, application, and data knowledge; practical Google Cloud experience recommended. The certification defines no formal prerequisite.
360 estimated study minutes
- Turn business objectives into criteria for comparing architectures.
- Distinguish availability, recovery, event identity, and access patterns.
- Explain network paths, delegation, and scaling limits before cutover.
- Combine controls with explicit scope and demonstrate enforcement.
- Connect technical changes to acceptance, complete costs, and RUN autonomy.
- Build implementation and recovery criteria that include data and consumers.
- Measure experience and collect evidence to locate regressions.
- Demonstrate complete recovery with boundaries, decisions, and reconciliation.
Modules
- Requirements, costs, and platform selection
- Data, resilience, and events
- Networking, provisioning, and capacity
- Identity, perimeters, and keys
- Migration, FinOps, and governance
- Implementation, canary, and persistent state
- SLI, SLO, and investigation
- Recovery, exercises, and RUN
Continue learning
- Associate Cloud Engineer
- Cloud Digital Leader
- AWS Certified Solutions Architect Professional
- Technical Project Manager
- Production Support L3
References and version
Current linked standard guide; edition date unconfirmed (2026-09-30 inspection)
- Google Cloud certification FAQs · 2026-09-30
- Well-Architected Framework · 2026-09-30
- Storage classes · 2026-09-30
- BigQuery overview · 2026-09-30
- Cloud SQL overview · 2026-09-30
- Pub/Sub overview · 2026-09-30
- Dataflow overview · 2026-09-30
- Gemini Enterprise Agent Platform overview · 2026-09-30
- Migration planning · 2026-09-30
- Cloud Run overview · 2026-09-30
- GKE overview · 2026-09-30
- Spot VMs · 2026-09-30
- Apigee overview · 2026-09-30
- IAM overview · 2026-09-30
- Model Armor overview · 2026-09-30
- Cloud Billing budgets · 2026-09-30
- Resource hierarchy · 2026-09-30
- Service level objectives · 2026-09-30
- Disaster recovery planning · 2026-09-30
- Professional Cloud Architect certification · 2026-09-30
- Professional Cloud Architect exam guide · 2026-09-30
- VPC Network Peering · 2026-09-30
- Shared VPC · 2026-09-30
- VPC Service Controls · 2026-09-30
- Workload Identity Federation · 2026-09-30
- Cloud SQL PostgreSQL high availability · 2026-09-30
- Cloud SQL regional disaster recovery · 2026-09-30
- Private Service Connect · 2026-09-30
- Cloud Interconnect overview · 2026-09-30
- Cloud KMS key rotation · 2026-09-30
- Binary Authorization overview · 2026-09-30
- Cloud Deploy canary strategy · 2026-09-30
- Pub/Sub exactly-once delivery · 2026-09-30
- Bigtable schema design · 2026-09-30
- Cloud Run service autoscaling · 2026-09-30
What you will explore
0 / 8Requirements, costs, and platform selection
Turn business objectives into criteria for comparing architectures.
Data, resilience, and events
Distinguish availability, recovery, event identity, and access patterns.
Networking, provisioning, and capacity
Explain network paths, delegation, and scaling limits before cutover.
Identity, perimeters, and keys
Combine controls with explicit scope and demonstrate enforcement.
Migration, FinOps, and governance
Connect technical changes to acceptance, complete costs, and RUN autonomy.
Implementation, canary, and persistent state
Build implementation and recovery criteria that include data and consumers.
SLI, SLO, and investigation
Measure experience and collect evidence to locate regressions.
Recovery, exercises, and RUN
Demonstrate complete recovery with boundaries, decisions, and reconciliation.