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 2

Question 10

At City parking payment app, the Google Cloud design for payment token audit is affected because service records full PAN in debug logs while application database is tokenized. A review found that log sample includes unmasked card numbers in error traces. The proposed response must account for the requirement that payment operations require minimized log retention and incident-ready evidence. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?

  1. Trace cardholder paths through logging, traces and batch exports
  2. Use TLS on log transport and keep full card numbers indefinitely
  3. Deploy sanitized logging with backfill remediation and evidence preservation
  4. Remove PAN from telemetry and apply scoped tokenization and log redaction

Explanation

Correct Answer

A:

Trace cardholder paths through logging, traces and batch exports is the appropriate diagnostic because the observation—log sample includes unmasked card numbers in error traces—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (service records full PAN in debug logs while application database is tokenized) before the design is approved.

Incorrect Answers

B:

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

C:

The alternative “Deploy sanitized logging with backfill remediation and evidence preservation” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, log sample includes unmasked card numbers in error traces. The option “Trace cardholder paths through logging, traces and batch exports” instead addresses the requested root-cause evidence.

D:

The alternative “Remove PAN from telemetry and apply scoped tokenization and log redaction” is target architecture selection; it does not establish why the observed path failed. In the reported observation, log sample includes unmasked card numbers in error traces. The option “Trace cardholder paths through logging, traces and batch exports” instead addresses the requested root-cause evidence.

Question 11

Financial consumer lender plans to update PCI data encryption separation. Investigators found that role review shows one service account can decrypt and administer Cloud KMS, consistent with the reported problem that application developers can read a cardholder encryption key and production data. The response must satisfy the requirement that PCI program requires separation of key administration and data processing. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?

  1. Map encryption/decrypt flows, identity grants and cardholder scope
  2. Apply separate IAM roles for key administration and cryptographic use, with CMEK where supported
  3. Rotate permissions and test service continuity during KMS grant changes
  4. Set a shared spreadsheet password on exported plaintext cards

Explanation

Correct Answer

A:

Map encryption/decrypt flows, identity grants and cardholder scope is the appropriate diagnostic because the observation—role review shows one service account can decrypt and administer Cloud KMS—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (application developers can read a cardholder encryption key and production data) before the design is approved.

Incorrect Answers

B:

The alternative “Apply separate IAM roles for key administration and cryptographic use, with CMEK where supported” is target architecture selection; it does not establish why the observed path failed. In the reported observation, role review shows one service account can decrypt and administer Cloud KMS. The option “Map encryption/decrypt flows, identity grants and cardholder scope” instead addresses the requested root-cause evidence.

C:

The alternative “Rotate permissions and test service continuity during KMS grant changes” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, role review shows one service account can decrypt and administer Cloud KMS. The option “Map encryption/decrypt flows, identity grants and cardholder scope” instead addresses the requested root-cause evidence.

D:

A shared password does not meet secure key custody requirements. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that PCI program requires separation of key administration and data processing.

Question 12

Case study: Regional electric utility: production support handoff

Regional electric utility relies on production support handoff to deliver its operational commitments. The current architectural problem is that platform team deploys new observability agents without defining who handles alerts. The team has recorded this evidence: incident rehearsal finds metrics present but no pager owner. Any proposed response must preserve the requirement that grid control support must remain staffed around the clock.

Regional electric utility plans to update production support handoff. Investigators found that incident rehearsal finds metrics present but no pager owner, consistent with the reported problem that platform team deploys new observability agents without defining who handles alerts. The response must satisfy the requirement that grid control support must remain staffed around the clock. The design review is over and production introduction is next. Which action is the best fit?

  1. Define operable SLOs, escalation routing and safe remediation authority
  2. Introduce new alarms to a trained response cohort with simulated pages
  3. Watch unowned pages, stale runbooks and response latency
  4. Enable thousands of pages with no routing or training

Explanation

Correct Answer

B:

Introduce new alarms to a trained response cohort with simulated pages is a controlled means to introduce the approved architecture while meeting the requirement that grid control support must remain staffed around the clock. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.

Incorrect Answers

A:

The alternative “Define operable SLOs, escalation routing and safe remediation authority” describes the chosen design, but not how it is introduced safely. In the reported observation, incident rehearsal finds metrics present but no pager owner. The option “Introduce new alarms to a trained response cohort with simulated pages” instead addresses the requested controlled implementation.

C:

The alternative “Watch unowned pages, stale runbooks and response latency” addresses later monitoring rather than the actual controlled deployment. In the reported observation, incident rehearsal finds metrics present but no pager owner. The option “Introduce new alarms to a trained response cohort with simulated pages” instead addresses the requested controlled implementation.

D:

Unowned alert volume does not create actionable operations. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that grid control support must remain staffed around the clock.

Question 13

At Regional trucking marketplace, the Google Cloud design for custom business metrics is affected because application metrics show 200 responses even as delivery confirmations are silently dropped. A review found that business reconciliation finds missing delivery events despite healthy pods. The proposed response must account for the requirement that the service must confirm each accepted shipment within five minutes. Which controlled implementation should be used to preserve operational continuity during the change?

  1. Use only VM CPU to measure whether shipments were delivered
  2. Track unconfirmed shipments and processing delay by customer cohort
  3. Publish business delivery-success metrics and SLOs with trace correlation
  4. Instrument the critical workflow and pilot actionable alerting

Explanation

Correct Answer

D:

Instrument the critical workflow and pilot actionable alerting is a controlled means to introduce the approved architecture while meeting the requirement that the service must confirm each accepted shipment within five minutes. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.

Incorrect Answers

A:

Healthy CPU is not evidence of successful business transactions. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that the service must confirm each accepted shipment within five minutes.

B:

The alternative “Track unconfirmed shipments and processing delay by customer cohort” addresses later monitoring rather than the actual controlled deployment. In the reported observation, business reconciliation finds missing delivery events despite healthy pods. The option “Instrument the critical workflow and pilot actionable alerting” instead addresses the requested controlled implementation.

C:

The alternative “Publish business delivery-success metrics and SLOs with trace correlation” describes the chosen design, but not how it is introduced safely. In the reported observation, business reconciliation finds missing delivery events despite healthy pods. The option “Instrument the critical workflow and pilot actionable alerting” instead addresses the requested controlled implementation.

Question 14

At Medical supply chain, the Google Cloud design for CDC job performance regression is affected because a nightly database export finishes late despite unchanged source volume. A review found that telemetry shows a new transformation now triggers full-table reloads. The proposed response must account for the requirement that hospital inventory reports must arrive before morning replenishment. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?

  1. Measure end-to-end finish time and exact record-level parity
  2. Change to incremental CDC processing with checkpointed offsets
  3. Monitor bytes scanned, checkpoint lag and daily delivery misses
  4. Provision more dashboard servers while keeping the full reload

Explanation

Correct Answer

C:

Monitor bytes scanned, checkpoint lag and daily delivery misses reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a nightly database export finishes late despite unchanged source volume) rather than treating the first successful test as permanent assurance.

Incorrect Answers

A:

The alternative “Measure end-to-end finish time and exact record-level parity” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, telemetry shows a new transformation now triggers full-table reloads. The option “Monitor bytes scanned, checkpoint lag and daily delivery misses” instead addresses the requested ongoing operational assurance.

B:

The alternative “Change to incremental CDC processing with checkpointed offsets” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, telemetry shows a new transformation now triggers full-table reloads. The option “Monitor bytes scanned, checkpoint lag and daily delivery misses” instead addresses the requested ongoing operational assurance.

D:

Dashboard compute does not correct an inefficient ingestion path. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that hospital inventory reports must arrive before morning replenishment.

Question 15

At International cargo platform, the operational excellence ownership workload has a documented risk: three independent teams deploy a critical shipment API without shared incident response rules. The review found that postmortem shows repeat outages with no accountable follow-up owner. The architecture must also ensure that shipment tracking must meet a documented four-nine availability SLO. What follow-up metric or alert will identify emerging failures after the initial acceptance test?

  1. Set SLOs, runbooks and assigned reliability improvement backlog with accountable owners
  2. Declare the system reliable because developers resolved one emergency manually
  3. Run an incident simulation and verify responders follow escalation and restoration steps
  4. Review error-budget burn, recurring incidents and overdue corrective actions

Explanation

Correct Answer

D:

Review error-budget burn, recurring incidents and overdue corrective actions reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (three independent teams deploy a critical shipment API without shared incident response rules) rather than treating the first successful test as permanent assurance.

Incorrect Answers

A:

The alternative “Set SLOs, runbooks and assigned reliability improvement backlog with accountable owners” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, postmortem shows repeat outages with no accountable follow-up owner. The option “Review error-budget burn, recurring incidents and overdue corrective actions” instead addresses the requested ongoing operational assurance.

B:

One heroic recovery is not an operating model. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that shipment tracking must meet a documented four-nine availability SLO.

C:

The alternative “Run an incident simulation and verify responders follow escalation and restoration steps” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, postmortem shows repeat outages with no accountable follow-up owner. The option “Review error-budget burn, recurring incidents and overdue corrective actions” instead addresses the requested ongoing operational assurance.

Question 16

At Industrial robotics startup, the Google Cloud design for edge-device digital twin is affected because architects assume GPU inference remains constant even though future robots gain local accelerators. A review found that hardware roadmap shows some plants will run most inference at the edge. The proposed response must account for the requirement that plant safety systems must not depend on public network availability. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?

  1. Design split edge/cloud inference with versioned model contracts and offline safety path
  2. Force all safety-critical inference through a distant cloud endpoint
  3. Track unsupported hardware, model rollout lag and cloud inference spend
  4. Disable WAN and confirm local safe operation with version-compatible models

Explanation

Correct Answer

C:

Track unsupported hardware, model rollout lag and cloud inference spend reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (architects assume GPU inference remains constant even though future robots gain local accelerators) rather than treating the first successful test as permanent assurance.

Incorrect Answers

A:

The alternative “Design split edge/cloud inference with versioned model contracts and offline safety path” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, hardware roadmap shows some plants will run most inference at the edge. The option “Track unsupported hardware, model rollout lag and cloud inference spend” instead addresses the requested ongoing operational assurance.

B:

WAN outages would compromise real-time plant operation. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that plant safety systems must not depend on public network availability.

D:

The alternative “Disable WAN and confirm local safe operation with version-compatible models” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, hardware roadmap shows some plants will run most inference at the edge. The option “Track unsupported hardware, model rollout lag and cloud inference spend” instead addresses the requested ongoing operational assurance.

Question 17

At Hospital imaging research unit, the Google Cloud design for regulated data classification is affected because an AI training workflow ingests medical reports with accidental patient identifiers. A review found that dataset profiler finds patient IDs inside free-text radiology comments. The proposed response must account for the requirement that only approved deidentified inputs may enter model training. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?

  1. Verify holdout samples contain no prohibited identifiers while clinical utility remains
  2. Trust a generic prompt to remove every patient ID from raw input
  3. Use Sensitive Data Protection inspection/deidentification with governance controls
  4. Track newly detected sensitive patterns, policy versions and false negatives

Explanation

Correct Answer

D:

Track newly detected sensitive patterns, policy versions and false negatives reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (an AI training workflow ingests medical reports with accidental patient identifiers) rather than treating the first successful test as permanent assurance.

Incorrect Answers

A:

The alternative “Verify holdout samples contain no prohibited identifiers while clinical utility remains” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, dataset profiler finds patient IDs inside free-text radiology comments. The option “Track newly detected sensitive patterns, policy versions and false negatives” instead addresses the requested ongoing operational assurance.

B:

Prompt guidance is not a deterministic privacy-control boundary. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that only approved deidentified inputs may enter model training.

C:

The alternative “Use Sensitive Data Protection inspection/deidentification with governance controls” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, dataset profiler finds patient IDs inside free-text radiology comments. The option “Track newly detected sensitive patterns, policy versions and false negatives” instead addresses the requested ongoing operational assurance.

Question 18

At Multinational retailer, the checkout cost modernization workload has a documented risk: a newly acquired brand will double country coverage and tax interfaces after migration. The review found that requirements show separate national tax authorities and holiday peak profiles. The architecture must also ensure that checkout must preserve local residency and transparent tax audit. What enduring Google Cloud design should the team choose now that the failure mode is understood?

  1. Identify regulatory and demand changes expected over the next two years
  2. Track change requests, country-level latency and tax-policy drift
  3. Use modular regional tax integration boundaries with portable checkout contracts
  4. Encode every country's tax rules in a single hard-coded pricing function

Explanation

Correct Answer

C:

Use modular regional tax integration boundaries with portable checkout contracts targets the underlying issue (a newly acquired brand will double country coverage and tax interfaces after migration) rather than merely reporting symptoms. It also preserves the required outcome (checkout must preserve local residency and transparent tax audit), which a target-state design must satisfy.

Incorrect Answers

A:

The alternative “Identify regulatory and demand changes expected over the next two years” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, requirements show separate national tax authorities and holiday peak profiles. The option “Use modular regional tax integration boundaries with portable checkout contracts” instead addresses the requested architecture selection.

B:

The alternative “Track change requests, country-level latency and tax-policy drift” measures results without defining the preventive design now required. In the reported observation, requirements show separate national tax authorities and holiday peak profiles. The option “Use modular regional tax integration boundaries with portable checkout contracts” instead addresses the requested architecture selection.

D:

Hardcoded global tax logic becomes fragile and difficult to audit. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that checkout must preserve local residency and transparent tax audit.

Question 19

At Multinational travel support service, the multilingual customer request assistant workload has a documented risk: an architecture team confuses basic FAQ retrieval with an agent allowed to change reservations. The review found that requirements show ticket search and refund actions have different authorization obligations. The architecture must also ensure that refunds require authenticated approval and audit. What follow-up metric or alert will identify emerging failures after the initial acceptance test?

  1. Monitor action denials, groundedness and escalated human approvals
  2. Test that an unauthenticated chat cannot invoke refunds despite valid FAQ answers
  3. Use a grounded search-based assistant and keep refund execution behind an authenticated tool policy
  4. Give every search result direct permission to execute refund APIs

Explanation

Correct Answer

A:

Monitor action denials, groundedness and escalated human approvals reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (an architecture team confuses basic FAQ retrieval with an agent allowed to change reservations) rather than treating the first successful test as permanent assurance.

Incorrect Answers

B:

The alternative “Test that an unauthenticated chat cannot invoke refunds despite valid FAQ answers” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, requirements show ticket search and refund actions have different authorization obligations. The option “Monitor action denials, groundedness and escalated human approvals” instead addresses the requested ongoing operational assurance.

C:

The alternative “Use a grounded search-based assistant and keep refund execution behind an authenticated tool policy” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, requirements show ticket search and refund actions have different authorization obligations. The option “Monitor action denials, groundedness and escalated human approvals” instead addresses the requested ongoing operational assurance.

D:

Retrieved text is untrusted input, not authorization. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that refunds require authenticated approval and audit.

Question 20

Case study: Payments risk laboratory: encryption key governance

Payments risk laboratory relies on encryption key governance to deliver its operational commitments. The current architectural problem is that payment data uses default encryption but contract requires customer control over key rotation. The team has recorded this evidence: key inventory shows provider-managed keys with no customer-managed lifecycle. Any proposed response must preserve the requirement that regulated card records require tracked access and planned key retirement.

The encryption key governance environment at Payments risk laboratory faces this issue: payment data uses default encryption but contract requires customer control over key rotation. Supporting evidence shows that key inventory shows provider-managed keys with no customer-managed lifecycle. The architect must preserve the requirement that regulated card records require tracked access and planned key retirement. Which migration or rollout step best manages risk, dependencies and reversibility?

  1. Choose Cloud KMS CMEK where supported with separated key administrators and encryption users
  2. Place plaintext encryption keys in shared project metadata
  3. Migrate eligible resources to approved keys with tested grant/rollback
  4. Monitor key disable events, grant drift and rotation compliance

Explanation

Correct Answer

C:

Migrate eligible resources to approved keys with tested grant/rollback is a controlled means to introduce the approved architecture while meeting the requirement that regulated card records require tracked access and planned key retirement. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.

Incorrect Answers

A:

The alternative “Choose Cloud KMS CMEK where supported with separated key administrators and encryption users” describes the chosen design, but not how it is introduced safely. In the reported observation, key inventory shows provider-managed keys with no customer-managed lifecycle. The option “Migrate eligible resources to approved keys with tested grant/rollback” instead addresses the requested controlled implementation.

B:

Shared metadata does not provide protected KMS custody. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that regulated card records require tracked access and planned key retirement.

D:

The alternative “Monitor key disable events, grant drift and rotation compliance” addresses later monitoring rather than the actual controlled deployment. In the reported observation, key inventory shows provider-managed keys with no customer-managed lifecycle. The option “Migrate eligible resources to approved keys with tested grant/rollback” instead addresses the requested controlled implementation.

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