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 93

Question 920

Case study: Cross-border payment provider: regulated retention policy

Cross-border payment provider relies on regulated retention policy to deliver its operational commitments. The current architectural problem is that cloud backups are replicated globally without legal review of data-residency restrictions. The team has recorded this evidence: compliance assessment finds a bucket's secondary location is outside allowed jurisdiction. Any proposed response must preserve the requirement that cardholder data must remain only in approved processing geography.

Consider Cross-border payment provider and its regulated retention policy workload. The issue is that cloud backups are replicated globally without legal review of data-residency restrictions; the current observation is that compliance assessment finds a bucket's secondary location is outside allowed jurisdiction. The team must ensure that cardholder data must remain only in approved processing geography. The target architecture is approved; execution without disruption is the remaining decision. Which rollout action is best?

  1. Migrate or recreate noncompliant replicas with regulatory signoff
  2. Review location-policy changes, recovery tests and retention deviations
  3. Use region-restricted storage, key policies and authenticated retention records
  4. Store the most sensitive copies in any multi-region regardless of its constituent locations

Explanation

Correct Answer

A:

Migrate or recreate noncompliant replicas with regulatory signoff is a controlled means to introduce the approved architecture while meeting the requirement that cardholder data must remain only in approved processing geography. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.

Incorrect Answers

B:

The alternative “Review location-policy changes, recovery tests and retention deviations” addresses later monitoring rather than the actual controlled deployment. In the reported observation, compliance assessment finds a bucket's secondary location is outside allowed jurisdiction. The option “Migrate or recreate noncompliant replicas with regulatory signoff” instead addresses the requested controlled implementation.

C:

The alternative “Use region-restricted storage, key policies and authenticated retention records” describes the chosen design, but not how it is introduced safely. In the reported observation, compliance assessment finds a bucket's secondary location is outside allowed jurisdiction. The option “Migrate or recreate noncompliant replicas with regulatory signoff” instead addresses the requested controlled implementation.

D:

A global location can violate specific geographic transfer restrictions. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that cardholder data must remain only in approved processing geography.

Question 921

The disaster recovery runbook environment at National rail passenger service faces this issue: backup jobs report success but operational teams have never restored ticket data. Supporting evidence shows that DR rehearsal cannot identify who owns recovery steps. The architect must preserve the requirement that tickets must be sold again within 30 minutes after a primary failure. Before approving a solution, which analysis most directly clarifies the underlying dependency or control gap?

  1. Inventory recovery dependencies, owners, RTO/RPO and validated backups
  2. Schedule isolated recovery drills and sign off runbook changes
  3. Increase the backup frequency and skip every restoration exercise
  4. Build owner-assigned DR procedures with restoration priorities and decision gates

Explanation

Correct Answer

A:

Inventory recovery dependencies, owners, RTO/RPO and validated backups is the appropriate diagnostic because the observation—DR rehearsal cannot identify who owns recovery steps—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (backup jobs report success but operational teams have never restored ticket data) before the design is approved.

Incorrect Answers

B:

The alternative “Schedule isolated recovery drills and sign off runbook changes” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, DR rehearsal cannot identify who owns recovery steps. The option “Inventory recovery dependencies, owners, RTO/RPO and validated backups” instead addresses the requested root-cause evidence.

C:

Backup completion does not prove recoverability or an executable procedure. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that tickets must be sold again within 30 minutes after a primary failure.

D:

The alternative “Build owner-assigned DR procedures with restoration priorities and decision gates” is target architecture selection; it does not establish why the observed path failed. In the reported observation, DR rehearsal cannot identify who owns recovery steps. The option “Inventory recovery dependencies, owners, RTO/RPO and validated backups” instead addresses the requested root-cause evidence.

Question 922

At Financial audit services group, the Google Cloud design for cloud organization inheritance is affected because security administrators grant broad roles directly to each production project. A review found that audit reveals inconsistent permissions across finance subsidiaries. The proposed response must account for the requirement that a central security team must enforce boundaries while subsidiaries run their own workloads. A deployment ticket has been closed. What direct evidence would justify solution signoff?

  1. Confirm a new project inherits restrictions and has only intended group access
  2. Inspect inherited IAM, folders, project ownership and org policies
  3. Grant Editor to every subsidiary developer on every production project
  4. Migrate grants through tested IAM groups and an exception approval window

Explanation

Correct Answer

A:

Confirm a new project inherits restrictions and has only intended group access is a direct acceptance test of the path implicated by audit reveals inconsistent permissions across finance subsidiaries. It checks that the original risk (security administrators grant broad roles directly to each production project) has actually been controlled and tests that permitted operations still meet the requirement that a central security team must enforce boundaries while subsidiaries run their own workloads.

Incorrect Answers

B:

The alternative “Inspect inherited IAM, folders, project ownership and org policies” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, audit reveals inconsistent permissions across finance subsidiaries. The option “Confirm a new project inherits restrictions and has only intended group access” instead addresses the requested acceptance verification.

C:

Broad organization-wide editing violates separation and least privilege. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that a central security team must enforce boundaries while subsidiaries run their own workloads.

D:

The alternative “Migrate grants through tested IAM groups and an exception approval window” documents change execution but not its operational acceptance result. In the reported observation, audit reveals inconsistent permissions across finance subsidiaries. The option “Confirm a new project inherits restrictions and has only intended group access” instead addresses the requested acceptance verification.

Question 923

National digital identification office plans to update external identity service onboarding. Investigators found that test shows an agency credential can call unrelated record endpoints, consistent with the reported problem that a public API rollout lacks per-agency token audience enforcement. The response must satisfy the requirement that agency access must be least privilege and auditable. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?

  1. Allow any signed token from any agency to read all records
  2. Use audience-scoped tokens and appropriate API authorization checks
  3. Profile identity issuers, service boundaries and API authorization needs
  4. Onboard agencies incrementally with policy tests and request logs

Explanation

Correct Answer

C:

Profile identity issuers, service boundaries and API authorization needs is the appropriate diagnostic because the observation—test shows an agency credential can call unrelated record endpoints—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (a public API rollout lacks per-agency token audience enforcement) before the design is approved.

Incorrect Answers

A:

Signature validity does not grant access to unrelated applications. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that agency access must be least privilege and auditable.

B:

The alternative “Use audience-scoped tokens and appropriate API authorization checks” is target architecture selection; it does not establish why the observed path failed. In the reported observation, test shows an agency credential can call unrelated record endpoints. The option “Profile identity issuers, service boundaries and API authorization needs” instead addresses the requested root-cause evidence.

D:

The alternative “Onboard agencies incrementally with policy tests and request logs” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, test shows an agency credential can call unrelated record endpoints. The option “Profile identity issuers, service boundaries and API authorization needs” instead addresses the requested root-cause evidence.

Question 924

Case study: National pharmacy network: central NAT egress

National pharmacy network relies on central NAT egress to deliver its operational commitments. The current architectural problem is that a vendor allowlist changes every time cloud VMs autoscale with ephemeral external IPs. The team has recorded this evidence: packet trace shows outbound API requests use different VM public addresses. Any proposed response must preserve the requirement that drug inventory partner permits only named stable source addresses.

National pharmacy network plans to update central NAT egress. Investigators found that packet trace shows outbound API requests use different VM public addresses, consistent with the reported problem that a vendor allowlist changes every time cloud VMs autoscale with ephemeral external IPs. The response must satisfy the requirement that drug inventory partner permits only named stable source addresses. The approved change has been applied. Which validation provides the clearest evidence the original problem is fixed?

  1. Force instance recreation and confirm the partner sees the approved egress IP
  2. Identify egress flows and where dynamic external addressing is introduced
  3. Migrate VMs to private instances and update partner allowlists before cutover
  4. Assign a new public IP to every ephemeral VM and email the vendor daily

Explanation

Correct Answer

A:

Force instance recreation and confirm the partner sees the approved egress IP is a direct acceptance test of the path implicated by packet trace shows outbound API requests use different VM public addresses. It checks that the original risk (a vendor allowlist changes every time cloud VMs autoscale with ephemeral external IPs) has actually been controlled and tests that permitted operations still meet the requirement that drug inventory partner permits only named stable source addresses.

Incorrect Answers

B:

The alternative “Identify egress flows and where dynamic external addressing is introduced” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, packet trace shows outbound API requests use different VM public addresses. The option “Force instance recreation and confirm the partner sees the approved egress IP” instead addresses the requested acceptance verification.

C:

The alternative “Migrate VMs to private instances and update partner allowlists before cutover” documents change execution but not its operational acceptance result. In the reported observation, packet trace shows outbound API requests use different VM public addresses. The option “Force instance recreation and confirm the partner sees the approved egress IP” instead addresses the requested acceptance verification.

D:

Changing per-instance IPs cannot maintain a stable partner allowlist. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that drug inventory partner permits only named stable source addresses.

Question 925

The runbook resilience environment at Green energy trading service faces this issue: a repeated Cloud SQL failover is handled differently by each on-call engineer. Supporting evidence shows that incident notes show conflicting restart commands and missing escalation steps. The architect must preserve the requirement that financial settlement recovery must be repeatable and auditable. What test must pass before the business accepts the remediated architecture?

  1. Rehearse primary failover and confirm consistent audited actions
  2. Reconstruct failures, decision points and runbook gaps
  3. Allow responders to improvise privileged database deletion during every outage
  4. Train the response team using a shadow exercise and signed change review

Explanation

Correct Answer

A:

Rehearse primary failover and confirm consistent audited actions is a direct acceptance test of the path implicated by incident notes show conflicting restart commands and missing escalation steps. It checks that the original risk (a repeated Cloud SQL failover is handled differently by each on-call engineer) has actually been controlled and tests that permitted operations still meet the requirement that financial settlement recovery must be repeatable and auditable.

Incorrect Answers

B:

The alternative “Reconstruct failures, decision points and runbook gaps” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, incident notes show conflicting restart commands and missing escalation steps. The option “Rehearse primary failover and confirm consistent audited actions” instead addresses the requested acceptance verification.

C:

Uncontrolled destructive actions increase recovery risk. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that financial settlement recovery must be repeatable and auditable.

D:

The alternative “Train the response team using a shadow exercise and signed change review” documents change execution but not its operational acceptance result. In the reported observation, incident notes show conflicting restart commands and missing escalation steps. The option “Rehearse primary failover and confirm consistent audited actions” instead addresses the requested acceptance verification.

Question 926

At National energy research agency, the Google Cloud design for customer-held encryption custody is affected because key users and key administrators are the same operational group. A review found that IAM audit finds anyone who deploys workloads can disable and destroy keys. The proposed response must account for the requirement that regulatory continuity requires separate key destruction approval. The cause has been established and a lasting architecture is being selected. Which design best meets the constraint?

  1. Alert on destructive key operations and emergency grants
  2. Split Cloud KMS key-admin and cryptographic-use roles with protected approval flow
  3. Analyze who can encrypt, decrypt, rotate, disable and schedule destruction
  4. Grant cryptoKeyAdmin to every application service account

Explanation

Correct Answer

B:

Split Cloud KMS key-admin and cryptographic-use roles with protected approval flow targets the underlying issue (key users and key administrators are the same operational group) rather than merely reporting symptoms. It also preserves the required outcome (regulatory continuity requires separate key destruction approval), which a target-state design must satisfy.

Incorrect Answers

A:

The alternative “Alert on destructive key operations and emergency grants” measures results without defining the preventive design now required. In the reported observation, IAM audit finds anyone who deploys workloads can disable and destroy keys. The option “Split Cloud KMS key-admin and cryptographic-use roles with protected approval flow” instead addresses the requested architecture selection.

C:

The alternative “Analyze who can encrypt, decrypt, rotate, disable and schedule destruction” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, IAM audit finds anyone who deploys workloads can disable and destroy keys. The option “Split Cloud KMS key-admin and cryptographic-use roles with protected approval flow” instead addresses the requested architecture selection.

D:

Applications do not need key lifecycle destruction authority. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that regulatory continuity requires separate key destruction approval.

Question 927

At Regional tax administration, the separation of duties workload has a documented risk: one engineer both edits production code and approves its own security policy exceptions. The review found that access review shows the same principal has release and audit-admin permissions. The architecture must also ensure that regulated changes require an independent approval trail. Which post-change test most reliably distinguishes a functioning control from a merely successful installation?

  1. Give all developers Owner and rely on an informal promise to avoid self-approval
  2. Map change roles, privileged groups and audit responsibilities
  3. Attempt self-approval and confirm policy blocks it while approved release succeeds
  4. Transition privileges into independent groups with emergency break-glass procedures

Explanation

Correct Answer

C:

Attempt self-approval and confirm policy blocks it while approved release succeeds is a direct acceptance test of the path implicated by access review shows the same principal has release and audit-admin permissions. It checks that the original risk (one engineer both edits production code and approves its own security policy exceptions) has actually been controlled and tests that permitted operations still meet the requirement that regulated changes require an independent approval trail.

Incorrect Answers

A:

An informal promise cannot enforce role separation. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that regulated changes require an independent approval trail.

B:

The alternative “Map change roles, privileged groups and audit responsibilities” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, access review shows the same principal has release and audit-admin permissions. The option “Attempt self-approval and confirm policy blocks it while approved release succeeds” instead addresses the requested acceptance verification.

D:

The alternative “Transition privileges into independent groups with emergency break-glass procedures” documents change execution but not its operational acceptance result. In the reported observation, access review shows the same principal has release and audit-admin permissions. The option “Attempt self-approval and confirm policy blocks it while approved release succeeds” instead addresses the requested acceptance verification.

Question 928

Case study: Public school admissions portal: release version safety

Public school admissions portal relies on release version safety to deliver its operational commitments. The current architectural problem is that frontend rollout references a backend schema that is not yet deployed. The team has recorded this evidence: incident shows new clients send unsupported enrollment fields. Any proposed response must preserve the requirement that admission forms cannot break during deadline week.

At Public school admissions portal, the Google Cloud design for release version safety is affected because frontend rollout references a backend schema that is not yet deployed. A review found that incident shows new clients send unsupported enrollment fields. The proposed response must account for the requirement that admission forms cannot break during deadline week. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?

  1. Map frontend/backend compatibility and schema transition dependencies
  2. Deploy breaking frontend and database schema simultaneously without canary
  3. Roll out schema first, then canary clients with traffic rollback
  4. Track 4xx schema errors and version skew
  5. Design backward-compatible API contracts and staged deployments

Explanation

Correct Answers

C:

Roll out schema first, then canary clients with traffic rollback is a controlled means to introduce the approved architecture while meeting the requirement that admission forms cannot break during deadline week. 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:

Design backward-compatible API contracts and staged deployments targets the underlying issue (frontend rollout references a backend schema that is not yet deployed) rather than merely reporting symptoms. It also preserves the required outcome (admission forms cannot break during deadline week), 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 (frontend rollout references a backend schema that is not yet deployed), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.

B:

A coupled big-bang change creates untested integration failures. The shortcut does not supply the requested design and safe rollout for release version safety, where incident shows new clients send unsupported enrollment fields.

D:

Monitoring release version safety for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: frontend rollout references a backend schema that is not yet deployed.

Question 929

Case study: Medical device logistics vendor: Windows application portfolio

Medical device logistics vendor relies on Windows application portfolio to deliver its operational commitments. The current architectural problem is that a vendor application requires proprietary Windows integration and cannot be modified until 2028. The team has recorded this evidence: application inventory confirms hard-coded Windows service dependency and vendor support conditions. Any proposed response must preserve the requirement that device dispatch must maintain support entitlement and tested restoration.

Medical device logistics vendor plans to update Windows application portfolio. Investigators found that application inventory confirms hard-coded Windows service dependency and vendor support conditions, consistent with the reported problem that a vendor application requires proprietary Windows integration and cannot be modified until 2028. The response must satisfy the requirement that device dispatch must maintain support entitlement and tested restoration. The team needs an operations signal rather than another design or one-time test. What should it track?

  1. Watch Windows patch windows, vendor support changes and hosting costs
  2. Convert the unsupported proprietary service directly to Cloud Run with no rewrite
  3. Choose supported Compute Engine Windows hosting as an interim migration disposition
  4. Run vendor certification tests and warehouse dispatch transactions on restored instances

Explanation

Correct Answer

A:

Watch Windows patch windows, vendor support changes and hosting costs reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a vendor application requires proprietary Windows integration and cannot be modified until 2028) rather than treating the first successful test as permanent assurance.

Incorrect Answers

B:

A Windows-service binary does not become a stateless Linux container automatically. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that device dispatch must maintain support entitlement and tested restoration.

C:

The alternative “Choose supported Compute Engine Windows hosting as an interim migration disposition” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, application inventory confirms hard-coded Windows service dependency and vendor support conditions. The option “Watch Windows patch windows, vendor support changes and hosting costs” instead addresses the requested ongoing operational assurance.

D:

The alternative “Run vendor certification tests and warehouse dispatch transactions on restored instances” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, application inventory confirms hard-coded Windows service dependency and vendor support conditions. The option “Watch Windows patch windows, vendor support changes and hosting costs” instead addresses the requested ongoing operational assurance.

Question 930

Case study: Regional sports venue: deploy-time traffic splitting

Regional sports venue relies on deploy-time traffic splitting to deliver its operational commitments. The current architectural problem is that teams replace a full production service revision in one step before stadium events. The team has recorded this evidence: last release caused 15 minutes of checkout errors during a full swap. Any proposed response must preserve the requirement that ticket scanning must stay available throughout peak admission.

The deploy-time traffic splitting environment at Regional sports venue faces this issue: teams replace a full production service revision in one step before stadium events. Supporting evidence shows that last release caused 15 minutes of checkout errors during a full swap. The architect must preserve the requirement that ticket scanning must stay available throughout peak admission. What test must pass before the business accepts the remediated architecture?

  1. Introduce weighted traffic shifting and automatic rollback thresholds
  2. Inspect release mechanics, rollback needs and request session behavior
  3. Send realistic admission traffic through both versions and verify stability
  4. Use a full instantaneous replace for every release and observe failures afterward

Explanation

Correct Answer

C:

Send realistic admission traffic through both versions and verify stability is a direct acceptance test of the path implicated by last release caused 15 minutes of checkout errors during a full swap. It checks that the original risk (teams replace a full production service revision in one step before stadium events) has actually been controlled and tests that permitted operations still meet the requirement that ticket scanning must stay available throughout peak admission.

Incorrect Answers

A:

The alternative “Introduce weighted traffic shifting and automatic rollback thresholds” documents change execution but not its operational acceptance result. In the reported observation, last release caused 15 minutes of checkout errors during a full swap. The option “Send realistic admission traffic through both versions and verify stability” instead addresses the requested acceptance verification.

B:

The alternative “Inspect release mechanics, rollback needs and request session behavior” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, last release caused 15 minutes of checkout errors during a full swap. The option “Send realistic admission traffic through both versions and verify stability” instead addresses the requested acceptance verification.

D:

A big-bang change concentrates customer impact. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that ticket scanning must stay available throughout peak admission.

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