☁️ Google Cloud Professional Cloud Architect - Exam-Prep
Home › Courses › Google Cloud Professional Cloud Architect - Exam-Prep

☁️ Google Cloud Professional Cloud Architect - Exam-Prep

Free exam-prep for Google Cloud Professional Cloud Architect (PCA), signed certificate $5. Learn the modules, pass the 10-question exam, EN/FR, no account.

Last updated: June 2026

For cloud engineers, solution architects, and IT pros preparing for Google's PCA exam — design, deploy, secure, and operate robust, cost-effective Google Cloud architectures with confidence. The course is organized into 8 modules, ending with a final exam (pass mark 70%). It is independent, free exam-preparation training — not an official or accredited review course.

What you'll learn

  • Designing and Planning a Cloud Solution Architecture
  • Designing for Scalability, Reliability, and High Availability
  • Managing and Provisioning the Cloud Solution Infrastructure
  • Designing for Security and Compliance
  • Analyzing and Optimizing Technical and Business Processes
  • Managing Implementations: Migration & CI/CD on Google Cloud
  • Solution & Operations Excellence: Monitoring and SRE
  • Case Studies, Trade-Offs, and Exam Strategy

Learning objectives

  • Translate business and technical requirements into a Google Cloud solution architecture aligned with the Well-Architected Framework.
  • Design scalable, reliable, and highly available systems using compute, storage, networking, and data services.
  • Provision and configure infrastructure with Infrastructure-as-Code, deployment automation, and managed services.
  • Apply security, identity, and compliance controls including IAM, encryption, VPC Service Controls, and regulatory requirements.
  • Optimize technical and business processes for cost, performance, and operational efficiency.
  • Plan and manage migrations, CI/CD pipelines, and the implementation of cloud architecture across teams.
  • Ensure operational excellence through monitoring, logging, SRE practices, reliability, and disaster recovery.
  • Analyze case-study scenarios and select trade-off-aware designs the way the real exam demands.

Course facts

Estimated study time
about 1.5 hours
Final assessment
50 questions · Pass mark 70%
Available in
English, Français
Price
Free. Optional verifiable certificate: $5
Last updated
Published by
AMAADOR ACADEMY

Course content

1. Designing and Planning a Cloud Solution Architecture

The architect's first job is not to choose a service — it is to translate business requirements into technical requirements, then into a defensible design. The exam relentlessly tests whether you can read a scenario, separate what the business wants from what an engineer assumes, and pick the option that satisfies the stated constraint at the lowest cost and risk. This chapter covers that translation discipline, the cloud design pillars, and the planning artifacts you must produce.

From business goals to technical requirements

Every design decision must trace back to a requirement. Requirements split into two families that the exam expects you to label correctly:

Non-functional requirements (NFRs) drive most architecture choices. A request for "five-nines" availability (99.999% = ~5 minutes downtime/year) eliminates single-zone deployments; "data must stay in the EU" forces region selection and rules out global multi-region writes. Always extract the NFR before naming a product.

Decision guide — availability targets:

SLADowntime/yrTypical pattern
99.9%8.8 hSingle region, multi-zone managed service
99.95%4.4 hRegional managed (e.g. regional load balancer + 2+ zones)
99.99%52 minMulti-zone with automated failover
99.999%5.3 minMulti-region active/active

2. Designing for Scalability, Reliability, and High Availability

Independent study guide — not affiliated with or endorsed by Google. Aligned to the published exam objectives for the Professional Cloud Architect.

Why this domain dominates the exam

A cloud architect is judged on whether a system stays up, recovers fast, and grows without a redesign. The exam tests three intertwined properties: scalability (capacity grows or shrinks with demand), reliability (the system does what it should, when it should), and high availability (HA) (it keeps serving despite component failures). You must translate business language — "99.9% uptime", "survive a zone outage" — into concrete topology and product choices.

Core definitions.Availability = % of time a service is usable. Reliability = probability it performs correctly over an interval. Durability = probability data is not lost (e.g. 11 nines for object storage). These are distinct: a service can be available but returning wrong data (unreliable), or reliable but offline (unavailable).

The availability math you must memorise

Nines map directly to allowed downtime. Expect a question that hands you an SLA and asks for the architecture, or vice versa.

3. Managing and Provisioning the Cloud Solution Infrastructure

Once an architecture is approved, the Cloud Architect must provision it reliably and repeatably, then manage it across networking, compute, storage, and data services. The exam tests whether you can pick the right primitive, wire it together securely, and operate it at scale without manual drift. This chapter walks the four pillars the body of knowledge emphasizes: networking, compute, storage, and infrastructure-as-code automation.

3.1 Networking: VPC design and connectivity

A Virtual Private Cloud (VPC) in Google Cloud is global; subnets are regional and span all zones in a region. This is a frequent exam trap: you do not create a subnet per zone. A single VPC can therefore connect resources across regions without VPN. Subnet IP ranges are RFC 1918 CIDR blocks and can be expanded but not shrunk.

Shared VPC vs VPC Peering. Use Shared VPC when one organization wants centralized network control: a host project owns the network and service projects attach to it (best for org-wide governance). Use VPC Peering to connect two independently administered VPCs (even across organizations) with non-transitive, private RFC 1918 routing.

4. Designing for Security and Compliance

Cloud security is a discipline of layered defense and least privilege. A Cloud Architect designs identity, network, data protection, and compliance controls so that a single failure never collapses the whole system. This chapter covers the body of knowledge the way certification exams frame it: identity-first design, the shared responsibility model, defense-in-depth, and mapping technical controls to regulatory obligations.

Shared Responsibility Model. The cloud provider secures the infrastructure (security of the cloud); the customer secures workloads, identities, and data (security in the cloud). Responsibility shifts with the service tier — IaaS pushes more onto you, SaaS pushes less. Exam trap: never assume the provider patches your OS or encrypts your application data by default.

Identity and Access Management (IAM)

IAM answers who can do what on which resource. The model binds members (users, groups, service accounts) to roles (bundles of permissions) at a resource hierarchy scope. Grant at the narrowest scope that works — project over folder, folder over organization.

5. Analyzing and Optimizing Technical and Business Processes

A cloud architect is not only a technical designer but a process engineer. The exam treats "analyzing and optimizing technical and business processes" as a distinct competency: turning how a team plans, builds, ships, observes, and decides into measurable, repeatable, automated flows. This chapter covers the software delivery lifecycle (SDLC), testing and validation, continuous integration and delivery (CI/CD), post-mortem culture, and the business-side disciplines of cost analysis, stakeholder management, and change control.

The software development lifecycle in the cloud

Modern SDLC is iterative, not waterfall. The architect's job is to ensure each phase has the right cloud primitives and guardrails so quality is built in, not inspected in afterward.

Best practice: Build the artifact once and promote the same immutable image across environments. Rebuilding per environment is a classic exam trap — it breaks reproducibility and introduces "works in staging, fails in prod" drift.

CI/CD: continuous integration and delivery

Continuous Integration means every commit is automatically built and tested against the shared mainline, catching integration problems within minutes. Continuous Delivery keeps every passing build deployable on demand; Continuous Deployment goes further and ships automatically once gates pass.

6. Managing Implementations: Migration & CI/CD on Google Cloud

Designing an architecture is only half the architect's job. The other half is managing its implementation: moving existing workloads into the cloud safely, automating how code reaches production, and choosing the right developer tooling and APIs. This chapter mirrors how the body of knowledge frames operational delivery.

The 5 Rs of Migration Strategy

Before any tooling decision, classify each workload. A widely-taught framework lists five (sometimes seven) treatment options. The exam loves matching a scenario to the cheapest-yet-feasible R.

StrategyWhat it meansUse when
Rehost (lift & shift)Move VMs as-is to Compute EngineFast exit from a data center; minimal code change
Replatform (lift & optimize)Minor tweaks, e.g. move DB to Cloud SQLQuick wins on managed services without rewriting
Refactor / Re-architectRewrite for cloud-native (GKE, Cloud Run)Long-term agility, scalability matters most
RepurchaseSwitch to SaaSCommodity workload (CRM, email)
Retire / RetainDecommission, or keep on-premUnused apps; or latency/compliance blockers

Migration phases (Google's model):

Key tools to recognize:Migrate to Virtual Machines (M2VM) replicates on-prem/AWS VMs into Compute Engine with minimal cutover. Database Migration Service (DMS) does continuous, near-zero-downtime DB replication (MySQL, PostgreSQL, Oracle). Transfer Appliance ships a physical box for petabyte-scale offline data; Storage Transfer Service handles online bucket-to-bucket and cloud-to-cloud copies. Datastream = serverless CDC.

7. Solution & Operations Excellence: Monitoring and SRE

An architecture that cannot be observed cannot be operated. This chapter covers how Google's Cloud Operations suite and the discipline of Site Reliability Engineering (SRE) turn a running system into a measurable, improvable service. The exam tests whether you can pick the right signal, set the right target, and balance reliability against feature velocity using objective numbers rather than opinion.

The four pillars of observability

Cloud Operations (formerly Stackdriver) bundles Cloud Monitoring (time-series metrics, dashboards, uptime checks, alerting policies), Cloud Logging (ingest, route, retain via sinks and Log Buckets), Cloud Trace (distributed latency), Cloud Profiler (continuous CPU/heap profiling), and Error Reporting. A key exam fact: the Ops Agent is the current unified collector for Compute Engine, replacing the legacy Monitoring and Logging agents; it must be installed to get in-guest metrics such as memory and disk.

SLI, SLO, SLA — know the difference cold. An SLI (Indicator) is a measured ratio, e.g. good requests ÷ valid requests. An SLO (Objective) is the internal target for that SLI, e.g. 99.9% over 28 days. An SLA (Agreement) is the contract with the customer, including penalties. Golden rule: the SLA target is always looser than the internal SLO, so you breach your own alarm before you breach the customer contract.

8. Case Studies, Trade-Offs, and Exam Strategy

The Google Cloud Professional Cloud Architect (PCA) exam is two hours, roughly 50–60 multiple-choice and multiple-select questions, and a significant share of items are anchored to four official case studies: EHR Healthcare, Helicopter Racing League (HRL), Mountkirk Games, and TerramEarth. This final chapter teaches you how to read a case study like an architect, how to resolve competing requirements through deliberate trade-offs, and how to manage the clock and the traps on exam day.

How to read a case study

Every case follows the same skeleton: Company overview → Solution concept → Existing technical environment → Business requirements → Technical requirements → Executive statement. The gold is in the requirements and the executive statement. Each requirement is a constraint that eliminates wrong answers. Build a mental map before reading any question.

Reading drill (do it once per case): Highlight every verb of intent — migrate, modernize, reduce, scale, comply, real-time — and every hard number (SLA %, latency ms, data volume, retention years). Map each to a managed service before you touch the questions.

The full lesson continues in the interactive course on this page.

Official reference

Customize this training

Get a certificate — $15$5