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 22

Question 210

Case study: Global research cloud: project-to-project data movement

Global research cloud relies on project-to-project data movement to deliver its operational commitments. The current architectural problem is that a sensitive BigQuery dataset is read by a broad reporting service account. The team has recorded this evidence: query logs show access from an unrelated project outside the research boundary. Any proposed response must preserve the requirement that only approved analytical workloads may join identifiable records.

Global research cloud plans to update project-to-project data movement. Investigators found that query logs show access from an unrelated project outside the research boundary, consistent with the reported problem that a sensitive BigQuery dataset is read by a broad reporting service account. The response must satisfy the requirement that only approved analytical workloads may join identifiable records. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?

  1. Combine dataset IAM with supported VPC Service Controls restrictions
  2. Inspect principals, service perimeter scope and destination datasets
  3. Assume a private IP alone prevents data exfiltration through API calls
  4. Apply access changes in dry-run and validate legitimate research exports

Explanation

Correct Answer

B:

Inspect principals, service perimeter scope and destination datasets is the appropriate diagnostic because the observation—query logs show access from an unrelated project outside the research boundary—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (a sensitive BigQuery dataset is read by a broad reporting service account) before the design is approved.

Incorrect Answers

A:

The alternative “Combine dataset IAM with supported VPC Service Controls restrictions” is target architecture selection; it does not establish why the observed path failed. In the reported observation, query logs show access from an unrelated project outside the research boundary. The option “Inspect principals, service perimeter scope and destination datasets” instead addresses the requested root-cause evidence.

C:

Network privacy alone cannot enforce Google API data boundaries. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that only approved analytical workloads may join identifiable records.

D:

The alternative “Apply access changes in dry-run and validate legitimate research exports” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, query logs show access from an unrelated project outside the research boundary. The option “Inspect principals, service perimeter scope and destination datasets” instead addresses the requested root-cause evidence.

Question 211

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.

At Regional electric utility, the production support handoff workload has a documented risk: platform team deploys new observability agents without defining who handles alerts. The review found that incident rehearsal finds metrics present but no pager owner. The architecture must also ensure that grid control support must remain staffed around the clock. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?

  1. Define operable SLOs, escalation routing and safe remediation authority
  2. Introduce new alarms to a trained response cohort with simulated pages
  3. Enable thousands of pages with no routing or training
  4. Identify alert severities, runbook gaps and on-call ownership

Explanation

Correct Answer

D:

Identify alert severities, runbook gaps and on-call ownership is the appropriate diagnostic because the observation—incident rehearsal finds metrics present but no pager owner—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (platform team deploys new observability agents without defining who handles alerts) before the design is approved.

Incorrect Answers

A:

The alternative “Define operable SLOs, escalation routing and safe remediation authority” is target architecture selection; it does not establish why the observed path failed. In the reported observation, incident rehearsal finds metrics present but no pager owner. The option “Identify alert severities, runbook gaps and on-call ownership” instead addresses the requested root-cause evidence.

B:

The alternative “Introduce new alarms to a trained response cohort with simulated pages” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, incident rehearsal finds metrics present but no pager owner. The option “Identify alert severities, runbook gaps and on-call ownership” instead addresses the requested root-cause evidence.

C:

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

Question 212

At National investment office, the Google Cloud design for emergency break-glass access is affected because a single admin group controls production recovery and can also edit security logs. A review found that tabletop shows no independent emergency account if primary IdP fails. The proposed response must account for the requirement that recovery access must be auditable and tightly time-bound. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?

  1. Simulate IdP outage and confirm authorized break-glass restores service with logs
  2. Review emergency usage, stale accounts and notification delay
  3. Define protected break-glass identities with separated ownership and alerts
  4. Share one break-glass password in the team chat channel

Explanation

Correct Answer

B:

Review emergency usage, stale accounts and notification delay reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a single admin group controls production recovery and can also edit security logs) rather than treating the first successful test as permanent assurance.

Incorrect Answers

A:

The alternative “Simulate IdP outage and confirm authorized break-glass restores service with logs” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, tabletop shows no independent emergency account if primary IdP fails. The option “Review emergency usage, stale accounts and notification delay” instead addresses the requested ongoing operational assurance.

C:

The alternative “Define protected break-glass identities with separated ownership and alerts” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, tabletop shows no independent emergency account if primary IdP fails. The option “Review emergency usage, stale accounts and notification delay” instead addresses the requested ongoing operational assurance.

D:

A widely shared emergency secret is not protected or attributable. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that recovery access must be auditable and tightly time-bound.

Question 213

Case study: Global coffee chain: Cloud Logging retention

Global coffee chain relies on Cloud Logging retention to deliver its operational commitments. The current architectural problem is that project logs disappear after 30 days but fraud investigations extend six months. The team has recorded this evidence: retention check shows no archived log bucket for point-of-sale events. Any proposed response must preserve the requirement that fraud evidence must be retrievable under restricted access.

Global coffee chain plans to update Cloud Logging retention. Investigators found that retention check shows no archived log bucket for point-of-sale events, consistent with the reported problem that project logs disappear after 30 days but fraud investigations extend six months. The response must satisfy the requirement that fraud evidence must be retrievable under restricted access. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?

  1. Use suitable log buckets/sinks with governed retention and protected access
  2. Identify mandatory log classes, retention duration and writer roles
  3. Configure exports with delivery tests and separate audit ownership
  4. Monitor sink health, retention policy drift and archive retrieval
  5. Rely only on application console scrollback as the audit archive

Explanation

Correct Answers

A:

Use suitable log buckets/sinks with governed retention and protected access targets the underlying issue (project logs disappear after 30 days but fraud investigations extend six months) rather than merely reporting symptoms. It also preserves the required outcome (fraud evidence must be retrievable under restricted access), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.

C:

Configure exports with delivery tests and separate audit ownership is a controlled means to introduce the approved architecture while meeting the requirement that fraud evidence must be retrievable under restricted access. 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.

Incorrect Answers

B:

This diagnoses the original issue (project logs disappear after 30 days but fraud investigations extend six months), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.

D:

Monitoring Cloud Logging retention for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: project logs disappear after 30 days but fraud investigations extend six months.

E:

Transient console views do not meet retention and integrity needs. The shortcut does not supply the requested design and safe rollout for Cloud Logging retention, where retention check shows no archived log bucket for point-of-sale events.

Question 214

Consider Cloud analytics consultancy and its artifact provenance release workload. The issue is that operations deploy a container whose mutable latest tag no longer matches the tested build; the current observation is that digest comparison finds production image differs from CI artifact. The team must ensure that client datasets must be processed only by reviewed releases. Which acceptance test should demonstrate both protection against the failure and continued authorized service?

  1. Compare production digest to signed tested artifact and reject mismatches
  2. Let production pull latest tags directly from an open registry
  3. Promote approved digest across environments with recorded rollback
  4. Trace build artifact digests and promotion history

Explanation

Correct Answer

A:

Compare production digest to signed tested artifact and reject mismatches is a direct acceptance test of the path implicated by digest comparison finds production image differs from CI artifact. It checks that the original risk (operations deploy a container whose mutable latest tag no longer matches the tested build) has actually been controlled and tests that permitted operations still meet the requirement that client datasets must be processed only by reviewed releases.

Incorrect Answers

B:

Mutable unaudited tags can substitute unapproved code. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that client datasets must be processed only by reviewed releases.

C:

The alternative “Promote approved digest across environments with recorded rollback” documents change execution but not its operational acceptance result. In the reported observation, digest comparison finds production image differs from CI artifact. The option “Compare production digest to signed tested artifact and reject mismatches” instead addresses the requested acceptance verification.

D:

The alternative “Trace build artifact digests and promotion history” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, digest comparison finds production image differs from CI artifact. The option “Compare production digest to signed tested artifact and reject mismatches” instead addresses the requested acceptance verification.

Question 215

Consider Financial consumer lender and its PCI data encryption separation workload. The issue is that application developers can read a cardholder encryption key and production data; the current observation is that role review shows one service account can decrypt and administer Cloud KMS. The team must ensure that PCI program requires separation of key administration and data processing. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?

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

Explanation

Correct Answers

B:

Apply separate IAM roles for key administration and cryptographic use, with CMEK where supported targets the underlying issue (application developers can read a cardholder encryption key and production data) rather than merely reporting symptoms. It also preserves the required outcome (PCI program requires separation of key administration and data processing), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.

D:

Rotate permissions and test service continuity during KMS grant changes is a controlled means to introduce the approved architecture while meeting the requirement that PCI program requires separation of key administration and data processing. 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.

Incorrect Answers

A:

Monitoring PCI data encryption separation for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: application developers can read a cardholder encryption key and production data.

C:

This diagnoses the original issue (application developers can read a cardholder encryption key and production data), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.

E:

A shared password does not meet secure key custody requirements. The shortcut does not supply the requested design and safe rollout for PCI data encryption separation, where role review shows one service account can decrypt and administer Cloud KMS.

Question 216

Case study: Global coffee chain: Cloud Logging retention

Global coffee chain relies on Cloud Logging retention to deliver its operational commitments. The current architectural problem is that project logs disappear after 30 days but fraud investigations extend six months. The team has recorded this evidence: retention check shows no archived log bucket for point-of-sale events. Any proposed response must preserve the requirement that fraud evidence must be retrievable under restricted access.

At Global coffee chain, the Google Cloud design for Cloud Logging retention is affected because project logs disappear after 30 days but fraud investigations extend six months. A review found that retention check shows no archived log bucket for point-of-sale events. The proposed response must account for the requirement that fraud evidence must be retrievable under restricted access. A deployment ticket has been closed. What direct evidence would justify solution signoff?

  1. Configure exports with delivery tests and separate audit ownership
  2. Rely only on application console scrollback as the audit archive
  3. Identify mandatory log classes, retention duration and writer roles
  4. Retrieve an older synthetic fraud event and confirm its integrity

Explanation

Correct Answer

D:

Retrieve an older synthetic fraud event and confirm its integrity is a direct acceptance test of the path implicated by retention check shows no archived log bucket for point-of-sale events. It checks that the original risk (project logs disappear after 30 days but fraud investigations extend six months) has actually been controlled and tests that permitted operations still meet the requirement that fraud evidence must be retrievable under restricted access.

Incorrect Answers

A:

The alternative “Configure exports with delivery tests and separate audit ownership” documents change execution but not its operational acceptance result. In the reported observation, retention check shows no archived log bucket for point-of-sale events. The option “Retrieve an older synthetic fraud event and confirm its integrity” instead addresses the requested acceptance verification.

B:

Transient console views do not meet retention and integrity needs. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that fraud evidence must be retrievable under restricted access.

C:

The alternative “Identify mandatory log classes, retention duration and writer roles” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, retention check shows no archived log bucket for point-of-sale events. The option “Retrieve an older synthetic fraud event and confirm its integrity” instead addresses the requested acceptance verification.

Question 217

National blood supply service plans to update database schema rollout. Investigators found that staging test shows older binary cannot read new tables, consistent with the reported problem that application instances migrate separately from the database schema and old pods fail on renamed columns. The response must satisfy the requirement that donation inventory cannot pause through rolling deployment. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?

  1. Analyze schema backward compatibility and the release dependency graph
  2. Monitor query failures, dead code paths and migration exceptions
  3. Apply additive schema first, migrate services, then remove old columns after validation
  4. Define expand-migrate-contract schema evolution with compatible views
  5. Drop the old column before the old application instances are drained

Explanation

Correct Answers

C:

Apply additive schema first, migrate services, then remove old columns after validation is a controlled means to introduce the approved architecture while meeting the requirement that donation inventory cannot pause through rolling deployment. 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.

D:

Define expand-migrate-contract schema evolution with compatible views targets the underlying issue (application instances migrate separately from the database schema and old pods fail on renamed columns) rather than merely reporting symptoms. It also preserves the required outcome (donation inventory cannot pause through rolling deployment), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.

Incorrect Answers

A:

This diagnoses the original issue (application instances migrate separately from the database schema and old pods fail on renamed columns), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.

B:

Monitoring database schema rollout for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: application instances migrate separately from the database schema and old pods fail on renamed columns.

E:

A destructive schema change strands older active binaries. The shortcut does not supply the requested design and safe rollout for database schema rollout, where staging test shows older binary cannot read new tables.

Question 218

At Regional airline, the Google Cloud design for crew roster API is affected because a database primary restart causes regional crews to lose schedules for an entire shift. A review found that failure logs show read-only standby exists but application uses only one endpoint. The proposed response must account for the requirement that dispatch must read the last approved crew plan during recovery. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?

  1. Track replication lag, failover times and stale roster warnings
  2. Point every client to an unreplicated local file as the only source
  3. Force primary failover and verify authorized roster reads within RTO
  4. Use high-availability database failover and a validated read-only contingency view

Explanation

Correct Answer

A:

Track replication lag, failover times and stale roster warnings reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a database primary restart causes regional crews to lose schedules for an entire shift) rather than treating the first successful test as permanent assurance.

Incorrect Answers

B:

An uncontrolled copy can yield inconsistent safety-critical rosters. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that dispatch must read the last approved crew plan during recovery.

C:

The alternative “Force primary failover and verify authorized roster reads within RTO” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, failure logs show read-only standby exists but application uses only one endpoint. The option “Track replication lag, failover times and stale roster warnings” instead addresses the requested ongoing operational assurance.

D:

The alternative “Use high-availability database failover and a validated read-only contingency view” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, failure logs show read-only standby exists but application uses only one endpoint. The option “Track replication lag, failover times and stale roster warnings” instead addresses the requested ongoing operational assurance.

Question 219

At Public archive network, the support dependency escalation workload has a documented risk: staff cannot resolve sporadic object read failures because the case lacks request IDs. The review found that support replies repeatedly ask for missing bucket and operation context. The architecture must also ensure that public document retrieval must be restored quickly without exposing personal data. Select THREE evidence activities to cover (1) diagnosis before design, (2) direct post-change acceptance, and (3) continued operational monitoring. Which THREE fit those stages?

  1. Send complete private object contents and unrestricted credentials in a support email
  2. Collect failing request identifiers, timestamps, bucket location and service status
  3. Track repeated evidence gaps and delayed support resolution
  4. Reproduce failures with sanitized requests and confirm the right support evidence is collected
  5. Define support runbooks with minimal reproducible evidence and safe redaction
  6. Exclude the affected dependency from all future tests and incident metrics to simplify reporting

Explanation

Correct Answers

B:

Collect failing request identifiers, timestamps, bucket location and service status is the appropriate diagnostic because the observation—support replies repeatedly ask for missing bucket and operation context—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (staff cannot resolve sporadic object read failures because the case lacks request IDs) before the design is approved. It supplies the pre-design diagnostic evidence requested.

C:

Track repeated evidence gaps and delayed support resolution reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (staff cannot resolve sporadic object read failures because the case lacks request IDs) rather than treating the first successful test as permanent assurance. It supplies the ongoing observation requested.

D:

Reproduce failures with sanitized requests and confirm the right support evidence is collected is a direct acceptance test of the path implicated by support replies repeatedly ask for missing bucket and operation context. It checks that the original risk (staff cannot resolve sporadic object read failures because the case lacks request IDs) has actually been controlled and tests that permitted operations still meet the requirement that public document retrieval must be restored quickly without exposing personal data. It supplies the separate post-change acceptance result requested.

Incorrect Answers

A:

Support evidence should be sufficient and minimized, not a credential leak. It cannot satisfy the required evidence stages.

E:

Designing support dependency escalation addresses the root cause, but this specific three-part question asks for evidence to diagnose, accept and continuously verify the response to staff cannot resolve sporadic object read failures because the case lacks request IDs, not another design proposal.

F:

Omitting the relevant dependency from testing and monitoring would hide, not correct, recurrence of the failure. In particular, the observed issue was: support replies repeatedly ask for missing bucket and operation context.

Question 220

Case study: Telehealth teleconsultation: regulated regional failover

Telehealth teleconsultation relies on regulated regional failover to deliver its operational commitments. The current architectural problem is that the recovery design sends patient consultations to a region forbidden by local processing rules. The team has recorded this evidence: failover plan lists a default backup service on another continent. Any proposed response must preserve the requirement that clinical service must be recoverable inside approved national boundaries.

Consider Telehealth teleconsultation and its regulated regional failover workload. The issue is that the recovery design sends patient consultations to a region forbidden by local processing rules; the current observation is that failover plan lists a default backup service on another continent. The team must ensure that clinical service must be recoverable inside approved national boundaries. The team has completed discovery. Which preventive or corrective architecture is most appropriate?

  1. Design in-country redundant service and storage with compliant backup
  2. Monitor regional replication, legal changes and failover access logs
  3. Review legal location rules and failover data-plane traffic
  4. Assume a foreign backup region is always allowed during emergencies

Explanation

Correct Answer

A:

Design in-country redundant service and storage with compliant backup targets the underlying issue (the recovery design sends patient consultations to a region forbidden by local processing rules) rather than merely reporting symptoms. It also preserves the required outcome (clinical service must be recoverable inside approved national boundaries), which a target-state design must satisfy.

Incorrect Answers

B:

The alternative “Monitor regional replication, legal changes and failover access logs” measures results without defining the preventive design now required. In the reported observation, failover plan lists a default backup service on another continent. The option “Design in-country redundant service and storage with compliant backup” instead addresses the requested architecture selection.

C:

The alternative “Review legal location rules and failover data-plane traffic” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, failover plan lists a default backup service on another continent. The option “Design in-country redundant service and storage with compliant backup” instead addresses the requested architecture selection.

D:

Emergency operations do not automatically waive data residency laws. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that clinical service must be recoverable inside approved national boundaries.

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