GCP Prep
ProfessionalArchitectCloud EngineerSecurity

Professional Cloud Architect

Professional Cloud Architect assesses whether you can design, plan and manage a cloud solution architecture that meets business and technical requirements. It is the broadest and most respected exam in the programme, and the one that most rewards genuine production experience.

Study GuidePractice Test

Overview

This is the hardest widely-taken exam in the programme, and its difficulty is a different kind from Associate Cloud Engineer's. That exam asks whether you know the command. This one asks whether you would make the right call under conflicting constraints.

The exam includes long case studies — fictional companies with business goals, technical requirements, existing systems and executive statements. A substantial portion of questions attach to them. Learning to read these efficiently is a distinct skill worth practising on its own.

The most common failure mode is technically correct answers that ignore a stated business constraint. If the case study says the company has a small operations team, the answer that requires managing a Kubernetes cluster is wrong even when it works.

You need Associate-level fluency as a floor, not a target. Everything at that level is assumed; the exam spends its time above it.

Level
Professional
Exam length
120 minutes
Questions
50–60 multiple choice and multiple select
Registration fee
USD $200 (plus tax where applicable)
Valid for
2 years
Delivery
Online proctored, or onsite at a test centre
Recommended experience (official)
Google recommends 3+ years of industry experience, including 1+ year designing and managing solutions on Google Cloud.

Our difficulty rating

5/5

Our recommended preparation

10–16weeks

Difficulty and preparation time are GCP Prep's own editorial assessments, not official figures.

Who Should Take This Certification?

  • Senior engineers moving into architecture
  • Existing architects proving Google Cloud specifically
  • Technical leads who set direction across multiple teams
  • Consultants who design systems for clients

Skills Covered

  • Translating business requirements into technical architecture
  • Designing for high availability, disaster recovery and defined RTO/RPO targets
  • Security, compliance and multi-tenancy design
  • Migration planning from on-premises and other clouds
  • Cost modelling and optimisation across a solution
  • Reliability engineering, capacity planning and operational readiness
  • Reading a long case study and extracting the constraints that matter

Exam Topics

Weightings are shown only where they are officially published — we do not estimate them.

1.Designing and planning a cloud solution architecture

~24%
  • Turning business requirements into technical and non-functional requirements
  • Designing for availability, durability, scalability and elasticity
  • Network, storage and compute resource design across regions
  • Migration planning, including phased and hybrid approaches
  • Designing for future growth without over-engineering today

2.Managing and provisioning a solution infrastructure

~15%
  • Configuring network topologies including shared and peered VPCs
  • Provisioning storage and data systems appropriate to the workload
  • Configuring compute systems and autoscaling behaviour
  • Infrastructure as code and repeatable provisioning

3.Designing for security and compliance

~18%
  • Identity and access management design across an organisation
  • Resource hierarchy and organisation policy as guardrails
  • Data security: encryption, key management and data classification
  • Separation of duties and privileged access design
  • Meeting regulatory requirements including data residency

4.Analysing and optimising technical and business processes

~18%
  • Analysing and defining technical and business processes
  • Cost optimisation across compute, storage, network and licensing
  • Team and stakeholder management considerations
  • Change management and phased rollout strategies

5.Managing implementation

~11%
  • Advising development and operations teams on implementation
  • Interacting with services programmatically and via APIs
  • Testing strategy and validating a design against requirements

6.Ensuring solution and operations reliability

~14%
  • Monitoring, alerting and observability design
  • Deployment and release management strategies
  • Disaster recovery design against defined RTO and RPO
  • Incident response, post-mortems and continuous improvement

Preparation Roadmap

Our suggested order of study. Tick steps as you complete them — progress is saved in this browser.

Loading your progress…

Progress is saved in this browser

  1. Consolidate Associate-level fundamentals

    Compute, storage, networking and IAM must be automatic. If any of these still require thinking, fix that before anything else.

  2. Resource hierarchy and organisation design

    Folders, projects, organisation policy and how enterprises actually structure an estate. Heavily represented in scenarios.

  3. Advanced networking

    Shared VPC, VPC peering, hybrid connectivity, private access to services, and the full load balancing decision tree.

  4. Data architecture

    Choosing between relational, document, wide-column and analytical stores under real constraints — and designing the pipeline between them.

  5. Security and compliance design

    Encryption and key management, data classification, boundary controls, audit and the vocabulary of compliance regimes.

  6. Reliability, HA and disaster recovery

    Multi-zone versus multi-region, backup and restore strategies, and designing explicitly to an RTO and RPO target.

  7. Migration and modernisation

    Lift and shift, replatform, refactor. Data transfer options at different scales, and phased cutover strategies.

  8. Cost modelling

    Committed use and sustained use discounts, storage class economics, egress, and how to argue a cost position credibly.

  9. Case study practice

    Work the published case studies deliberately. For each one, write down the constraints that would eliminate an otherwise-correct answer.

  10. Timed mock exams

    Full-length, timed, without notes. Two hours of dense scenario reading is a stamina problem as much as a knowledge one.

Certification ready

Study Resources

Learning-hub topics that cover this certification's material, written by us.

Official documentation and training remain the authoritative source for exam content. Our material explains concepts in our own words and is designed to sit alongside it, not replace it.

Practice Questions & Mock Exam

We have 37 original questions relevant to this certification, each with an explanation of why the correct answer is correct and why every distractor is not.

Practice test

Work through questions at your own pace with immediate explanations.

Timed mock exam

Full-length, timed, with results and per-topic breakdown at the end.

Career Opportunities

Cloud Architect

Design systems and set technical direction. The certification is frequently a screening requirement for these roles.

Solutions Architect (pre-sales)

Design for customers during the sales cycle. Partner organisations often require this certification to maintain their status.

Principal / Staff Engineer

Cross-team technical leadership where breadth and trade-off judgement matter more than depth in one product.

Cloud Consultant

Advisory and migration work, where credibility with client stakeholders is part of the job.

Explore career resources

Frequently Asked Questions

Do I need Associate Cloud Engineer before Professional Cloud Architect?
It is not a formal prerequisite and you can register directly. In practice, Associate-level fluency is assumed throughout, so most people either hold it or have equivalent hands-on experience. Going straight to Architect with no platform experience is the most common cause of an expensive failed attempt.
How hard is Professional Cloud Architect really?
It is the hardest in the mainstream programme. The difficulty is judgement under conflicting constraints rather than obscure facts. Experienced engineers who have never designed a full system often find it harder than they expected.
How much time should I budget?
Ten to sixteen weeks for most people with relevant experience. If you are already architecting on Google Cloud daily, six to eight weeks of targeted revision can be enough.
How important are the case studies?
Very. A significant share of questions attach to them, and they are published in advance. Reading them cold during the exam wastes time you will need. Know the companies, their constraints and their stated goals before you walk in.
How long does the certification last?
Google publishes a two-year validity for Professional-level certifications. Confirm current recertification requirements on the official certification page before you plan around it.