GCP-PCA Google Cloud Professional Cloud Architect
- Vendor
- Google Cloud
- Level
- Professional
- Questions
- 55
- Time
- 120 min
- Domains
- 6
- In the bank
- 334
Practice 334 questionsTake a timed mock examDay-by-day study plan
Guides for this exam
- 9 Question Patterns People Get Wrong Across the Google Cloud Exams, and the Rule Behind Each · 한국어
- GCP-PCA Study Guide: Turn Every Requirement Into a Number, Then Defend the Cheapest Design That Meets It · 한국어
- Cloud SQL vs AlloyDB vs Spanner vs Bigtable vs Firestore vs BigQuery: How to Tell Which One a Question Wants · 한국어
The exam at a glance
| Level | Professional |
|---|---|
| Questions | 55 |
| Time | 120 minutes (about 2.2 minutes per question) |
| Passing mark | Not published by the vendor |
Domains and weights
| Domain | Weight | Practice questions here |
|---|---|---|
| D1 · Designing and planning a cloud solution architecture | 25% | 84 |
| D2 · Managing and provisioning a cloud solution infrastructure | 17.5% | 59 |
| D3 · Designing for security and compliance | 17.5% | 58 |
| D4 · Analyzing and optimizing technical and business processes | 15% | 50 |
| D5 · Managing implementation | 12.5% | 41 |
| D6 · Ensuring solution and operations excellence | 12.5% | 42 |
60 of the 334 practice questions (18%) ask for more than one answer.
D1 · Designing and planning a cloud solution architecture 25%
Architecture design questions start from requirements, often from a case study such as EHR Healthcare, and ask for the design or the order of work that satisfies them. Constraints like licensing terms, spiky streaming data or read-heavy load usually decide. Strong options solve the stated bottleneck with the least disruption; weaker ones change engines or add clusters the requirements never asked for.
What to watch for
- Separate what the system must do from how well it must do it; measurable qualities such as availability under failure and latency targets shape the architecture most.
- When a relational database is overloaded by reads, consider splitting read and write traffic before any option that replaces the database engine.
- Licensing terms belong in planning: per-core licenses with dedicated hardware rules narrow the compute choice before performance even comes into it.
Tasks in the official exam guide (5)
D2 · Managing and provisioning a cloud solution infrastructure 17.5%
Provisioning questions are concrete. A setup already exists (a hybrid link, a managed instance group, a backup routine, a planned GPU run) and a symptom or new risk appears. You pick the configuration change or capacity model that fixes it. Distractors work in a narrow sense but keep the weakness, such as patching VMs in place or keeping backups within reach of stolen admin credentials.
What to watch for
- When on-premises routers see only some regions, inspect the routing settings of the VPC network itself before adding routers or tunnels.
- Match GPU consumption to the job's tolerance: work that can be preempted, work that can wait, and a fixed-date training run each map to a different way of obtaining capacity.
- For ransomware resilience, backups need both a policy that schedules them and a store that even an administrator cannot shorten or erase.
Tasks in the official exam guide (5)
D3 · Designing for security and compliance 17.5%
Security design scenarios mix regulation with real threats: exfiltration by a valid user, tenant data at contract end, separation of duties on keys, re-identification of released data. Correct answers layer controls on top of IAM instead of replacing it. Read whether the requirement is to prevent, detect or prove something, because options often offer the right family of tool for the wrong one of those.
What to watch for
- If valid permissions are part of the threat, IAM alone will not stop it; look for a perimeter that limits where protected services can send data.
- For separation of duties on encryption, check that the people who manage keys cannot use them to decrypt, and that data access runs through a service identity.
- Before releasing de-identified data, measure how easily people can be singled out from the remaining quasi-identifiers rather than assuming removed names are enough.
D4 · Analyzing and optimizing technical and business processes 15%
Process questions blend technical and organizational work: moving checks earlier in the delivery pipeline, winning adoption across teams, explaining cloud spending, finding the root cause of an outage. The best options gather evidence or change the process gradually. Mandates, big-bang rollouts and fixes applied before a hypothesis exists are common distractors.
What to watch for
- Troubleshooting answers start with data: gateway logs and metrics for failing outbound calls, or audit logs lined up with a metrics timeline for a suspected change.
- Adoption of a new tool or pipeline is earned with champions, phased onboarding and support, not with a mandate that teams have ignored before.
- Cost concerns call for visibility and control together: attribution through labels, budget alerts, and commitments only for load that is steady.
Tasks in the official exam guide (2)
D5 · Managing implementation 12.5%
Implementation items read like advice to a delivery team: where to place tests, how to write a shared Terraform module, how to move a database with little downtime, which command-line tool to standardize on. The architect's answer should keep environments safe and repeatable. Legacy tools, hidden defaults and manual changes that drift from code are the recurring wrong turns.
What to watch for
- Place tests by cost and speed: fast checks run often, while slow and expensive ones run less often in an environment that resembles production.
- In shared modules, a default that points at production is a hidden risk; values that differ per environment should be required inputs that fail early when missing.
- For low-downtime database moves, think initial load plus continuous replication and a short cutover, and prefer current tools such as gcloud storage over legacy ones.
Tasks in the official exam guide (2)
D6 · Ensuring solution and operations excellence 12.5%
Operations excellence is tested through reliability that must be shown, not assumed. Stems describe rollouts that serve errors, ignored alerts, untested failover, unexplained CPU use or logs too large to aggregate by hand. You pick the practice or observability tool that produces real evidence, and the right one usually matches the exact question being asked, such as which code burns CPU.
What to watch for
- A high availability setting is not proof; run a planned failover with production-like traffic and time how long clients take to recover, then compare that with the target.
- Pick the observability tool by question: request paths across services, resource use inside code, and SQL aggregation over large log volumes each have a different home.
- Safe rollouts limit how many instances change at once and wait for application health checks before new instances receive traffic.
Tasks in the official exam guide (6)
A study order that works
The 26-day study plan for GCP-PCA takes the domains in this order. Each day has a short reading, key terms and a quiz from the bank.
- Days 1–7: D1 · Designing and planning a cloud solution architecture
- Days 8–13: D2 · Managing and provisioning a cloud solution infrastructure
- Days 14–18: D3 · Designing for security and compliance
- Days 19–21: D4 · Analyzing and optimizing technical and business processes
- Days 22–24: D5 · Managing implementation
- Day 25: D6 · Ensuring solution and operations excellence
- Day 26: Final Review: Exam Format, Case Studies, Confused Pairs and Test Day
Recent changes to these questions
- : 4 answer choice sets changed, 4 answer keys corrected, 4 explanations rewritten
- : 60 questions added
- : 1 answer choice set changed, 1 answer key corrected, 1 explanation rewritten
- : 1 explanation rewritten
About these questions
Every question is original, written from the public exam guide and checked against the vendor's own documentation. None comes from a real exam. Each one has an explanation of why the answer is right and why the other options are wrong. How the questions are written.