Markdown Editor

Google Cloud Professional Cloud Architect Case Study Workbook Template

Exam facts, guide section weights, self-assessment, case study register, 11-step analysis frame, pillar check, security, migration, cost, practice log

ArchitekturVollständigGoogle Cloud Professional Cloud Architect exam guide as linked on 2026-10-23 (successor to v6.1); Google Cloud Well-Architected Framework (6 pillars)googlepcacasestudyworkbook

Anleitung: Use it when you prepare for the Google Cloud Professional Cloud Architect exam. Fill the subsection self-assessment first, then apply the analysis frame to each official case study in your own words. The main pitfall is jumping to products before listing requirements and constraints.

Vorschau

Case Study Workbook: Google Cloud Professional Cloud Architect ([Candidate or study group])

Preparation workbook for the Google Cloud Professional Cloud Architect exam. It maps the six sections of the official exam guide (with their published weights) to your own evidence, gives a reusable frame for analysing any case study (business requirements, technical requirements, constraints, current state, proposed architecture, service choices, Well-Architected pillar check, security and compliance, migration, cost, trade-offs) and works that frame through once on a fictional company written for this template. It follows the exam guide linked from the certification page as checked on 2026-10-23 (successor to guide v6.1, October 2025) and the Google Cloud Well-Architected Framework (six pillars). It does not contain any text from the official case studies: read them at the source. Replace every [bracketed] value and every row marked Example.

Document control

FieldValue
Document ID[PCA-WB-001]
Candidate or study group[Name]
ExamGoogle Cloud Professional Cloud Architect (standard exam)
Exam guide version studied[Guide linked on certification page, downloaded YYYY-MM-DD]
Case studies studiedAltostrat Media, Cymbal Retail, EHR Healthcare, KnightMotives Automotive
Target exam dateYYYY-MM-DD
Delivery mode[Online proctored / Test centre]
Version[0.1]
Status[Draft / In progress / Exam ready / Archived]
Owner[@candidate]
Approvers/reviewers[@mentor], [@study-partner]
Last updatedYYYY-MM-DD
Classification[Personal / Internal]

Approvals

RoleNameDecisionDate
Candidate[@candidate][Ready to book / Not ready]YYYY-MM-DD
Mentor or reviewer[@mentor][Agree / Revise plan]YYYY-MM-DD
Training budget owner[@manager][Approve exam fee / Defer]YYYY-MM-DD

Revision history

VersionDateAuthorChange summary
0.1YYYY-MM-DD[@candidate]First self-assessment against the exam guide
0.2YYYY-MM-DD[@candidate]Example: Frame applied to two official case studies
1.0YYYY-MM-DD[@candidate]Example: All four case studies analysed; readiness gate passed

Contents

1. Purpose and exam facts

This workbook turns the exam guide into a study plan and turns each case study into a structured architecture analysis. The exam rewards candidates who read a business situation, separate what the business needs from what the technology must do, and pick the Google Cloud service that satisfies the stated requirement with the least operational burden. The frame in this workbook trains exactly that habit.

1.1 Exam facts as published

ItemValue as stated on the certification page (checked 2026-10-23)
Length2 hours (standard exam); 1 hour (renewal exam)
Questions50 to 60 (standard); 25 (renewal)
Question typesMultiple choice and multiple select
Case study shareCase study questions are 20 to 30 percent of the standard exam and 90 to 100 percent of the renewal exam
Case studies available4 available for the standard exam (2 appear in each exam), 2 available for the renewal exam (1 per exam), named in the exam guides
DeliveryOnline proctored, or onsite at a test centre
FeeUSD 200 plus tax (standard); USD 100 plus tax (renewal)
LanguagesEnglish, Japanese
Recommended experience3 or more years in industry, including 1 or more years designing and managing solutions on Google Cloud; no prerequisites
Validity2 years; check the renewal options on the certification page

1.2 How the workbook fits a study cycle

Repeat the loop until the readiness gate in section 14 is met; each pass should shrink the weighted gaps found in section 2.

1.3 Rules for this workbook

  • Summarise the official case studies in your own words. Keep the official PDFs beside the workbook; do not paste their text here, and do not share copies of them.
  • Write every practice question yourself. Do not record or share real exam questions; that breaches the exam agreement and invalidates the certification.
  • When a product name in your notes differs from the current guide, use the current guide name and note the old one in brackets. Example: the guide linked in October 2026 uses Gemini Enterprise Agent Platform where guide v6.1 used Vertex AI.

2. Exam guide coverage map

The guide linked from the certification page on 2026-10-23 gives six sections with approximate weights. The earlier guide v6.1 (October 2025) used slightly different weights and is shown for comparison so that you can spot which version a course was built on.

SectionTitle (short form)Weight, current guideWeight, guide v6.1Library templates that practise it
1Designing and planning a cloud solution architecture~25%~25%Google Cloud Well-Architected Review (architecture/google-well-architected-review), Application Migration Assessment (architecture/application-migration-assessment), Build vs Buy Analysis (architecture/build-vs-buy-analysis)
2Managing and provisioning a cloud solution infrastructure~17.5%~18%Landing Zone Design (architecture/landing-zone-design), Network Architecture Design (architecture/network-architecture-design), Data Platform Architecture (architecture/data-platform-architecture)
3Designing for security and compliance~17.5%~19%IAM Solution Design (security/iam-solution-design), Cloud Security Reference Patterns (security/cloud-security-reference-patterns), Data Residency and Sovereignty Assessment (compliance/data-residency-sovereignty-assessment)
4Analyzing and optimizing technical and business processes~15%~15%Disaster Recovery Plan (ops/disaster-recovery-plan), FinOps Cost Review (ops/finops-cost-review), Stakeholder Register (project/stakeholder-register)
5Managing implementation~12.5%~11%API Management Platform Design (architecture/api-management-platform-design), Deployment Runbook (ops/deployment-runbook), Migration Wave Plan (project/migration-wave-plan)
6Ensuring solution and operations excellence~12.5%~12%Observability Spec (ops/observability-spec), Chaos Experiment (ops/chaos-experiment), Error Budget Policy (ops/error-budget-policy)

2.1 Subsection self-assessment

Subsection topics are summarised in original short wording. Check the exact scope in the guide.

IDGuide subsection (topic in short)Rating 1 to 5Weight x gapEvidence or study action
1.1Infrastructure that meets business requirements: use cases, requirements, continuity, cost, integration, data movement, disposition, success measures[3][50][Action]
1.2Infrastructure that meets technical requirements: Well-Architected Framework, high availability, scaling, latency, backup, Gemini Cloud Assist[ ][ ][Action]
1.3Network, storage and compute choices, including AI and ML services[ ][ ][Action]
1.4Migration plan: integration, assessment with Migration Center, dependencies, licensing impact[ ][ ][Action]
1.5Future improvements and cloud-first evolution[ ][ ][Action]
2.1Network topologies: hybrid, multicloud, protection, VPC and load balancing[ ][ ][Action]
2.2Storage systems: allocation, access, transfer, lifecycle, growth, protection[ ][ ][Action]
2.3Compute systems: provisioning, Spot versus standard, networking, orchestration, serverless[ ][ ][Action]
2.4End-to-end ML workflows on Gemini Enterprise Agent Platform (formerly Vertex AI), AI Hypercomputer[ ][ ][Action]
2.5Prebuilt solutions and APIs with Agent Platform; Model Garden models[ ][ ][Action]
3.1Security design: IAM, hierarchy, keys and secrets, separation of duties, perimeter controls, remote access, supply chain, securing AI[ ][ ][Action]
3.2Compliance design: regulation, sensitive commercial data, certifications, audit logs[ ][ ][Action]
4.1Technical processes: SDLC, CI/CD, root cause analysis, testing, service catalogue, disaster recovery[ ][ ][Action]
4.2Business processes: stakeholders, change, skills, decisions, customer success, CapEx and OpEx, continuity[ ][ ][Action]
5.1Advising delivery teams: deployment, API management, test frameworks, migration tooling[ ][ ][Action]
5.2Working with Google Cloud programmatically: Cloud Shell, SDKs, emulators, Terraform, client libraries[ ][ ][Action]
6.1Operational excellence pillar principles[ ][ ][Action]
6.2Observability: monitoring, logging, profiling, alerting[ ][ ][Action]
6.3Deployment and release management[ ][ ][Action]
6.4Supporting deployed solutions[ ][ ][Action]
6.5Quality control measures[ ][ ][Action]
6.6Reliability in production: chaos, penetration and load testing[ ][ ][Action]

Example: subsection 1.1 rated 3 gives 25 x (5 - 3) = 50; subsection 6.3 rated 2 gives 12.5 x 3 = 37.5, so 1.1 is studied first.

3. Case study register

Case IDOfficial case studySector (from the name)Read onOwn summary writtenFrame applied (sections 4 to 12)Practice questions written
CS-01Altostrat MediaMediaYYYY-MM-DD[Yes / No][Yes / Partly / No][n]
CS-02Cymbal RetailRetailYYYY-MM-DD[Yes / No][Yes / Partly / No][n]
CS-03EHR HealthcareHealthcareYYYY-MM-DD[Yes / No][Yes / Partly / No][n]
CS-04KnightMotives AutomotiveAutomotiveYYYY-MM-DD[Yes / No][Yes / Partly / No][n]
CS-EX (Example)Halden Cold Chain (fictional, this template)Refrigerated logistics2026-10-23YesYes5

For each official case study, write a half-page summary in your own words under four headings: what the company sells and to whom, what is broken today, what leadership wants within which time frame, and which rules bind it (regulation, contracts, data location). Then copy only the requirement IDs into the tables in section 5.

4. Analysis frame and worked company

4.1 The eleven-step frame

StepQuestion to answerWhere in this workbookTypical exam signal
1What outcome does the business pay for?Section 5Words about growth, new markets, customer experience, time to market
2What must the system do and how well?Section 5Latency, availability, scale, recovery targets
3What cannot change?Section 6Regulation, contract dates, existing licences, skills
4What exists today and what hurts?Section 6Data centre, legacy databases, manual operations
5What is the target shape?Section 7Diagram questions, "which design best"
6Which managed service fits each component?Section 7Choosing between two similar products
7Does the design hold up against all six pillars?Section 8Reliability or cost distractors
8How is data, identity and AI protected?Section 9Least privilege, perimeter, keys, audit
9How do we get there safely?Section 10Order of moves, tooling, cutover
10What does it cost and how is cost controlled?Section 11Discounts, Spot, licensing
11What did we give up?Section 12"Most cost-effective" versus "most resilient"

4.2 Worked company brief (fictional)

Example: Halden Cold Chain is a fictional refrigerated freight company invented for this template. It runs 4,000 temperature-controlled trucks across the European Union and the United States, serving food and pharmaceutical shippers. It operates from two leased data centres; the lease on the larger one ends in 18 months and will not be renewed. Dispatch runs on a containerised Java application on a self-managed Kubernetes cluster; billing and contracts run on an Oracle database on VMware virtual machines; truck telemetry (position, reefer temperature, door events) arrives every 30 seconds through a message broker that drops data at peak. Shippers complain that the tracking portal is slow and that temperature excursion alerts arrive late. The board wants a shipper self-service portal with predicted arrival times and a natural-language assistant that answers "where is my load and is it within temperature". Pharmaceutical customers require audit evidence of temperature history for seven years, and EU shipper data must stay in the EU. The IT team of 25 knows VMware, Java and SQL well and has little cloud experience.

5. Business and technical requirements

5.1 Business requirements

IDRequirementStated or inferredSuccess measurePriority
BR-001 (Example)Exit the larger data centre before the lease ends in 18 monthsStatedData centre empty by month 18Must
BR-002 (Example)Give shippers a self-service tracking portal with predicted arrival timesStated70% of status calls deflected to the portal within 6 months of launchMust
BR-003 (Example)Offer a conversational assistant over load status and temperature historyStatedAssistant answers rated correct in 95% of sampled conversationsShould
BR-004 (Example)Reduce late temperature excursion alerts that cause spoiled loadsStatedAlert raised within 60 seconds of an excursionMust
BR-005 (Example)Keep the IT team productive without a large hiring waveInferredNo more than 3 new hires; training plan fundedShould
[BR-NNN][Requirement][Stated / Inferred][Measure][Must / Should / Could]

5.2 Technical requirements

IDRequirementTraces toTargetVerification
TR-001 (Example)Ingest truck telemetry without loss at peakBR-0044,000 trucks x 1 message per 30 s, about 133 messages per second average; design for 10x burstsLoad test at 1,400 messages per second
TR-002 (Example)Detect temperature excursions in a streaming pathBR-004Under 60 s from reading to alertEnd-to-end synthetic excursion test
TR-003 (Example)Serve the portal with high availability in each geographyBR-00299.9% monthly availability, p95 page under 2 sUptime checks and real user monitoring
TR-004 (Example)Retain temperature history for pharmaceutical loads for 7 years, immutableBR-004, CN-002Retention lock, audit trail of accessRetention policy review and restore test
TR-005 (Example)Ground assistant answers in load and telemetry data onlyBR-003No answer without a cited recordEvaluation set of 300 questions
TR-006 (Example)Recover billing within 4 hours with no more than 15 minutes of data lossBR-001RTO 4 h, RPO 15 minAnnual DR exercise
[TR-NNN][Requirement][BR-NNN][Target][Method]

Example: 4,000 trucks x 2,880 messages per day (one every 30 seconds) = 11,520,000 messages per day. At about 1 KB per message that is about 11.5 GB per day and about 4.2 TB per year of raw telemetry, so seven years of pharmaceutical history is a storage-class and lifecycle decision, not a database sizing problem.

6. Current state and constraints

6.1 Current state

IDComponentTodayPain pointDisposition candidate
CUR-001 (Example)Dispatch applicationJava containers on self-managed KubernetesCluster upgrades lag; on-call fatigueMove to managed Kubernetes (replatform)
CUR-002 (Example)Billing and contractsOracle on VMware virtual machinesLicence cost; DBA bottleneckRehost first, then refactor database
CUR-003 (Example)Telemetry brokerSelf-managed message broker on two serversDrops messages at peakReplace with managed messaging
CUR-004 (Example)Tracking portalMonolithic web app polling the dispatch databaseSlow at peak; couples portal load to dispatchRebuild as stateless services
CUR-005 (Example)ReportingNightly batch to a reporting databaseData a day oldReplace with a warehouse fed by streams
[CUR-NNN][Component][Today][Pain][Retain / Rehost / Replatform / Refactor / Replace / Retire]

6.2 Constraints

IDConstraintSourceEffect on the design
CN-001 (Example)Data centre lease ends in 18 monthsBusinessSpeed beats elegance for the first move; rehost what cannot be refactored in time
CN-002 (Example)EU shipper data stays in the EUContracts and data protection lawSeparate EU and US regional deployments; organisation policy restricts resource locations
CN-003 (Example)Seven-year immutable temperature history for pharmaceutical loadsCustomer quality agreementsObject storage with retention lock; access logged
CN-004 (Example)Team skills: VMware, Java, SQLOrganisationPrefer managed services close to current skills; fund training
CN-005 (Example)Existing Oracle licences run for 2 more yearsCommercialLicence impact assessed before any rehost onto new hosts
[CN-NNN][Constraint][Source][Effect]

7. Proposed architecture and service choices

7.1 Target architecture

Example: the target for Halden Cold Chain separates the telemetry path from the portal path so that a burst of truck messages cannot slow shipper pages, and keeps one deployment per geography to satisfy CN-002.

7.2 Service choices with rationale

IDComponentChosen serviceAlternatives consideredReason (trace)
SVC-001 (Example)Telemetry ingestionPub/SubSelf-managed broker on Compute Engine; Managed Service for Apache KafkaFully managed, scales with bursts, no broker operations (TR-001, CN-004); Kafka kept as an option only if partners require the Kafka protocol
SVC-002 (Example)Excursion detectionDataflow streamingCloud Run functions per messageWindowed, stateful stream processing with exactly-once semantics for alerts (TR-002)
SVC-003 (Example)Latest truck stateBigtableFirestore; MemorystoreLow-latency key lookups at high write rates keyed by truck ID (TR-003)
SVC-004 (Example)History and analyticsBigQueryCloud SQL reporting replicaServerless analytics over billions of rows, feeds arrival-time models (BR-002)
SVC-005 (Example)Seven-year archiveCloud Storage with Bucket Lock retention policy and Archive class through lifecycle rulesKeep everything in BigQueryImmutable retention at low cost (TR-004, CN-003)
SVC-006 (Example)Portal and APIsCloud Run behind the External Application Load BalancerGKE; Compute Engine managed instance groupsStateless, scales to zero overnight in each geography, least operations (TR-003)
SVC-007 (Example)DispatchGKE (Autopilot)Cloud RunExisting Kubernetes manifests and long-running workers; managed control plane removes upgrade lag (CUR-001)
SVC-008 (Example)Billing database, interimGoogle Cloud VMware EngineBare Metal Solution; immediate refactorFastest exit for Oracle on VMware within 18 months (CN-001); licence review in CN-005
SVC-009 (Example)Billing database, targetAlloyDB for PostgreSQL via Database Migration ServiceCloud SQL for PostgreSQL; SpannerPostgreSQL skills fit the team; Oracle to PostgreSQL-compatible migration path (confirm the supported source and destination pairs in Database Migration Service documentation); Spanner not justified without global writes (TR-006)
SVC-010 (Example)AssistantGemini models on Gemini Enterprise Agent Platform, grounded on BigQuery and Bigtable data through an API layerSelf-hosted open model on GKE GPUsManaged model serving and grounding, no GPU fleet to run (BR-003, TR-005)
SVC-011 (Example)Partner APIsApigeePlain load balancerShipper API keys, quotas and analytics (BR-002)
SVC-012 (Example)Hybrid connectivityPartner Interconnect with HA VPN as backupHA VPN onlyBandwidth and stable latency for replication during migration (section 10)
[SVC-NNN][Component][Service][Alternatives][Reason and trace IDs]

8. Well-Architected pillar check

PillarQuestion to ask of the designFindingStatusAction
Operational excellenceCan the team deploy, observe and roll back each component with automation?Example: Cloud Deploy pipelines for Cloud Run and GKE; dashboards and SLO alerts in Cloud MonitoringPassWrite runbooks for the streaming jobs
Security, privacy, and complianceIs access least privilege, is data protected in transit and at rest, are perimeters and audit logs in place?Example: VPC Service Controls around data projects; CMEK in Cloud KMS for the archive; Data Access audit logs onPass with actionAdd Model Armor screening for the assistant (section 9)
ReliabilityDoes each tier meet its availability and recovery target, including regional failure?Example: Cloud Run is regional and a single-cluster Bigtable instance sits in one zone; a region loss takes the portal down in that geographyGapAdd a second region per geography for the portal tier, Bigtable replication across two regions
Cost optimizationIs each component right-sized, and are discounts and lifecycle rules used?Example: Archive class after 90 days; committed use discounts planned after 3 months of usage dataPassReview in section 11
Performance optimizationDo latency and throughput targets hold at 10x load?Example: Bigtable key design by truck ID avoids hotspots only if IDs are not sequentialPass with actionHash or reverse truck IDs in the row key
SustainabilityAre regions and resources chosen with carbon in mind, and is idle capacity avoided?Example: Cloud Run scales to zero overnight; region choice considers carbon-free energy dataPassCheck the Carbon Footprint report quarterly

The framework also offers cross-pillar perspectives (AI and ML, Financial services). Apply the AI and ML perspective to any case study that includes generative AI, as the worked assistant does.

9. Security, compliance and AI safeguards

IDControl objectiveImplementationSatisfiesEvidence
SEC-001 (Example)Separate EU and US data and keep resources in permitted regionsFolder per geography; organisation policy restricting resource locations; consider Assured Workloads for the EU folderCN-002Policy export, audit of resource locations
SEC-002 (Example)Least-privilege human accessGroups from the corporate identity provider federated to Cloud Identity; predefined roles granted to groups at folder level; no basic rolesSEC baselineQuarterly access review
SEC-003 (Example)No long-lived keys in CIWorkload Identity Federation from the CI system; service account impersonation for operatorsSupply chainIAM policy and key inventory showing zero user-managed keys
SEC-004 (Example)Exfiltration protection for data projectsVPC Service Controls perimeter around BigQuery, Bigtable and Cloud StorageCN-002, CN-003Perimeter dry-run log, then enforced
SEC-005 (Example)Customer-controlled encryption for the archiveCMEK in Cloud KMS, key rotation, separate key admin groupCN-003Key usage logs
SEC-006 (Example)Admin access to internal tools without VPNIdentity-Aware Proxy with context-aware accessSEC baselineAccess logs
SEC-007 (Example)Trusted container images onlyArtifact Registry with vulnerability scanning; Binary Authorization on GKESupply chainAdmission logs
SEC-008 (Example)Prompt and response screening for the assistantModel Armor templates for prompt injection and sensitive data; Sensitive Data Protection on grounding sourcesBR-003, TR-005Screening logs, red-team results
SEC-009 (Example)Audit trail for pharmaceutical customersCloud Audit Logs routed to a locked log bucket in a dedicated projectCN-003Log retention configuration
[SEC-NNN][Objective][Implementation][Trace][Evidence]

Compliance note: record which laws and certifications the case study names (health records, children's privacy, card data, sovereignty, SOC 2) and which Google Cloud compliance offerings support them. Shared responsibility still applies: the provider's certification does not certify your workload.

10. Migration plan

WaveScopeStrategyToolingEntry criteriaExit criteria
W0 (Example)Discovery and foundationAssessMigration Center for inventory and cost estimates; landing zone through TerraformSponsor sign-offLanding zone live, interconnect tested
W1 (Example)Telemetry pipelineReplacePub/Sub, Dataflow; dual-publish from trucks during transitionW0 done14 days of parallel run with no message loss
W2 (Example)Portal and APIsRefactorCloud Run, ApigeeW1 doneLoad test at 10x passed; shipper pilot accepted
W3 (Example)DispatchReplatformGKE Autopilot; container images rebuilt in Cloud BuildW0 doneCutover rehearsal passed
W4 (Example)Billing interimRehostGoogle Cloud VMware Engine with VMware HCXLicence review done (CN-005)Data centre empty, before month 18
W5 (Example)Billing targetRefactor databaseDatabase Migration Service, Oracle to AlloyDBW4 stable for 3 monthsReconciliation clean; VMware Engine decommissioned

Plan cutovers with the Cutover Plan (project/cutover-plan) and the Migration Wave Plan (project/migration-wave-plan), and reconcile data with Data Migration Reconciliation (project/data-migration-reconciliation).

11. Cost view

IDLeverApplies toConditionExpected effect
COST-001 (Example)Committed use discountsGKE nodes, AlloyDB, VMware Engine nodesStable baseline after 3 months of dataLower unit price for the steady base
COST-002 (Example)Spot VMsNightly model retraining and batch reprocessingWork can be interrupted and retriedLarge discount on interruptible capacity
COST-003 (Example)Scale to zeroCloud Run portal in each geographyTraffic falls overnightNo idle instance cost
COST-004 (Example)Storage lifecycle rulesTelemetry archiveObjects older than 90 days rarely readArchive class price for most of the seven years
COST-005 (Example)BigQuery partitioning and clusteringTelemetry history tablesQueries filter on date and truckLess data scanned per query
COST-006 (Example)Licence portability reviewOracle on VMware EngineContract terms allow itAvoid buying new licences during the interim
COST-007 (Example)Budgets and alerts per projectAll projectsLabels applied by the landing zoneEarly warning on overspend

Business case framing: compare data centre exit costs (lease, hardware refresh avoided, staff time) with the cloud run rate in CapEx and OpEx terms, and state the success measures from section 5 that justify the spend.

12. Trade-offs and decision log

IDDecisionOptimisesGives upRevisit when
DEC-001 (Example)Rehost Oracle on VMware Engine first, refactor laterSpeed to data centre exitPays VMware Engine and Oracle costs for a periodBilling refactor ready (W5)
DEC-002 (Example)Pub/Sub instead of managed KafkaLeast operational overheadKafka protocol compatibility for partnersA partner requires Kafka
DEC-003 (Example)Regional deployments per geography, two regions each for the portalResidency and resilienceHigher cost than a single regionShipper SLA changes
DEC-004 (Example)Managed Gemini models rather than self-hosted modelsTime to market, no GPU operationsLess control over model internals and pricingVolume makes self-hosting cheaper, or a residency rule blocks the managed model
DEC-005 (Example)Cloud Run for the portal, GKE for dispatchLeast operations per workloadTwo runtime platforms to supportTeam skills converge on one
Scale testAt 0.1x loadAt 10x load
Example: Telemetry pathSame design; costs fall with Pub/Sub and Dataflow autoscalingSame design; check Bigtable node count and Dataflow worker limits
Example: PortalCloud Run scales to zero; fineCheck per-region quotas and database connection limits

13. Practice question log

IDCaseGuide sectionStem (own words)OptionsAnswerWhy the others are wrongResult
PQ-001 (Example)Halden1.3Telemetry from 4,000 trucks must be ingested without loss and processed for alerts within 60 s, with the least operations. Which design?A: Pub/Sub then Dataflow. B: Broker on Compute Engine then cron jobs. C: Direct writes to Cloud SQL. D: Batch uploads to Cloud Storage hourlyAB adds operations; C does not scale for writes and has no stream logic; D misses 60 sCorrect
PQ-002 (Example)Halden3.1Prevent data in BigQuery from being copied to projects outside the organisation even by users with valid roles. Which control?A: More restrictive IAM roles. B: VPC Service Controls perimeter. C: Firewall rules. D: CMEKBA does not stop a legitimate user copying data out; C does not apply to Google APIs; D protects keys, not data movementCorrect
PQ-003 (Example)Halden1.4The data centre must be empty in 18 months; Oracle runs on VMware. Fastest low-risk first move?A: Rewrite billing as microservices. B: Rehost to Google Cloud VMware Engine. C: Export to CSV and load to BigQuery. D: Wait for the lease to endBA misses the deadline; C breaks the transactional system; D is not a planIncorrect, revisit 1.4
PQ-004 (Example)Halden2.3Nightly model retraining can restart if interrupted. Which compute option is cheapest?A: Standard VMs with sustained use. B: Spot VMs. C: Sole-tenant nodes. D: Larger committed machineBA and D cost more for interruptible work; C is for licensing or isolation needsCorrect
PQ-005 (Example)Halden3.1CI pipelines in an external CI system need to deploy to Google Cloud without stored keys. Which approach?A: Service account key in CI secrets. B: Workload Identity Federation. C: Shared user account. D: API keyBA stores a long-lived key; C breaks accountability; D cannot authorise deploymentsCorrect
[PQ-NNN][Case][Section][Stem][Options][Answer][Reasoning][Correct / Incorrect]

14. Readiness tracker and exam-day plan

14.1 Readiness gate

CriterionTargetCurrentMet
Every guide subsection rated 3 or higher22 of 22[n][Yes / No]
Frame applied to all four official case studies4 of 4[n][Yes / No]
Own practice questions written per case studyAt least 10[n][Yes / No]
Correct rate on own and official sample questions over the last two weeks[Target you set, e.g. 80%][x%][Yes / No]
Hands-on labs completed in a sandbox project[List][List][Yes / No]

14.2 Exam-day plan

  • Re-read your own case study summaries the day before, not the product documentation.
  • With 120 minutes for 50 to 60 questions, budget about 2 minutes per question; mark long ones for review and return.
  • For a case study question, find the requirement ID or constraint that the question touches before you read the options.
  • Eliminate options that break a stated constraint, then options that add self-managed components without need, then choose between the remaining ones on the qualifier in the stem (cheapest, fastest, least operations, most secure).
  • For multiple-select items, check the stem for the exact number of answers.

15. Glossary and references

15.1 Glossary

TermMeaning
Case studyFictitious company description published with the exam guide; some questions refer to it
DispositionDecision on what happens to an existing workload: retain, rehost, replatform, refactor, replace or retire
CMEKCustomer-managed encryption keys held in Cloud KMS
VPC Service ControlsPerimeter around Google Cloud APIs that limits data movement across the boundary
Workload Identity FederationLets external workloads obtain short-lived Google Cloud credentials without service account keys
GroundingConstraining a model's answers to supplied enterprise data
RTO and RPOMaximum tolerated downtime and maximum tolerated data loss after a failure
Stated versus inferred requirementWritten in the case text, versus concluded by the analyst

15.2 References

ReferenceVersion or date checkedUse
Google Cloud, Professional Cloud Architect certification page, cloud.google.com/learn/certification/cloud-architectChecked 2026-10-23Exam facts in section 1.1
Google Cloud, Professional Cloud Architect exam guide (English), linked from the certification pageDownloaded 2026-10-23; no version number printedSection names, weights, case study names
Google Cloud, Professional Cloud Architect exam guide v6.1 (English)October 2025Earlier weights for comparison
Google Cloud Well-Architected Framework, docs.cloud.google.com/architecture/frameworkPage updated 2026-10-13Six pillars and cross-pillar perspectives
Google Cloud product documentation for each service named in section 7Check at time of studyService capabilities

Standard and licence note

Structure aligned with the section outline and weights of the Google Cloud Professional Cloud Architect exam guide (as linked from the certification page on 2026-10-23, successor to guide v6.1 of October 2025) and with the six pillars of the Google Cloud Well-Architected Framework. Only section names, weights, pillar names and the names of the official case studies are used; no case study text, exam guide text or exam questions are reproduced. The analysis frame, the fictional company Halden Cold Chain and all practice questions are original text written for this collection. Check the current exam guide, case studies and product names on the official certification page before use. Google, Google Cloud and the product names used here are trademarks of their owners; this template is not affiliated with or endorsed by them. Template licence: MIT.

Ähnliche Vorlagen