Google Professional Cloud Architect Exam Guide (2026)

If you can say whether a workload should sit on Compute Engine, Google Kubernetes Engine, or Cloud Run, whether the data is an object library or a relational ledger, and whether the case study is buying 99.9 percent availability or a human-in-the-loop catalog review, you are reading the right outline.

Professional Cloud Architect is the Google Cloud certification for people who design, develop, and manage solutions that have to stay secure, scalable, efficient, cost-effective, and highly available while they still serve a business objective. The Professional Cloud Architect certification page is the source for length, fee, question count, case-study share, validity, and recommended experience. The Professional Cloud Architect exam guide is the source for the six scored sections, the product names used on the sitting, and the four official case studies.

The sitting is live. There is no prerequisite exam. Google recommends 3 or more years of industry experience, including 1 or more years designing and managing solutions on Google Cloud. This guide is for people scheduling the current standard exam, people who already hold the title and need the current task list, and people moving from Associate Cloud Engineer work into the architect role.

Who this exam is for

Take it as a map of the Google Cloud architect job the current exam guide scores. The audience profile asks for someone who can turn a business objective into a solution that uses Google Cloud, then stay with that solution through migration, deployment, orchestration, and optimization. The same profile expects fluency with common open-source technologies and with software development methods for multitiered distributed applications that cross legacy, multicloud, or hybrid environments.

Familiarity with the Google Cloud Well-Architected Framework is a named requirement, not optional reading. The framework's six pillars are operational excellence, security, reliability, performance optimization, cost optimization, and sustainability. The exam guide says those pillars are woven through the objectives and should guide architectural decisions. Section 6 later scores the operational excellence pillar by name. A candidate who can name products but cannot say which pillar a recommendation serves will lose items that look like product questions.

The responsibility list on the certification page is concrete. Design and plan a cloud solution architecture. Manage and provision the cloud solution infrastructure. Design for security and compliance. Analyze and optimize technical and business processes. Manage implementations of cloud architecture. Ensure solution and operations excellence. Those six verbs are the six scored sections. The sitting punishes people who treat the role as a catalog of services and rewards people who can read a constraint and pick the control that matches it.

There is no required prior certification. The recommended experience is the gap check. If projects, Identity and Access Management roles, virtual private clouds, and gcloud are still a catalog rather than weekly work, sit Associate Cloud Engineer first. The architect sitting assumes those controls and then asks which design to recommend. If the goal is the language of Google Cloud rather than the design of it, Cloud Digital Leader is the closer match. Service definitions, shared responsibility, and product families belong there. They appear here as the vocabulary inside a design, not as the whole job.

Skip it if the work you actually want is deploying someone else's design day to day without owning the compute shape, the data model, or the recovery objective. That job is Associate Cloud Engineer. Skip it if the work you actually want is hardening identity, keys, and perimeters without owning the solution tradeoff across pillars. Those controls appear on this outline as the security half of the same design. They are scored here as recommendations, not as the entire security-engineer sitting. Skip it if the stem you actually want is a failed deploy and a log line. Troubleshooting appears in section 4 as a process, not as the whole exam.

The current professional architect credential Google publishes for this role is this one. Use this page for the Professional Cloud Architect task list. Use the Google Associate Cloud Engineer exam guide when the stem is an operator control that happens to sit on a workload. Use the Google Cloud Digital Leader exam guide when the stem is still vocabulary. Sibling architect readings of the same kind of decision are the AZ-305 exam guide and the SAP-C02 exam guide. The products change. The habit of reading the constraint before the logo does not.

Exam shape and how a pass is decided

The current exam guide publishes six sections and marks each weight as an approximation.

Do the arithmetic on those approximations before building a plan. The six midpoints total 100%. Google still prints a tilde on every band, so no exact split exists to memorize. Section 1 sits alone at the top. Sections 2 and 3 share the next band. Section 4 sits in the middle. Sections 5 and 6 share the lightest band. Any study plan that gives six equal weeks overweights implementation and operations and underweights design.

The logistics come off the certification page. The standard sitting is 2 hours. The format is 50 to 60 multiple choice and multiple select questions. Languages are English and Japanese. The registration fee is 200 USD, and tax where applicable. Delivery is online-proctored from a remote location or onsite-proctored at a testing center. Prerequisites are none. Validity for the professional certification is 2 years.

Case studies are not a seventh section. They cut across the six. Each standard exam includes 2 of the 4 official case studies. Case study questions make up 20 to 30% of the exam. They assess the ability to apply knowledge to a realistic business situation. The case studies stay on a split screen during the sitting. A candidate who never opens the four official PDFs is leaving a fifth to a third of the exam to guesswork.

Scoring is the part most third-party pages get wrong. The certification page and the exam guide do not publish a numeric passing score, a scaled range, or a percent hedge. Google Cloud Certification Exam Policies and Exam Terms and Conditions say that if you pass an Exam, you will receive a digital certificate after Google has validated your score. That is the official pass language. This guide does not invent a 700 mark or a 70 percent story for a vendor that did not publish one.

The same terms page is the source for retakes and for how long the credential lasts. Associate and Professional exams allow a maximum of four attempts in a two year period. After a failed attempt, the wait is 14 days. After a second failed attempt, the wait is 60 days. After a third failed attempt, the wait is 365 days before a fourth attempt. Each attempt requires payment. A Professional Certification is valid for two years from the date of issue. Passing a Professional exam during renewal extends validity for two years from the date of passing.

Renewal has three official doors. The standard 2 hour exam. A 1 hour renewal exam of 25 questions with 1 generative AI case study that makes up 90 to 100% of that shorter sitting, at 100 USD and tax where applicable. Designated courses or skill badges in Google Skills, which the certification page lists with a 1 year validity. Professional renewal eligibility on the terms page begins 60 days before expiration. The renewal FAQ PDF also names a window that runs 60 days before expiration and 30 days after. After that window closes, the path back is the standard exam.

Two more details change how the sitting is taken. Google may update exam content at any time to reflect changes to Google Cloud technology. The certifications hub says exams are being updated for product updates announced at Google Cloud Next '26, including Gemini Enterprise Agent Platform. The product names that matter are the names on the current exam guide, not the names on last year's notes.

What the current outline changed

The exam guide does not publish a Microsoft-style change-log table. The official delta is the set of names the current pages print.

The certification page opens with a banner. The exam was updated to reflect recent branding changes. The exam guide is the place to review the product names used on the exam. That sentence is the reason Cloud Functions notes written against the old name are already stale. The current guide says Cloud Run functions.

The certifications hub is more specific about the product wave. Exams are being updated to reflect product updates announced at Google Cloud Next '26, including Gemini Enterprise Agent Platform and Google Cloud's data and analytics stack. The current Professional Cloud Architect guide already names Gemini Cloud Assist, Gemini Enterprise Agent Platform, Agent Platform Pipelines, AI Hypercomputer, Model Garden, Gemini models, Model Armor, and Sensitive Data Protection. Section 2 now spends two full task groups on Agent Platform workflows and on prebuilt AI APIs. A study plan that treats generative AI as a side topic is studying last year's job.

The case studies moved with the same wave. The current exam guide names Altostrat Media, Cymbal Retail, EHR Healthcare, and KnightMotives Automotive. The PDFs are version 6.1. Several of those businesses use Google Cloud generative AI. The exam guide says so in the case study introduction. Older company names do not appear on the current guide or on the current certification page, so this guide does not resurrect them.

Validity and renewal changed the calendar around the sitting even when the six section names stayed close. Professional Cloud Architect lasts 2 years. A 1 hour renewal exam and a Google Skills course path sit beside the standard exam. Foundational and Associate credentials last 3 years on the same terms page. Mixing those clocks is how people schedule the wrong renewal door.

Three things follow for anyone holding older material.

The six section names are still the spine. Design, provision, security, processes, implementation, and operations excellence are still the scored map. Notes organized on those six headings are still structurally useful.

The product names inside those headings are not. Cloud Run functions, Gemini Cloud Assist, Agent Platform, Model Armor, and Migration Center are current names. A flashcard that still says Cloud Functions as the only functions product is already wrong on the branding the banner warned about.

The case studies are not optional color. They are 20 to 30% of the standard sitting and 90 to 100% of the renewal sitting. Opening the four official PDFs is part of studying section 1, not a reward after the product list is done.

How a compute shape gets picked

Section 1 is about 25%, the heaviest band, and the same discriminator shows up in migration stems, application-architecture stems, and case-study stems as often as in compute ones. Section 2 then asks the candidate to provision the shape they just recommended.

The exam guide maps compute needs to platform products and names Google Kubernetes Engine, Cloud Run, and Cloud Run functions. It then names compute resources such as spot VMs, custom machine types, and specialized workloads. Select a managed container runtime environment is the Architecture Center page that turns those names into a decision. Unless the team specifically wants or needs Kubernetes, that page tells the architect to consider serverless first. If the workload is a poor fit for serverless, the next managed stop is GKE Autopilot. Compute Engine and GKE Standard sit on the less-managed side of the same diagram, where the team still owns virtual machines or cluster nodes.

Compute Engine is the guest-operating-system path. The team picks the machine type, the disk, the image, and the kernel behavior. Custom machine types and spot VMs live here. Spot VMs are the volatility option the exam guide names against standard VMs. A stem that wants full control of the operating system, a line-of-business installer that cannot be containerized, or a specialized machine that only exists as a virtual machine, is a Compute Engine stem. Google Cloud VMware Engine is the named path when the estate is already VMware and the network configuration has to follow that estate into Google Cloud.

Cloud Run is a serverless platform that runs source or a container on Google's infrastructure. What is Cloud Run and the Architecture Center page agree on the two deployment models. Cloud Run services respond to web requests. Cloud Run jobs run background tasks and then exit. Cloud Run can scale to zero. Billing is pay-per-use, rounded to the nearest 100 milliseconds on the GKE comparison page. A stem about a stateless API, a website, or a batch job that should cost nothing when idle is Cloud Run. A stem about a long-running process that needs a persistent local disk or a custom kernel is not.

Cloud Run functions is the current name for the single-purpose event handler. The exam guide uses that name in section 1.3 and again when it talks about AI Hypercomputer and Agent Platform. Altostrat Media already runs Cloud Run functions for transcoding, metadata extraction, and personalized recommendations. A stem about one event, one bucket notification, or one Pub/Sub message that should run and disappear is Cloud Run functions. Putting that work on a GKE Deployment because the rest of the platform is already on GKE is the trap when the stem never asked for the Kubernetes API.

GKE is the Kubernetes path. GKE and Cloud Run draws the line in one table. GKE supports stateless and stateful applications and is the answer when the team needs the Kubernetes API, custom networking, or deep cluster control. The team still manages cluster shape, node pools or Autopilot configuration, and upgrades. Autopilot is the default and recommended mode on the Architecture Center page. Standard is the mode that scales to very large node counts and keeps more of the node in the team's hands. A stem that asks for kubectl, a StatefulSet, a custom network policy, or a sidecar mesh is GKE. A stem that wants scale-to-zero containers without cluster operations is Cloud Run.

Two more facts change how those answers are used. The same container image can run on GKE and on Cloud Run. The Cloud Run Admin API is designed to be compatible with the Kubernetes API. A complete solution can therefore include both, and the GKE comparison page describes that hybrid on purpose. A retail front end on Cloud Run and a stateful inventory service on GKE is a documented pattern, not a contradiction. The second fact is specialized hardware. GPUs and TPUs appear on the exam guide under AI Hypercomputer. Those accelerators attach to the compute shape that can take them. They do not turn every AI stem into a GKE stem.

Read the constraint the stem is buying. An existing server that must move with the guest intact is Compute Engine. A stateless container the team will only deploy is Cloud Run. An event that should run and disappear is Cloud Run functions. A container whose team must keep the Kubernetes API, or a workload that must stay up as a stateful cluster service, is GKE. A VMware private cloud that must keep vCenter is Google Cloud VMware Engine.

How a data store gets picked

Storage and data sit inside section 1.3 and again in section 2.2. Most of those questions reduce to one skill. Name whether the stem is about an object, a file, a relational ledger, a wide-column operational store, a document, or a warehouse. Then name the service that implements that model.

Design an optimal storage strategy for your cloud workload sorts Google Cloud storage into block, file, and object. Block storage is Persistent Disk, Hyperdisk, and Local SSD, and it lives with Compute Engine and GKE nodes. File storage is Filestore for NFS, NetApp Volumes when the protocol is NFS or SMB, and Managed Lustre for AI and high-performance computing. Object storage is Cloud Storage. The exam guide's own storage bullet says object, file, and databases. Read the format before reading the brand.

Cloud Storage is the object store with no lower or upper capacity limit on the storage-advisor page. Storage classes pick the cost curve. Standard has no minimum duration and no retrieval fee, and it is the class for data that is read often, including websites, streaming video, and objects colocated with GKE or Compute Engine. Nearline has a 30 day minimum and a retrieval fee, and it is the class for data read about once a month. Coldline has a 90 day minimum and is the class for data read about once a quarter. Archive has a 365 day minimum, is the lowest-cost class, and still returns data in milliseconds. Autoclass is the switch when access frequency is unknown. Rapid storage is the zonal class for intensive reads and writes and only exists on Rapid Bucket. Altostrat's media library is a Cloud Storage problem before it is a GKE problem. A stem that wants last year's documentaries to stay cheap but still open quickly is Archive, not a Filestore share.

Filestore is the managed NFS server for Compute Engine and GKE. The storage-advisor page names it for lift-and-shift file systems, shared configuration, and centralized logs. A stem about an application that mounts a path and breaks if that path becomes an object API is Filestore. Putting that tree in Cloud Storage because objects are cheaper is the trap.

Cloud SQL is the managed MySQL, PostgreSQL, or SQL Server service. Cloud SQL handles backups, high availability and failover, encryption, connectivity, storage, export and import, replication, maintenance, monitoring, and logging. Each instance is a virtual machine with a persistent disk. High availability adds a standby virtual machine in another zone. Cymbal Retail and EHR Healthcare both still run MySQL and Microsoft SQL Server. A stem about lifting those engines with the least rewrite is Cloud SQL. A stem that names a SQL Server feature the team refuses to give up is still Cloud SQL, not Spanner.

Spanner is the globally distributed relational database with horizontal scale and strong consistency. The product page contrasts it with other relational databases that scale vertically and fail over with downtime, and with non-relational stores that give up strong consistency. Availability is listed up to 99.999%. Configurations include single-region, dual-region, and multi-region. SQL dialects are PostgreSQL and Google SQL. A stem about a checkout ledger that must take writes in more than one region without the team sharding by hand is Spanner. A stem about a regional reporting database that already runs on PostgreSQL and must move this quarter is Cloud SQL.

Firestore is the document model. Bigtable is the wide-column operational store. BigQuery is the warehouse. Altostrat already uses BigQuery to study audience behavior. That does not make BigQuery the store for a product catalog or a patient record. A stem about interactive analytics over large analytical tables is BigQuery. A stem about a mobile client that syncs documents is Firestore. A stem about high-throughput operational reads and writes on a wide key is Bigtable. Cymbal's MongoDB catalog is a document problem first. The exam will tell you whether the constraint is the document model, the relational join, or the cache in Redis.

Data protection is its own bullet in section 2.2. Backup and recovery sit next to retention, lifecycle, growth planning, and access management. Cloud Storage lifecycle policies and Autoclass are how an object library ages. Cloud SQL backups and high availability are how a regional ledger survives a zone. Spanner's regional configuration is how a global ledger survives a region. Mixing those three answers is how the question is lost. A deleted object that must come back from last night is a backup. A zone that failed and must not take the database down is high availability. A region that went dark and must keep serving writes is a multi-region database design, not a colder storage class.

How a case study gets read

Each standard exam includes 2 of the 4 official case studies. The PDFs are on the exam guide page. The companies are Altostrat Media, Cymbal Retail, EHR Healthcare, and KnightMotives Automotive. Do not study a fifth company a dump site invented.

The method is the same on every PDF. Read the company. Read the existing environment. Read the business requirements. Read the technical requirements. Read the executive statement last, because it names the priority the options will try to distract you from. Then pick the control that satisfies the constraint the PDF already wrote down.

Altostrat is already on Google Cloud for the platform that matters. GKE holds the content system. Cloud Storage holds the library. BigQuery holds the warehouse. Cloud Run functions already do the event work. The remaining work is hybrid connectivity for ingest, a cheaper class for media that is no longer hot, CI/CD for containers, and generative AI that can be audited and explained. A stem that offers to rebuild the library on Filestore is fighting the PDF. A stem that offers an AI feature the PDF asked to be explainable, with no audit path, is fighting the technical requirements.

Cymbal is a modernization story with a human still in the loop. The catalog is messy, the web app queries relational databases by name and category, and agents type orders by hand after an IVR transfer. Generative AI is in the solution concept for attributes, descriptions, images, and conversational discovery. The technical requirements still demand a review UI so associates can approve, reject, or edit suggestions before the catalog updates. A stem that publishes generated content with no review step is fighting the PDF. A stem that replaces the whole relational catalog with a warehouse because BigQuery is on the architect's flashcards is fighting the existing environment.

EHR Healthcare is the availability and compliance story. The software is a service for medical offices, hospitals, and insurance providers. One colocation lease is about to expire. Many customer-facing apps are already containerized. The legacy insurance integrations stay on-premises for years. The business requirements ask for a minimum 99.9% availability on customer-facing systems, lower latency, regulatory compliance, and centralized visibility. The executive statement blames misconfiguration, weak capacity, and ignored alerts. A stem that moves the insurance interfaces this quarter is fighting the PDF. A stem that treats monitoring as an email list is fighting the same PDF. A stem that ignores health-record privacy is fighting section 3.2 and the company overview at the same time.

KnightMotives Automotive is the hybrid, privacy, and dealer-tooling story. The BEV fleet already has a modern in-vehicle experience. Hybrid and ICE vehicles do not. The online build-to-order path is unreliable. Supply chain still sits on a mainframe. Dealers have no budget for new equipment. Business requirements name EU data protection, past breaches, data monetization, and employee upskilling. Technical requirements name rural connectivity, plant-to-headquarters networks, a hybrid cloud strategy, and gradual legacy modernization. A stem that lifts the mainframe in one weekend is fighting "gradually." A stem that stores European driver data in a region the PDF would not accept is fighting the privacy line. A stem that ignores dealers because the fun part is autonomous-vehicle training is fighting the executive statement about dealer success.

The renewal exam uses a shorter map. Its guide names only Cymbal Retail and Altostrat Media, uses one of them, and makes that case study 90 to 100% of the shorter sitting. First-time candidates still study all four. The two generative AI companies are not a reason to skip EHR Healthcare or KnightMotives Automotive on the standard exam.

How to study the current blueprint

Order the weeks by the weight bands and by the case-study share, not by the order the products appear in a catalog.

Week 1. Designing and planning, the band near 25%. Draw one workload three ways. Put the same API on Compute Engine, on Cloud Run, and on GKE, and write down which operating-system task, which scale-to-zero behavior, and which Kubernetes API each one removed. Deploy one Cloud Run function on a bucket event and confirm it is not a GKE Deployment. Create a Cloud Storage bucket and put the same object in Standard, Nearline, Coldline, and Archive. Create Cloud SQL for one engine Cymbal still runs, then open the Spanner product page and write down the constraint that would have forced the other choice. Finish the week on the Well-Architected pillars. For each recommendation, name the pillar it serves. Use Gemini Cloud Assist only as far as the exam guide names it, as a design and operations assistant, not as a substitute for the outline.

Week 2. Provisioning and security, the two bands near 17.5%. Build a shared network story. Create a VPC, a Cloud VPN path or the Interconnect documentation equivalent, and a Private Service Connect endpoint, and write down which one is hybrid, which one is private service access, and which one is a shared host project. Put an Application Load Balancer in front of a Cloud Run service and a passthrough Network Load Balancer in front of a Compute Engine instance group, using Choose a load balancer. Then build the hierarchy. Create a folder under an organization, hang two projects under it, and assign one IAM role and one organization policy at the folder so both projects inherit. Store a customer-managed key in Cloud KMS. Turn on a VPC Service Controls perimeter around a Cloud Storage bucket. Use Identity-Aware Proxy in front of one application and write down why that is not the same control as a firewall rule. Open Model Armor and Sensitive Data Protection long enough to say which one sits on a model prompt and which one sits on the data.

Week 3. The four case studies, and the data the PDFs already chose. Print or split-screen the four official PDFs. For each company, write one page that lists the existing products, the one business number or legal constraint, and the one thing the executive statement refuses to trade away. Then map those lines onto week 1 and week 2. Altostrat is GKE, Cloud Storage classes, hybrid ingest, and explainable AI. Cymbal is catalog generation with a review step, conversational discovery, and a cheaper call center. EHR Healthcare is 99.9 percent, containers that span environments, a connection that does not move the insurance interfaces, and alerts that someone actually sees. KnightMotives Automotive is hybrid plants, EU privacy, dealer tooling, and a security program after a breach. Spend the second half of the week on Migration Center as the named assessment product in section 1.4, and on a migration plan that includes license impact, dependency planning, and a test, because those are the bullets the guide actually prints.

Week 4. Processes, implementation, and operations, the remaining 40%, and a full review. Write a short software delivery story that includes a source repository, a Cloud Build or other pipeline, Terraform or another infrastructure-as-code tool the exam guide names, and a Cloud Deploy or release step. Call one Google API from Cloud Shell with gcloud, gsutil, and bq so those three clients are not theoretical. Put Apigee in front of an API only when the stem is API management. Create a Cloud Monitoring dashboard and an alerting policy that is not email-only, because EHR Healthcare already told you ignored email is a failure mode. Re-read section 6.1 and the operational excellence pillar. Then sit with the exam guide and, for each bullet, name the product, the pillar, and the case study that would have forced that product.

Take the official sample questions linked from the certification page and walk the exam tutorial at least once before using this outline against a clock. The sample set exists so the question format costs nothing on the timer.

Traps that look like easy elimination

Architect items rarely give one plausible answer and three absurd ones. They give two controls that both sound correct and one detail that picks between them.

• There is no prerequisite certification. Recommended experience is still 3 or more years, including 1 or more years on Google Cloud. Showing up with only vocabulary from Cloud Digital Leader is how section 1 is lost.
• The Well-Architected Framework is six pillars, including sustainability. A stem about pillar tradeoffs is Well-Architected. A stem about a folder and a project tree is the resource hierarchy.
• Organization, folders, and projects inherit IAM and organization policy downward. A policy on the organization hits every project. A project belongs to the organization, not to the person who created it.
• Serverless first is the Architecture Center default when Kubernetes is not required. GKE is the answer when the stem needs the Kubernetes API, a stateful cluster pattern, or custom cluster networking.
• Cloud Run scales to zero and bills per use. GKE bills for the cluster. An idle API that must cost nothing is Cloud Run. An API that must keep a warm cluster of sidecars is GKE.
• Cloud Run functions is the current functions name. Cloud Functions notes that never mention the new name are already off the branding banner.
• Spot VMs are reclaimable capacity. Standard VMs are the path when the stem cannot accept preemption.
• Cloud SQL is the managed engine for MySQL, PostgreSQL, or SQL Server. Spanner is the global relational store with horizontal writes. JSON in Cloud Storage does not make that bucket a document database.
• Standard, Nearline, Coldline, and Archive are duration and access trades, not durability trades. Archive still opens in milliseconds. A stem that says "cold" and "must wait hours" is not describing Cloud Storage Archive.
• Application Load Balancers handle HTTP and HTTPS. Proxy Network Load Balancers handle TCP. Passthrough Network Load Balancers keep the client IP and can take UDP. A global external Application Load Balancer is not the answer to a regional compliance stem that must terminate TLS in one region.
• Cloud VPN and Cloud Interconnect extend on-premises networks. Private Service Connect publishes or consumes a service privately. Shared VPC shares a host network across service projects. Those are three answers.
• Identity-Aware Proxy is application-level access. A VPC firewall is network-level access. Workload Identity Federation is how an external workload gets a Google token without a downloaded key.
• Model Armor sits on the model path. Sensitive Data Protection sits on the data. Securing AI is a scored bullet, not a slogan.
• EHR Healthcare keeps the insurance integrations on-premises. A migrate-everything answer is wrong on that PDF.
• Cymbal requires a human review step before generated catalog content goes live. A fully automatic publish is wrong on that PDF.
• Altostrat already has GKE, Cloud Storage, BigQuery, and Cloud Run functions. Re-platforming those four for no reason is wrong on that PDF.
• KnightMotives Automotive names EU data protection and a hybrid strategy. A single-region lift that ignores residency is wrong on that PDF.
• Case studies are 20 to 30% of the standard exam and appear on a split screen. Closing the PDF to save time is how those items are lost.
• Google does not publish a numeric passing score on the certification page or the exam guide. A third-party 700 or 70 percent figure is not official language for this sitting.

If deleting the scenario still lets you pick the answer from the service name, the question is easier than the live exam.

How this maps to CloudFluently

Start with the official material. The Professional Cloud Architect certification page carries the audience profile, the 2 hour timer, the 50 to 60 question format, the 20 to 30% case-study share, the 200 USD fee, the 2 year validity, and the three renewal doors. The Professional Cloud Architect exam guide carries the six sections, the product names, and the four case studies. The official case study PDFs are Altostrat Media, Cymbal Retail, EHR Healthcare, and KnightMotives Automotive. Exam Terms and Conditions explain what it means to pass an Exam, how long a Professional Certification lasts, and the 14 day, 60 day, and 365 day retake waits. The Well-Architected Framework is the pillar list the exam guide treats as a key requirement.

Professional Cloud Architect sits on top of Google Cloud vocabulary and Google Cloud operations, and that ground is already live here. Shared responsibility, product families, and the idea of a cloud bill are the Cloud Digital Leader study notes and the Cloud Digital Leader practice exam set. The GCP Digital Leader roadmap sequences that ground, and the Cloud Digital Leader exam guide is the first companion page. Projects, IAM, Compute Engine, Cloud Storage, VPC networks, and the operator form of GKE and Cloud Run are the Associate Cloud Engineer study notes and the Associate Cloud Engineer practice exam sets. The GCP Associate Cloud Engineer roadmap sequences that work, and the Associate Cloud Engineer exam guide is the operator companion.

The same architect decision on the other two clouds is already written in the same spine. Compute shape, data model, and continuity control on Azure are the AZ-305 exam guide. Multi-account networks, recovery objectives, and migration strategy on AWS are the SAP-C02 exam guide.

Work those until the vocabulary, the operator controls, and the architect habit are automatic, then use this page and the official exam guide for the architect-only skills: the compute shape, the data model, the network path, and the case-study constraint that holds them.

Frequently Asked Questions

What is the passing score for Professional Cloud Architect? Google does not publish a numeric passing score on the certification page or the exam guide. Exam Terms and Conditions say that if you pass an Exam, you receive a digital certificate after Google has validated your score.

How long is the exam and how many questions are there? The standard sitting is 2 hours with 50 to 60 multiple choice and multiple select questions. The renewal exam is 1 hour with 25 questions.

How much of the exam is case studies? Each standard exam includes 2 case studies, and those questions make up 20 to 30% of the exam. The four official companies are Altostrat Media, Cymbal Retail, EHR Healthcare, and KnightMotives Automotive. The renewal exam includes 1 case study that makes up 90 to 100% of that shorter sitting.

Is there a prerequisite? No. Google recommends 3 or more years of industry experience, including 1 or more years designing and managing solutions using Google Cloud.

How long does the certification last? A Professional Certification is valid for two years from the date of issue. Renewal is the standard exam, the 1 hour renewal exam, or designated Google Skills courses or skill badges. The Skills path is listed with a 1 year validity on the certification page.

Can I retake it if I fail? Associate and Professional exams allow four attempts in two years. The waits are 14 days after the first fail, 60 days after the second, and 365 days after the third. Each attempt is paid.

What changed on the current outline? The certification page says the exam was updated for branding. The current guide names Cloud Run functions, Gemini Cloud Assist, Gemini Enterprise Agent Platform, Model Armor, and the four case studies above. The certifications hub points at Google Cloud Next '26 product updates, including Gemini Enterprise Agent Platform.

Which section is heaviest? Designing and planning a cloud solution architecture is about 25%. Managing and provisioning, and designing for security and compliance, are about 17.5% each. Processes are about 15%. Implementation and operations excellence are about 12.5% each.

Does Google publish a 700 or 70 percent pass mark? No. That figure is not on the certification page, the exam guide, or the terms page opened for this guide.

How does this exam relate to Associate Cloud Engineer and Cloud Digital Leader? Cloud Digital Leader scores vocabulary. Associate Cloud Engineer scores the operator controls. Professional Cloud Architect scores the solution recommendation: the compute shape, the data model, the network path, and the case-study constraint. The official outline is the Professional Cloud Architect exam guide. Use Google for the task statements and the case study PDFs. Use this page for how those statements get picked, what the current names are, and how to sequence the blueprint.