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 8

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.

Question 71

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.

At Payments risk laboratory, the Google Cloud design for encryption key governance is affected because payment data uses default encryption but contract requires customer control over key rotation. A review found that key inventory shows provider-managed keys with no customer-managed lifecycle. The proposed response must account for the requirement that regulated card records require tracked access and planned key retirement. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?

  1. Clarify contract control requirements, key users and outage recovery implications
  2. Choose Cloud KMS CMEK where supported with separated key administrators and encryption users
  3. Migrate eligible resources to approved keys with tested grant/rollback
  4. Place plaintext encryption keys in shared project metadata

Explanation

Correct Answer

A:

Clarify contract control requirements, key users and outage recovery implications is the appropriate diagnostic because the observation—key inventory shows provider-managed keys with no customer-managed lifecycle—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (payment data uses default encryption but contract requires customer control over key rotation) before the design is approved.

Incorrect Answers

B:

The alternative “Choose Cloud KMS CMEK where supported with separated key administrators and encryption users” is target architecture selection; it does not establish why the observed path failed. In the reported observation, key inventory shows provider-managed keys with no customer-managed lifecycle. The option “Clarify contract control requirements, key users and outage recovery implications” instead addresses the requested root-cause evidence.

C:

The alternative “Migrate eligible resources to approved keys with tested grant/rollback” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, key inventory shows provider-managed keys with no customer-managed lifecycle. The option “Clarify contract control requirements, key users and outage recovery implications” instead addresses the requested root-cause evidence.

D:

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

Question 72

Case study: National agricultural extension office: drought forecasts

National agricultural extension office relies on drought forecasts to deliver its operational commitments. The current architectural problem is that satellite datasets will multiply as climate partners join and current retention assumes fixed volume. The team has recorded this evidence: forecast identifies increasing seasonal data and changing external contracts. Any proposed response must preserve the requirement that field staff still need affordable offline reports.

At National agricultural extension office, the Google Cloud design for drought forecasts is affected because satellite datasets will multiply as climate partners join and current retention assumes fixed volume. A review found that forecast identifies increasing seasonal data and changing external contracts. The proposed response must account for the requirement that field staff still need affordable offline reports. The cause has been established and a lasting architecture is being selected. Which design best meets the constraint?

  1. Adopt lifecycle-based object storage and decoupled batch product publishing
  2. Keep every raw satellite capture indefinitely in the highest-price storage class
  3. Monitor storage class transitions and data license expirations
  4. Model data retention, new partnership terms and user-access needs

Explanation

Correct Answer

A:

Adopt lifecycle-based object storage and decoupled batch product publishing targets the underlying issue (satellite datasets will multiply as climate partners join and current retention assumes fixed volume) rather than merely reporting symptoms. It also preserves the required outcome (field staff still need affordable offline reports), which a target-state design must satisfy.

Incorrect Answers

B:

A fixed hot-storage policy wastes funds and ignores changing licenses. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that field staff still need affordable offline reports.

C:

The alternative “Monitor storage class transitions and data license expirations” measures results without defining the preventive design now required. In the reported observation, forecast identifies increasing seasonal data and changing external contracts. The option “Adopt lifecycle-based object storage and decoupled batch product publishing” instead addresses the requested architecture selection.

D:

The alternative “Model data retention, new partnership terms and user-access needs” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, forecast identifies increasing seasonal data and changing external contracts. The option “Adopt lifecycle-based object storage and decoupled batch product publishing” instead addresses the requested architecture selection.

Question 73

At Multinational retailer, the Google Cloud design for checkout cost modernization is affected because a newly acquired brand will double country coverage and tax interfaces after migration. A review found that requirements show separate national tax authorities and holiday peak profiles. The proposed response must account for the requirement that checkout must preserve local residency and transparent tax audit. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?

  1. Identify regulatory and demand changes expected over the next two years
  2. Use modular regional tax integration boundaries with portable checkout contracts
  3. Encode every country's tax rules in a single hard-coded pricing function
  4. Onboard one new country with shadow invoices and local compliance signoff

Explanation

Correct Answer

A:

Identify regulatory and demand changes expected over the next two years is the appropriate diagnostic because the observation—requirements show separate national tax authorities and holiday peak profiles—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (a newly acquired brand will double country coverage and tax interfaces after migration) before the design is approved.

Incorrect Answers

B:

The alternative “Use modular regional tax integration boundaries with portable checkout contracts” is target architecture selection; it does not establish why the observed path failed. In the reported observation, requirements show separate national tax authorities and holiday peak profiles. The option “Identify regulatory and demand changes expected over the next two years” instead addresses the requested root-cause evidence.

C:

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

D:

The alternative “Onboard one new country with shadow invoices and local compliance signoff” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, requirements show separate national tax authorities and holiday peak profiles. The option “Identify regulatory and demand changes expected over the next two years” instead addresses the requested root-cause evidence.

Question 74

At Global pharmacy vendor, the private AI endpoint access workload has a documented risk: public model endpoints are reachable by unauthorized IPs while containing protected pricing prompts. The review found that network scan finds broad ingress on a model-serving load balancer. The architecture must also ensure that only corporate approved callers may submit sensitive requests. 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. Map service callers, endpoint type and private reachability needs
  2. Use private model-serving access and workload-bound IAM with constrained ingress
  3. Monitor ingress drift and attempted model endpoint abuse
  4. Try unauthorized public access and confirm private authenticated clients still work
  5. Hide endpoint names in source code but leave public access open
  6. Exclude the affected dependency from all future tests and incident metrics to simplify reporting

Explanation

Correct Answers

A:

Map service callers, endpoint type and private reachability needs is the appropriate diagnostic because the observation—network scan finds broad ingress on a model-serving load balancer—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (public model endpoints are reachable by unauthorized IPs while containing protected pricing prompts) before the design is approved. It supplies the pre-design diagnostic evidence requested.

C:

Monitor ingress drift and attempted model endpoint abuse reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (public model endpoints are reachable by unauthorized IPs while containing protected pricing prompts) rather than treating the first successful test as permanent assurance. It supplies the ongoing observation requested.

D:

Try unauthorized public access and confirm private authenticated clients still work is a direct acceptance test of the path implicated by network scan finds broad ingress on a model-serving load balancer. It checks that the original risk (public model endpoints are reachable by unauthorized IPs while containing protected pricing prompts) has actually been controlled and tests that permitted operations still meet the requirement that only corporate approved callers may submit sensitive requests. It supplies the separate post-change acceptance result requested.

Incorrect Answers

B:

Designing private AI endpoint access addresses the root cause, but this specific three-part question asks for evidence to diagnose, accept and continuously verify the response to public model endpoints are reachable by unauthorized IPs while containing protected pricing prompts, not another design proposal.

E:

Obscurity is not an endpoint authorization control. It cannot satisfy the required evidence stages.

F:

Omitting the relevant dependency from testing and monitoring would hide, not correct, recurrence of the failure. In particular, the observed issue was: network scan finds broad ingress on a model-serving load balancer.

Question 75

At Metropolitan power utility, the Google Cloud design for SCADA historian migration is affected because historian collectors send proprietary UDP and engineers propose direct internet exposure. A review found that packet survey shows embedded devices without TLS or authentication. The proposed response must account for the requirement that plant control networks must remain isolated from public ingress. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?

  1. Design a controlled telemetry bridge through an industrial DMZ to cloud storage
  2. Pilot one substation with read-only replicated data and authenticated broker
  3. Identify collectors, untrusted protocols, firewall dependencies and vendor constraints
  4. Give cloud VMs public routes into the SCADA control VLAN

Explanation

Correct Answer

C:

Identify collectors, untrusted protocols, firewall dependencies and vendor constraints is the appropriate diagnostic because the observation—packet survey shows embedded devices without TLS or authentication—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (historian collectors send proprietary UDP and engineers propose direct internet exposure) before the design is approved.

Incorrect Answers

A:

The alternative “Design a controlled telemetry bridge through an industrial DMZ to cloud storage” is target architecture selection; it does not establish why the observed path failed. In the reported observation, packet survey shows embedded devices without TLS or authentication. The option “Identify collectors, untrusted protocols, firewall dependencies and vendor constraints” instead addresses the requested root-cause evidence.

B:

The alternative “Pilot one substation with read-only replicated data and authenticated broker” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, packet survey shows embedded devices without TLS or authentication. The option “Identify collectors, untrusted protocols, firewall dependencies and vendor constraints” instead addresses the requested root-cause evidence.

D:

Direct internet access violates industrial segmentation. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that plant control networks must remain isolated from public ingress.

Question 76

At Telecom operator, the shared enterprise networking workload has a documented risk: every project creates ad hoc network policies and overlapping RFC1918 subnets. The review found that IPAM records show peering failures between billing and analytics projects. The architecture must also ensure that tenants need centralized network controls without project-wide admin grants. What follow-up metric or alert will identify emerging failures after the initial acceptance test?

  1. Peer all overlapping VPCs directly and rely on implicit transitivity
  2. Verify least-privilege subnet use and route reachability per service project
  3. Use Shared VPC with centralized host-network administration and delegated service projects
  4. Track subnet exhaustion, firewall drift and cross-project IAM grants

Explanation

Correct Answer

D:

Track subnet exhaustion, firewall drift and cross-project IAM grants reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (every project creates ad hoc network policies and overlapping RFC1918 subnets) rather than treating the first successful test as permanent assurance.

Incorrect Answers

A:

Overlapping ranges and nontransitive peering block reliable routing. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that tenants need centralized network controls without project-wide admin grants.

B:

The alternative “Verify least-privilege subnet use and route reachability per service project” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, IPAM records show peering failures between billing and analytics projects. The option “Track subnet exhaustion, firewall drift and cross-project IAM grants” instead addresses the requested ongoing operational assurance.

C:

The alternative “Use Shared VPC with centralized host-network administration and delegated service projects” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, IPAM records show peering failures between billing and analytics projects. The option “Track subnet exhaustion, firewall drift and cross-project IAM grants” instead addresses the requested ongoing operational assurance.

Question 77

Case study: National utility network: Terraform state protection

National utility network relies on Terraform state protection to deliver its operational commitments. The current architectural problem is that team stores Terraform state publicly in a source repository with embedded secrets. The team has recorded this evidence: security scan detects database credentials and sensitive IP inventory in state. Any proposed response must preserve the requirement that all state edits require audited locking and backup.

At National utility network, the Google Cloud design for Terraform state protection is affected because team stores Terraform state publicly in a source repository with embedded secrets. A review found that security scan detects database credentials and sensitive IP inventory in state. The proposed response must account for the requirement that all state edits require audited locking and backup. Which controlled implementation should be used to preserve operational continuity during the change?

  1. Place the same state JSON in a publicly readable object bucket
  2. Use protected remote state with access controls, locking and secret avoidance
  3. Monitor unauthorized state reads and failed locking events
  4. Migrate state to restricted storage and rotate any exposed secrets

Explanation

Correct Answer

D:

Migrate state to restricted storage and rotate any exposed secrets is a controlled means to introduce the approved architecture while meeting the requirement that all state edits require audited locking and backup. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.

Incorrect Answers

A:

Public state exposes sensitive configuration and cannot enforce controlled locking. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that all state edits require audited locking and backup.

B:

The alternative “Use protected remote state with access controls, locking and secret avoidance” describes the chosen design, but not how it is introduced safely. In the reported observation, security scan detects database credentials and sensitive IP inventory in state. The option “Migrate state to restricted storage and rotate any exposed secrets” instead addresses the requested controlled implementation.

C:

The alternative “Monitor unauthorized state reads and failed locking events” addresses later monitoring rather than the actual controlled deployment. In the reported observation, security scan detects database credentials and sensitive IP inventory in state. The option “Migrate state to restricted storage and rotate any exposed secrets” instead addresses the requested controlled implementation.

Question 78

At Retail airline reservations, the Google Cloud design for load-test realism is affected because capacity tests generate simple GET requests but real transactions require multiple write steps. A review found that peak production incident shows locks on seat inventory despite low GET latency. The proposed response must account for the requirement that holiday purchase flow must sustain transactional volume without overselling. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?

  1. Introduce production-like synthetic traffic safely before peak season
  2. Model full booking transactions, contention and peak user behavior
  3. Design capacity and admission control around realistic end-to-end flows
  4. Declare peak readiness because static homepage GET requests are fast

Explanation

Correct Answer

B:

Model full booking transactions, contention and peak user behavior is the appropriate diagnostic because the observation—peak production incident shows locks on seat inventory despite low GET latency—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (capacity tests generate simple GET requests but real transactions require multiple write steps) before the design is approved.

Incorrect Answers

A:

The alternative “Introduce production-like synthetic traffic safely before peak season” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, peak production incident shows locks on seat inventory despite low GET latency. The option “Model full booking transactions, contention and peak user behavior” instead addresses the requested root-cause evidence.

C:

The alternative “Design capacity and admission control around realistic end-to-end flows” is target architecture selection; it does not establish why the observed path failed. In the reported observation, peak production incident shows locks on seat inventory despite low GET latency. The option “Model full booking transactions, contention and peak user behavior” instead addresses the requested root-cause evidence.

D:

Read-only performance does not establish transactional capacity. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that holiday purchase flow must sustain transactional volume without overselling.

Question 79

Consider International renewable energy fund and its cost governance of abandoned environments workload. The issue is that unused development clusters persist after quarter-end project closures; the current observation is that billing export shows idle infrastructure without current cost owner. The team must ensure that audit requirements retain records but not unused compute. Which acceptance test should demonstrate both protection against the failure and continued authorized service?

  1. Map workloads, cleanup ownership and retention dependencies
  2. Confirm retained evidence is accessible while stopped compute charges cease
  3. Run owner-approved cleanup on tagged nonproduction environments
  4. Delete every project including protected regulatory evidence without review

Explanation

Correct Answer

B:

Confirm retained evidence is accessible while stopped compute charges cease is a direct acceptance test of the path implicated by billing export shows idle infrastructure without current cost owner. It checks that the original risk (unused development clusters persist after quarter-end project closures) has actually been controlled and tests that permitted operations still meet the requirement that audit requirements retain records but not unused compute.

Incorrect Answers

A:

The alternative “Map workloads, cleanup ownership and retention dependencies” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, billing export shows idle infrastructure without current cost owner. The option “Confirm retained evidence is accessible while stopped compute charges cease” instead addresses the requested acceptance verification.

C:

The alternative “Run owner-approved cleanup on tagged nonproduction environments” documents change execution but not its operational acceptance result. In the reported observation, billing export shows idle infrastructure without current cost owner. The option “Confirm retained evidence is accessible while stopped compute charges cease” instead addresses the requested acceptance verification.

D:

Unreviewed cleanup can destroy necessary retained records. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that audit requirements retain records but not unused compute.

Question 80

Legal case management SaaS plans to update multi-tenant object security. Investigators found that penetration test exchanges a case ID and retrieves another tenant's document, consistent with the reported problem that valid user tokens can access case files belonging to other law firms. The response must satisfy the requirement that each firm requires strict object-level isolation. Which target-state design is best justified by the evidence and required business outcome?

  1. Trace subject, tenant, object and data-layer authorization decisions
  2. Rely only on login authentication without checking case object ownership
  3. Apply tenant-bound object authorization enforced on every API and data query
  4. Monitor denied cross-tenant access and new API routes lacking ownership checks

Explanation

Correct Answer

C:

Apply tenant-bound object authorization enforced on every API and data query targets the underlying issue (valid user tokens can access case files belonging to other law firms) rather than merely reporting symptoms. It also preserves the required outcome (each firm requires strict object-level isolation), which a target-state design must satisfy.

Incorrect Answers

A:

The alternative “Trace subject, tenant, object and data-layer authorization decisions” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, penetration test exchanges a case ID and retrieves another tenant's document. The option “Apply tenant-bound object authorization enforced on every API and data query” instead addresses the requested architecture selection.

B:

Authentication cannot replace per-object authorization. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that each firm requires strict object-level isolation.

D:

The alternative “Monitor denied cross-tenant access and new API routes lacking ownership checks” measures results without defining the preventive design now required. In the reported observation, penetration test exchanges a case ID and retrieves another tenant's document. The option “Apply tenant-bound object authorization enforced on every API and data query” instead addresses the requested architecture selection.

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