cert
cert-1
cert-2

Pass Google Professional Cloud Architect Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
Professional Cloud Architect Exam - Verified By Experts
Professional Cloud Architect Premium Bundle
$29.98

Professional Cloud Architect Premium Bundle

$79.99
$109.97
  • Premium File 370 Questions & Answers. Last update: Nov 13, 2026
  • Training Course 63 Video Lectures
  • Study Guide 491 Pages
 
$109.97
$79.99
accept 142 downloads in last 7 days
block-screenshots
Purchase Google Professional Cloud Architect Exam Training Products Individually
Google Professional Cloud Architect Premium File
Premium File 370 Q&A
$76.99$69.99
Google Professional Cloud Architect Video Training Course
Training Course 63 Lectures
$21.99 $19.99
Google Professional Cloud Architect PDF Study Guide
Study Guide 491 Pages
$21.99 $19.99
Google Professional Cloud Architect Practice Test 7

Question 60

At International game publisher, the Google Cloud design for multiplayer leaderboard is affected because the team needs globally consistent top-rank writes but each region has independent SQL databases. A review found that traces show duplicate rank commits during cross-region failover. The proposed response must account for the requirement that player rewards require globally serialized authoritative outcomes. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?

  1. Track commit latency, aborted transaction retries and region failover
  2. Measure write conflicts, data model and multi-region latency budgets
  3. Use independent last-writer-wins Redis counters as the financial reward ledger
  4. Migrate selected leaderboard partitions with dual reconciliation
  5. Choose globally consistent Spanner transactions for authoritative ranking records

Explanation

Correct Answers

D:

Migrate selected leaderboard partitions with dual reconciliation is a controlled means to introduce the approved architecture while meeting the requirement that player rewards require globally serialized authoritative outcomes. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption. This supplies the controlled-introduction half of the two-action package.

E:

Choose globally consistent Spanner transactions for authoritative ranking records targets the underlying issue (the team needs globally consistent top-rank writes but each region has independent SQL databases) rather than merely reporting symptoms. It also preserves the required outcome (player rewards require globally serialized authoritative outcomes), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.

Incorrect Answers

A:

Monitoring multiplayer leaderboard for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: the team needs globally consistent top-rank writes but each region has independent SQL databases.

B:

This diagnoses the original issue (the team needs globally consistent top-rank writes but each region has independent SQL databases), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.

C:

Conflict resolution by overwrite can duplicate or lose reward decisions. The shortcut does not supply the requested design and safe rollout for multiplayer leaderboard, where traces show duplicate rank commits during cross-region failover.

Question 61

Case study: Medical imaging supplier: patient identifier transformation

Medical imaging supplier relies on patient identifier transformation to deliver its operational commitments. The current architectural problem is that the data warehouse stores masked fields but shared exports retain direct identifiers. The team has recorded this evidence: sampling shows patient names survive in analytical free-text notes. Any proposed response must preserve the requirement that only approved care providers may see reidentifiable data.

At Medical imaging supplier, the patient identifier transformation workload has a documented risk: the data warehouse stores masked fields but shared exports retain direct identifiers. The review found that sampling shows patient names survive in analytical free-text notes. The architecture must also ensure that only approved care providers may see reidentifiable data. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?

  1. Use Sensitive Data Protection and governed deidentification with appropriate keys
  2. Stage transformations and validate clinical utility before enabling broad analytics
  3. Inspect free-text PII, transformations, ownership and access conditions
  4. Simply rename a column from patient_name to alias

Explanation

Correct Answer

C:

Inspect free-text PII, transformations, ownership and access conditions is the appropriate diagnostic because the observation—sampling shows patient names survive in analytical free-text notes—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (the data warehouse stores masked fields but shared exports retain direct identifiers) before the design is approved.

Incorrect Answers

A:

The alternative “Use Sensitive Data Protection and governed deidentification with appropriate keys” is target architecture selection; it does not establish why the observed path failed. In the reported observation, sampling shows patient names survive in analytical free-text notes. The option “Inspect free-text PII, transformations, ownership and access conditions” instead addresses the requested root-cause evidence.

B:

The alternative “Stage transformations and validate clinical utility before enabling broad analytics” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, sampling shows patient names survive in analytical free-text notes. The option “Inspect free-text PII, transformations, ownership and access conditions” instead addresses the requested root-cause evidence.

D:

Renaming does not remove personal identifiers. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that only approved care providers may see reidentifiable data.

Question 62

City parking payment app plans to update payment token audit. Investigators found that log sample includes unmasked card numbers in error traces, consistent with the reported problem that service records full PAN in debug logs while application database is tokenized. The response must satisfy the requirement that payment operations require minimized log retention and incident-ready evidence. The approved change has been applied. Which validation provides the clearest evidence the original problem is fixed?

  1. Trace cardholder paths through logging, traces and batch exports
  2. Deploy sanitized logging with backfill remediation and evidence preservation
  3. Generate test errors and verify no PAN appears in log destinations
  4. Use TLS on log transport and keep full card numbers indefinitely

Explanation

Correct Answer

C:

Generate test errors and verify no PAN appears in log destinations is a direct acceptance test of the path implicated by log sample includes unmasked card numbers in error traces. It checks that the original risk (service records full PAN in debug logs while application database is tokenized) has actually been controlled and tests that permitted operations still meet the requirement that payment operations require minimized log retention and incident-ready evidence.

Incorrect Answers

A:

The alternative “Trace cardholder paths through logging, traces and batch exports” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, log sample includes unmasked card numbers in error traces. The option “Generate test errors and verify no PAN appears in log destinations” instead addresses the requested acceptance verification.

B:

The alternative “Deploy sanitized logging with backfill remediation and evidence preservation” documents change execution but not its operational acceptance result. In the reported observation, log sample includes unmasked card numbers in error traces. The option “Generate test errors and verify no PAN appears in log destinations” instead addresses the requested acceptance verification.

D:

Transport encryption alone does not minimize sensitive logged content. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that payment operations require minimized log retention and incident-ready evidence.

Question 63

Case study: Regional farmers market network: mobile checkout modernization

Regional farmers market network relies on mobile checkout modernization to deliver its operational commitments. The current architectural problem is that the business case assumes continuous cellular service across remote event sites. The team has recorded this evidence: store surveys show multi-hour connectivity gaps at harvest festivals. Any proposed response must preserve the requirement that offline payments must reconcile without accepting unlimited duplicate orders.

Regional farmers market network plans to update mobile checkout modernization. Investigators found that store surveys show multi-hour connectivity gaps at harvest festivals, consistent with the reported problem that the business case assumes continuous cellular service across remote event sites. The response must satisfy the requirement that offline payments must reconcile without accepting unlimited duplicate orders. The team needs an operations signal rather than another design or one-time test. What should it track?

  1. Run an offline purchase and reconnect cycle while checking uniqueness and ledger totals
  2. Define offline order tokens with bounded spend, duplicate prevention and asynchronous reconciliation
  3. Measure unresolved offline orders, fraud exceptions and end-of-day settlement times
  4. Let every device approve unlimited offline charges without identity checks

Explanation

Correct Answer

C:

Measure unresolved offline orders, fraud exceptions and end-of-day settlement times reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (the business case assumes continuous cellular service across remote event sites) rather than treating the first successful test as permanent assurance.

Incorrect Answers

A:

The alternative “Run an offline purchase and reconnect cycle while checking uniqueness and ledger totals” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, store surveys show multi-hour connectivity gaps at harvest festivals. The option “Measure unresolved offline orders, fraud exceptions and end-of-day settlement times” instead addresses the requested ongoing operational assurance.

B:

The alternative “Define offline order tokens with bounded spend, duplicate prevention and asynchronous reconciliation” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, store surveys show multi-hour connectivity gaps at harvest festivals. The option “Measure unresolved offline orders, fraud exceptions and end-of-day settlement times” instead addresses the requested ongoing operational assurance.

D:

Unlimited offline approvals create unbounded fraud and reconciliation exposure. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that offline payments must reconcile without accepting unlimited duplicate orders.

Question 64

Consider Emergency medical scheduling startup and its feature-flag rollback workload. The issue is that a risky appointment algorithm is released to all users before its impacts can be measured; the current observation is that pilot notes show accepted bookings are reallocated unexpectedly. The team must ensure that existing appointments must remain stable during launch. The target architecture is approved; execution without disruption is the remaining decision. Which rollout action is best?

  1. Modify all stored appointments irreversibly when enabling the feature
  2. Roll out the algorithm to a small cohort while preserving old logic as fallback
  3. Watch cohort-specific booking errors and rollback latency
  4. Use controlled feature flags with experiment guards and durable booking invariants

Explanation

Correct Answer

B:

Roll out the algorithm to a small cohort while preserving old logic as fallback is a controlled means to introduce the approved architecture while meeting the requirement that existing appointments must remain stable during launch. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.

Incorrect Answers

A:

Feature flags cannot undo unprotected database side effects. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that existing appointments must remain stable during launch.

C:

The alternative “Watch cohort-specific booking errors and rollback latency” addresses later monitoring rather than the actual controlled deployment. In the reported observation, pilot notes show accepted bookings are reallocated unexpectedly. The option “Roll out the algorithm to a small cohort while preserving old logic as fallback” instead addresses the requested controlled implementation.

D:

The alternative “Use controlled feature flags with experiment guards and durable booking invariants” describes the chosen design, but not how it is introduced safely. In the reported observation, pilot notes show accepted bookings are reallocated unexpectedly. The option “Roll out the algorithm to a small cohort while preserving old logic as fallback” instead addresses the requested controlled implementation.

Question 65

International telemedicine API plans to update client-library retry behavior. Investigators found that trace shows repeated POST requests after an upstream timeout, consistent with the reported problem that SDK integration retries non-idempotent appointment creation and doubles bookings. The response must satisfy the requirement that appointments must not be created twice for one patient request. The team needs an operations signal rather than another design or one-time test. What should it track?

  1. Use idempotency keys and safe retry policy for mutation requests
  2. Enable unlimited blind retries on every POST
  3. Inject transient timeouts and verify one confirmed appointment
  4. Track duplicate request keys and erroneous retry policy changes

Explanation

Correct Answer

D:

Track duplicate request keys and erroneous retry policy changes reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (SDK integration retries non-idempotent appointment creation and doubles bookings) rather than treating the first successful test as permanent assurance.

Incorrect Answers

A:

The alternative “Use idempotency keys and safe retry policy for mutation requests” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, trace shows repeated POST requests after an upstream timeout. The option “Track duplicate request keys and erroneous retry policy changes” instead addresses the requested ongoing operational assurance.

B:

Unbounded retries can repeat side effects. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that appointments must not be created twice for one patient request.

C:

The alternative “Inject transient timeouts and verify one confirmed appointment” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, trace shows repeated POST requests after an upstream timeout. The option “Track duplicate request keys and erroneous retry policy changes” instead addresses the requested ongoing operational assurance.

Question 66

At Community public library, the Google Cloud design for Terraform landing zone rollout is affected because new projects require approved security settings but Terraform changes are applied directly from laptops. A review found that audit finds mutable local state and unreviewed IAM grants. The proposed response must account for the requirement that public catalog availability must not be interrupted by infrastructure drift. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?

  1. Map infrastructure state, approval roles and module dependencies
  2. Apply reviewed Terraform changes by staged projects with rollback
  3. Give all engineers full project Owner for local Terraform apply
  4. Use remote protected Terraform state and policy-controlled plans

Explanation

Correct Answer

A:

Map infrastructure state, approval roles and module dependencies is the appropriate diagnostic because the observation—audit finds mutable local state and unreviewed IAM grants—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (new projects require approved security settings but Terraform changes are applied directly from laptops) before the design is approved.

Incorrect Answers

B:

The alternative “Apply reviewed Terraform changes by staged projects with rollback” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, audit finds mutable local state and unreviewed IAM grants. The option “Map infrastructure state, approval roles and module dependencies” instead addresses the requested root-cause evidence.

C:

Unreviewed broad changes negate controlled infrastructure rollout. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that public catalog availability must not be interrupted by infrastructure drift.

D:

The alternative “Use remote protected Terraform state and policy-controlled plans” is target architecture selection; it does not establish why the observed path failed. In the reported observation, audit finds mutable local state and unreviewed IAM grants. The option “Map infrastructure state, approval roles and module dependencies” instead addresses the requested root-cause evidence.

Question 67

At International legal services company, the Google Cloud design for cross-border document collaboration is affected because client files are copied to consumer accounts without contractual evidence ownership. A review found that storage audit finds externally shared matter documents with no expiry. The proposed response must account for the requirement that case confidentiality requires explicit client-purpose authorization. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?

  1. Apply scoped sharing, purpose labels and time-limited grants with legal approval
  2. Publish a universally accessible link and rely on legal disclaimers
  3. Track external-sharing exceptions and contract termination
  4. Verify expired clients can no longer read restricted matter files

Explanation

Correct Answer

C:

Track external-sharing exceptions and contract termination reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (client files are copied to consumer accounts without contractual evidence ownership) rather than treating the first successful test as permanent assurance.

Incorrect Answers

A:

The alternative “Apply scoped sharing, purpose labels and time-limited grants with legal approval” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, storage audit finds externally shared matter documents with no expiry. The option “Track external-sharing exceptions and contract termination” instead addresses the requested ongoing operational assurance.

B:

Disclaimers cannot enforce confidential document access. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that case confidentiality requires explicit client-purpose authorization.

D:

The alternative “Verify expired clients can no longer read restricted matter files” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, storage audit finds externally shared matter documents with no expiry. The option “Track external-sharing exceptions and contract termination” instead addresses the requested ongoing operational assurance.

Question 68

Case study: Public broadcaster: live event thumbnail pipeline

Public broadcaster relies on live event thumbnail pipeline to deliver its operational commitments. The current architectural problem is that image conversion jobs scale unpredictably and operators provision fixed VMs manually. The team has recorded this evidence: daily charts show 60x spikes lasting ten minutes with idle nights. Any proposed response must preserve the requirement that uploads require isolated execution and no long-lived server state.

At Public broadcaster, the live event thumbnail pipeline workload has a documented risk: image conversion jobs scale unpredictably and operators provision fixed VMs manually. The review found that daily charts show 60x spikes lasting ten minutes with idle nights. The architecture must also ensure that uploads require isolated execution and no long-lived server state. What follow-up metric or alert will identify emerging failures after the initial acceptance test?

  1. Send production-like burst uploads and check output integrity and run latency
  2. Operate a fixed single VM with no scaling or restart policy
  3. Select Cloud Run for stateless event-driven conversion with managed scaling
  4. Monitor instance scaling, errors and cost per generated image

Explanation

Correct Answer

D:

Monitor instance scaling, errors and cost per generated image reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (image conversion jobs scale unpredictably and operators provision fixed VMs manually) rather than treating the first successful test as permanent assurance.

Incorrect Answers

A:

The alternative “Send production-like burst uploads and check output integrity and run latency” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, daily charts show 60x spikes lasting ten minutes with idle nights. The option “Monitor instance scaling, errors and cost per generated image” instead addresses the requested ongoing operational assurance.

B:

A fixed VM creates capacity bottlenecks and idle cost. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that uploads require isolated execution and no long-lived server state.

C:

The alternative “Select Cloud Run for stateless event-driven conversion with managed scaling” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, daily charts show 60x spikes lasting ten minutes with idle nights. The option “Monitor instance scaling, errors and cost per generated image” instead addresses the requested ongoing operational assurance.

Question 69

Consider Regional vehicle-parts supplier and its hybrid stock synchronization workload. The issue is that headquarters reaches Google Cloud only through one IPsec tunnel that drops during maintenance; the current observation is that network log shows packets re-route onto a congested internet path after the gateway reboot. The team must ensure that inventory updates need redundant private routing to two regions. The target architecture is approved; execution without disruption is the remaining decision. Which rollout action is best?

  1. Establish both encrypted paths and verify advertised routes before removing the old tunnel
  2. Use a single static VPN gateway and advertise a default public route for all stock traffic
  3. Use redundant HA VPN gateways with Cloud Router and independent peer paths
  4. Alert on tunnel status, route withdrawals and peer latency

Explanation

Correct Answer

A:

Establish both encrypted paths and verify advertised routes before removing the old tunnel is a controlled means to introduce the approved architecture while meeting the requirement that inventory updates need redundant private routing to two regions. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.

Incorrect Answers

B:

One tunnel and unscoped route reproduce the outage and security risk. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that inventory updates need redundant private routing to two regions.

C:

The alternative “Use redundant HA VPN gateways with Cloud Router and independent peer paths” describes the chosen design, but not how it is introduced safely. In the reported observation, network log shows packets re-route onto a congested internet path after the gateway reboot. The option “Establish both encrypted paths and verify advertised routes before removing the old tunnel” instead addresses the requested controlled implementation.

D:

The alternative “Alert on tunnel status, route withdrawals and peer latency” addresses later monitoring rather than the actual controlled deployment. In the reported observation, network log shows packets re-route onto a congested internet path after the gateway reboot. The option “Establish both encrypted paths and verify advertised routes before removing the old tunnel” instead addresses the requested controlled implementation.

Question 70

At Healthcare payments startup, the release regression validation workload has a documented risk: team tests only HTTP status after replacing the production authentication component. The review found that incident reveals token expiry and cross-tenant access tests were omitted. The architecture must also ensure that payments and patient data require safe release acceptance. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?

  1. Build automated integration tests for valid and denied authorization paths
  2. Treat an HTTP 200 response as proof all identity controls work
  3. Deploy new authentication through canary traffic with rollback on errors
  4. Map critical auth flows, negative tests and dependency boundaries

Explanation

Correct Answer

D:

Map critical auth flows, negative tests and dependency boundaries is the appropriate diagnostic because the observation—incident reveals token expiry and cross-tenant access tests were omitted—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (team tests only HTTP status after replacing the production authentication component) before the design is approved.

Incorrect Answers

A:

The alternative “Build automated integration tests for valid and denied authorization paths” is target architecture selection; it does not establish why the observed path failed. In the reported observation, incident reveals token expiry and cross-tenant access tests were omitted. The option “Map critical auth flows, negative tests and dependency boundaries” instead addresses the requested root-cause evidence.

B:

A success code says nothing about unauthorized access paths. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that payments and patient data require safe release acceptance.

C:

The alternative “Deploy new authentication through canary traffic with rollback on errors” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, incident reveals token expiry and cross-tenant access tests were omitted. The option “Map critical auth flows, negative tests and dependency boundaries” instead addresses the requested root-cause evidence.

Google Cloud Certified - Professional Cloud Architect (Professional Cloud Architect) Practice Tests