Google Professional Cloud Architect Certification Guide

No other Google Cloud exam works quite like the Professional Cloud Architect (PCA). Alongside standard scenario questions, every sitting includes two full business case studies — drawn from a published pool of four — which together drive 20–30% of the questions you answer. The exam runs two hours, contains 50–60 multiple-choice and multiple-select questions, costs $200 plus applicable tax, and certifies at Google Cloud's Professional tier with a two-year validity period.

This guide is a working map of that exam and nothing else: its structure, its case-study mechanism, what its questions demand, what it costs over time, and how to organise a serious attempt at it. It deliberately avoids comparing the PCA with other certifications — for where it sits among Google's credentials, see our Google Cloud certifications overview.

The credential in brief

The Professional Cloud Architect certification is issued by Google Cloud on passing the exam of the same name — like all Google Cloud exams, it carries no exam code. It attests that you can design, plan and manage cloud solution architecture on Google Cloud: the role-level claim is architect, not operator.

Key facts, current as of 2026 and worth re-confirming on the official Professional Cloud Architect page before booking:

• 50–60 questions, multiple-choice and multiple-select, in 2 hours
• 2 case studies per exam, presented on a split screen, contributing 20–30% of questions
• $200 registration fee, plus tax where applicable; offered in English and Japanese
• No prerequisites — Google recommends 3+ years of industry experience including 1+ year designing and managing solutions on Google Cloud
• Delivered via Pearson VUE, online-proctored or at a test centre, booked through Google's CertMetrics portal
• Pass/fail only — no published passing score, provisional result on screen, confirmation within 7–10 days
• Valid for 2 years (Professional-tier certifications carry a shorter term than Google's three-year Foundational and Associate credentials)

Note the absence of prerequisites is real: you may sit the PCA without holding any other Google Cloud certification. The experience recommendation, however, is not decorative — this exam presumes you have made real architectural decisions and lived with their consequences.

How the case studies work — and how to use them

The case-study mechanism deserves its own section because it changes both the exam experience and your preparation.

Google publishes a pool of four fictional-company case studies with the exam guide. Each describes an organisation — its existing environment, business requirements, and technical requirements. In the exam, two of the four appear, and the questions tied to them open the case study on a split screen beside the question. You are not asked to recall the case study from memory; you are asked to apply it — to pick the architecture decision that satisfies that company's stated constraints.

This creates the single biggest preparation lever unique to the PCA: you can study a substantial slice of the exam in advance, in full detail, because Google hands you the source material. Working each case study before exam day means:

• Reading it the way a consulting architect reads a client brief: list the business requirements and technical requirements separately, then sketch the target architecture you would propose and note which Google Cloud services satisfy each requirement — and why the runner-up options fall short.
• Anticipating tension points. Case studies embed competing pressures (growth plans versus cost control, legacy systems versus modernisation goals). Exam questions live in exactly those tensions, so name them explicitly in your notes.
• Re-reading on a split screen mentally: in the exam you will not have time to re-digest a full case study per question. Familiarity beforehand turns each case-study question into a quick requirements lookup instead of a comprehension exercise.

Since only two of the four appear in your sitting and you will not know which in advance, prepare all four to the same standard. A structured way of working them into a study schedule is set out in How to prepare for the Google Professional Cloud Architect exam.

What the rest of the exam asks

The remaining 70–80% of questions are standalone scenarios spanning the design and management of cloud architecture. For the authoritative domain list, download the current exam guide from the official certification page — Google has updated the exam to reflect recent product branding changes, so the live guide outranks any third-party syllabus, including course materials that predate the renames.

Reading the guide as an experienced engineer, the pattern to internalise is that PCA questions sit one level of altitude above implementation. You are rarely asked how to perform a task; you are asked which approach a company in a given situation should take. Expect stems built around requirements — availability targets, compliance obligations, cost ceilings, migration constraints, organisational structure — with answer options that are all technically feasible. The scoring difference lies in matching the option to the stated requirements and to Google's recommended practices, not in spotting the one answer that "works".

Three habits that pay off across the whole paper:

1. Extract requirements before reading options. Underline (mentally, or on the whiteboard tool if available in your delivery format) each hard constraint in the stem. An option that violates any hard constraint is gone, however elegant.
2. Respect the boring answer. Where two options meet requirements, Google's recommended practice usually favours the managed, simpler, less operationally expensive choice over the clever one.
3. Mind multiple-select counts. Some questions require multiple answers; the instruction line states how many. Under time pressure, mis-counting selections is an unforced error.