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 24

Question 230

The Secret Manager credential lifecycle environment at Public safety communications service faces this issue: a service passes a database password through the deployment YAML. Supporting evidence shows that pipeline logs contain plaintext passwords used in production. The architect must preserve the requirement that credentials must rotate without emergency downtime. What test must pass before the business accepts the remediated architecture?

  1. Deploy consumers that read approved versions before retiring the old secret
  2. Rotate the database secret and verify old versions are rejected after cutover
  3. Locate credential copies, readers and rotation/dependency relationships
  4. Put the same plaintext password into a Kubernetes ConfigMap

Explanation

Correct Answer

B:

Rotate the database secret and verify old versions are rejected after cutover is a direct acceptance test of the path implicated by pipeline logs contain plaintext passwords used in production. It checks that the original risk (a service passes a database password through the deployment YAML) has actually been controlled and tests that permitted operations still meet the requirement that credentials must rotate without emergency downtime.

Incorrect Answers

A:

The alternative “Deploy consumers that read approved versions before retiring the old secret” documents change execution but not its operational acceptance result. In the reported observation, pipeline logs contain plaintext passwords used in production. The option “Rotate the database secret and verify old versions are rejected after cutover” instead addresses the requested acceptance verification.

C:

The alternative “Locate credential copies, readers and rotation/dependency relationships” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, pipeline logs contain plaintext passwords used in production. The option “Rotate the database secret and verify old versions are rejected after cutover” instead addresses the requested acceptance verification.

D:

A ConfigMap alone does not secure the original secret. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that credentials must rotate without emergency downtime.

Question 231

At Regional tax administration, the Google Cloud design for separation of duties is affected because one engineer both edits production code and approves its own security policy exceptions. A review found that access review shows the same principal has release and audit-admin permissions. The proposed response must account for the requirement that regulated changes require an independent approval trail. Which controlled implementation should be used to preserve operational continuity during the change?

  1. Transition privileges into independent groups with emergency break-glass procedures
  2. Separate release, approval and audit roles with enforceable IAM constraints
  3. Monitor break-glass sessions and privilege role conflicts
  4. Give all developers Owner and rely on an informal promise to avoid self-approval

Explanation

Correct Answer

A:

Transition privileges into independent groups with emergency break-glass procedures is a controlled means to introduce the approved architecture while meeting the requirement that regulated changes require an independent approval trail. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.

Incorrect Answers

B:

The alternative “Separate release, approval and audit roles with enforceable IAM constraints” describes the chosen design, but not how it is introduced safely. In the reported observation, access review shows the same principal has release and audit-admin permissions. The option “Transition privileges into independent groups with emergency break-glass procedures” instead addresses the requested controlled implementation.

C:

The alternative “Monitor break-glass sessions and privilege role conflicts” addresses later monitoring rather than the actual controlled deployment. In the reported observation, access review shows the same principal has release and audit-admin permissions. The option “Transition privileges into independent groups with emergency break-glass procedures” instead addresses the requested controlled implementation.

D:

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

Question 232

Case study: International automotive retailer: API gateway migration

International automotive retailer relies on API gateway migration to deliver its operational commitments. The current architectural problem is that third-party dealerships expect old JSON fields while a new service removes one required property. The team has recorded this evidence: contract tests show older clients fail when the new revision is published. Any proposed response must preserve the requirement that dealer ordering cannot require simultaneous client upgrades.

Consider International automotive retailer and its API gateway migration workload. The issue is that third-party dealerships expect old JSON fields while a new service removes one required property; the current observation is that contract tests show older clients fail when the new revision is published. The team must ensure that dealer ordering cannot require simultaneous client upgrades. 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. Design backward-compatible API versioning and deprecation policy
  2. Track remaining old-client traffic and breaking-response failures
  3. Accept the deployment ticket as proof that the control has no remaining security or availability risk
  4. Run old-client and new-client tests through the gateway
  5. Identify required fields, version agreements and client deployment windows
  6. Remove legacy fields immediately because the provider source code is updated

Explanation

Correct Answers

B:

Track remaining old-client traffic and breaking-response failures reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (third-party dealerships expect old JSON fields while a new service removes one required property) rather than treating the first successful test as permanent assurance. It supplies the ongoing observation requested.

D:

Run old-client and new-client tests through the gateway is a direct acceptance test of the path implicated by contract tests show older clients fail when the new revision is published. It checks that the original risk (third-party dealerships expect old JSON fields while a new service removes one required property) has actually been controlled and tests that permitted operations still meet the requirement that dealer ordering cannot require simultaneous client upgrades. It supplies the separate post-change acceptance result requested.

E:

Identify required fields, version agreements and client deployment windows is the appropriate diagnostic because the observation—contract tests show older clients fail when the new revision is published—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (third-party dealerships expect old JSON fields while a new service removes one required property) before the design is approved. It supplies the pre-design diagnostic evidence requested.

Incorrect Answers

A:

Designing API gateway migration addresses the root cause, but this specific three-part question asks for evidence to diagnose, accept and continuously verify the response to third-party dealerships expect old JSON fields while a new service removes one required property, not another design proposal.

C:

A change-record state does not measure the behavior reported by the original evidence, and cannot prove protection or availability. In particular, the observed issue was: contract tests show older clients fail when the new revision is published.

F:

Client contracts are not automatically updated with server code. It cannot satisfy the required evidence stages.

Question 233

At Medical lab network, the Google Cloud design for shared filesystem for containers is affected because lab containers need concurrent POSIX file writes but the team selected object-storage semantics. A review found that test suite fails on file-lock operations and atomic renames. The proposed response must account for the requirement that laboratory collaboration requires managed NFS semantics in one region. A deployment ticket has been closed. What direct evidence would justify solution signoff?

  1. Profile POSIX operations, concurrency, required throughput and backup needs
  2. Mount managed file shares using approved network and workload IAM arrangements
  3. Run concurrent file-lock and rename tests under a pod restart
  4. Treat Cloud Storage object writes as POSIX byte-range locking

Explanation

Correct Answer

C:

Run concurrent file-lock and rename tests under a pod restart is a direct acceptance test of the path implicated by test suite fails on file-lock operations and atomic renames. It checks that the original risk (lab containers need concurrent POSIX file writes but the team selected object-storage semantics) has actually been controlled and tests that permitted operations still meet the requirement that laboratory collaboration requires managed NFS semantics in one region.

Incorrect Answers

A:

The alternative “Profile POSIX operations, concurrency, required throughput and backup needs” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, test suite fails on file-lock operations and atomic renames. The option “Run concurrent file-lock and rename tests under a pod restart” instead addresses the requested acceptance verification.

B:

The alternative “Mount managed file shares using approved network and workload IAM arrangements” documents change execution but not its operational acceptance result. In the reported observation, test suite fails on file-lock operations and atomic renames. The option “Run concurrent file-lock and rename tests under a pod restart” instead addresses the requested acceptance verification.

D:

Object storage does not provide identical filesystem locking semantics. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that laboratory collaboration requires managed NFS semantics in one region.

Question 234

Case study: Regional museum: global artifact web gallery

Regional museum relies on global artifact web gallery to deliver its operational commitments. The current architectural problem is that public image delivery overloads the origin service on exhibit announcement days. The team has recorded this evidence: traces show the same static media repeatedly retrieved by remote browsers. Any proposed response must preserve the requirement that private curator uploads must remain restricted while published assets are cacheable.

Consider Regional museum and its global artifact web gallery workload. The issue is that public image delivery overloads the origin service on exhibit announcement days; the current observation is that traces show the same static media repeatedly retrieved by remote browsers. The team must ensure that private curator uploads must remain restricted while published assets are cacheable. The team has completed discovery. Which preventive or corrective architecture is most appropriate?

  1. Serve public assets through Cloud CDN while keeping private edit APIs uncached
  2. Monitor cache invalidations, origin egress and signed-access errors
  3. Measure static/dynamic request mix, cache control and publication boundaries
  4. Cache authenticated curator endpoints for every visitor under a shared key

Explanation

Correct Answer

A:

Serve public assets through Cloud CDN while keeping private edit APIs uncached targets the underlying issue (public image delivery overloads the origin service on exhibit announcement days) rather than merely reporting symptoms. It also preserves the required outcome (private curator uploads must remain restricted while published assets are cacheable), which a target-state design must satisfy.

Incorrect Answers

B:

The alternative “Monitor cache invalidations, origin egress and signed-access errors” measures results without defining the preventive design now required. In the reported observation, traces show the same static media repeatedly retrieved by remote browsers. The option “Serve public assets through Cloud CDN while keeping private edit APIs uncached” instead addresses the requested architecture selection.

C:

The alternative “Measure static/dynamic request mix, cache control and publication boundaries” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, traces show the same static media repeatedly retrieved by remote browsers. The option “Serve public assets through Cloud CDN while keeping private edit APIs uncached” instead addresses the requested architecture selection.

D:

Shared caching of private responses can leak unreleased content. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that private curator uploads must remain restricted while published assets are cacheable.

Question 235

At Manufacturer predictive maintenance team, the Google Cloud design for Agent Platform ML pipelines is affected because each retraining run uses a different preprocessing notebook with no lineage. A review found that model results diverge even when training data IDs match. The proposed response must account for the requirement that factory anomaly models need reproducible releases and operator approval. A deployment ticket has been closed. What direct evidence would justify solution signoff?

  1. Train directly on mutable shared notebooks without tracking artifact versions
  2. Re-run the same dataset and verify matching approved artifact lineage
  3. Migrate manual retraining into an approved Agent Platform pipeline in shadow mode
  4. Compare data hashes, preprocessing versions, evaluation steps and feature schema

Explanation

Correct Answer

B:

Re-run the same dataset and verify matching approved artifact lineage is a direct acceptance test of the path implicated by model results diverge even when training data IDs match. It checks that the original risk (each retraining run uses a different preprocessing notebook with no lineage) has actually been controlled and tests that permitted operations still meet the requirement that factory anomaly models need reproducible releases and operator approval.

Incorrect Answers

A:

An unversioned notebook cannot support reproducible evaluation. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that factory anomaly models need reproducible releases and operator approval.

C:

The alternative “Migrate manual retraining into an approved Agent Platform pipeline in shadow mode” documents change execution but not its operational acceptance result. In the reported observation, model results diverge even when training data IDs match. The option “Re-run the same dataset and verify matching approved artifact lineage” instead addresses the requested acceptance verification.

D:

The alternative “Compare data hashes, preprocessing versions, evaluation steps and feature schema” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, model results diverge even when training data IDs match. The option “Re-run the same dataset and verify matching approved artifact lineage” instead addresses the requested acceptance verification.

Question 236

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 Google Cloud design for production support handoff is affected because platform team deploys new observability agents without defining who handles alerts. A review found that incident rehearsal finds metrics present but no pager owner. The proposed response must account for the requirement that grid control support must remain staffed around the clock. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?

  1. Define operable SLOs, escalation routing and safe remediation authority
  2. Watch unowned pages, stale runbooks and response latency
  3. Enable thousands of pages with no routing or training
  4. Trigger a critical service alert and confirm correct acknowledgement and escalation

Explanation

Correct Answer

B:

Watch unowned pages, stale runbooks and response latency reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (platform team deploys new observability agents without defining who handles alerts) rather than treating the first successful test as permanent assurance.

Incorrect Answers

A:

The alternative “Define operable SLOs, escalation routing and safe remediation authority” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, incident rehearsal finds metrics present but no pager owner. The option “Watch unowned pages, stale runbooks and response latency” instead addresses the requested ongoing operational assurance.

C:

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

D:

The alternative “Trigger a critical service alert and confirm correct acknowledgement and escalation” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, incident rehearsal finds metrics present but no pager owner. The option “Watch unowned pages, stale runbooks and response latency” instead addresses the requested ongoing operational assurance.

Question 237

At Neighborhood banking cooperative, the Google Cloud design for loan-origination approval service is affected because the planned monolith migration promises lower costs but omits the regulatory audit and branch-outage requirements. A review found that business interviews reveal a four-hour branch outage limit and an immutable decision-history obligation. The proposed response must account for the requirement that branches need approvals even when a regional WAN circuit fails. A deployment ticket has been closed. What direct evidence would justify solution signoff?

  1. Migrate one branch at a time with reconciled event replay and rollback
  2. Map branch dependencies, decision-record retention and acceptable outage duration with risk owners
  3. Exercise a WAN partition and reconcile approval events against immutable records after recovery
  4. Choose the cheapest single-zone VM and discard decision events once the API responds

Explanation

Correct Answer

C:

Exercise a WAN partition and reconcile approval events against immutable records after recovery is a direct acceptance test of the path implicated by business interviews reveal a four-hour branch outage limit and an immutable decision-history obligation. It checks that the original risk (the planned monolith migration promises lower costs but omits the regulatory audit and branch-outage requirements) has actually been controlled and tests that permitted operations still meet the requirement that branches need approvals even when a regional WAN circuit fails.

Incorrect Answers

A:

The alternative “Migrate one branch at a time with reconciled event replay and rollback” documents change execution but not its operational acceptance result. In the reported observation, business interviews reveal a four-hour branch outage limit and an immutable decision-history obligation. The option “Exercise a WAN partition and reconcile approval events against immutable records after recovery” instead addresses the requested acceptance verification.

B:

The alternative “Map branch dependencies, decision-record retention and acceptable outage duration with risk owners” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, business interviews reveal a four-hour branch outage limit and an immutable decision-history obligation. The option “Exercise a WAN partition and reconcile approval events against immutable records after recovery” instead addresses the requested acceptance verification.

D:

Lower initial infrastructure cost does not satisfy auditable decisions or disconnected operation. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that branches need approvals even when a regional WAN circuit fails.

Question 238

Consider Sustainable packaging manufacturer and its energy-aware workload economics workload. The issue is that nightly noncritical reports run during peak electricity pricing even though deadline is the next afternoon; the current observation is that billing data shows batch energy and instance costs spike in fixed early hours. The team must ensure that reports must be complete by 14:00, not in real time. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?

  1. Trial alternative schedules with rollback before peak season
  2. Schedule nonurgent batch jobs in lower-cost windows subject to completion SLO
  3. Monitor deadline misses, cost and unexpected runtime expansion
  4. Compare time flexibility, consumption profiles and data freshness
  5. Terminate all reports to maximize energy savings

Explanation

Correct Answers

A:

Trial alternative schedules with rollback before peak season is a controlled means to introduce the approved architecture while meeting the requirement that reports must be complete by 14:00, not in real time. 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.

B:

Schedule nonurgent batch jobs in lower-cost windows subject to completion SLO targets the underlying issue (nightly noncritical reports run during peak electricity pricing even though deadline is the next afternoon) rather than merely reporting symptoms. It also preserves the required outcome (reports must be complete by 14:00, not in real time), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.

Incorrect Answers

C:

Monitoring energy-aware workload economics for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: nightly noncritical reports run during peak electricity pricing even though deadline is the next afternoon.

D:

This diagnoses the original issue (nightly noncritical reports run during peak electricity pricing even though deadline is the next afternoon), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.

E:

Zero processing fails the defined reporting objective. The shortcut does not supply the requested design and safe rollout for energy-aware workload economics, where billing data shows batch energy and instance costs spike in fixed early hours.

Question 239

Consider Public archive network and its support dependency escalation workload. The issue is that staff cannot resolve sporadic object read failures because the case lacks request IDs; the current observation is that support replies repeatedly ask for missing bucket and operation context. The team must ensure that public document retrieval must be restored quickly without exposing personal data. The team has completed discovery. Which preventive or corrective architecture is most appropriate?

  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. Define support runbooks with minimal reproducible evidence and safe redaction
  4. Track repeated evidence gaps and delayed support resolution

Explanation

Correct Answer

C:

Define support runbooks with minimal reproducible evidence and safe redaction targets the underlying issue (staff cannot resolve sporadic object read failures because the case lacks request IDs) rather than merely reporting symptoms. It also preserves the required outcome (public document retrieval must be restored quickly without exposing personal data), which a target-state design must satisfy.

Incorrect Answers

A:

Support evidence should be sufficient and minimized, not a credential leak. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that public document retrieval must be restored quickly without exposing personal data.

B:

The alternative “Collect failing request identifiers, timestamps, bucket location and service status” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, support replies repeatedly ask for missing bucket and operation context. The option “Define support runbooks with minimal reproducible evidence and safe redaction” instead addresses the requested architecture selection.

D:

The alternative “Track repeated evidence gaps and delayed support resolution” measures results without defining the preventive design now required. In the reported observation, support replies repeatedly ask for missing bucket and operation context. The option “Define support runbooks with minimal reproducible evidence and safe redaction” instead addresses the requested architecture selection.

Question 240

At Agricultural crop analysis firm, the agentic data preparation workload has a documented risk: different dataset formats feed model training but lineage disappears when one parser fails. The review found that pipeline logs show successful jobs produce artifacts from incompatible schema versions. The architecture must also ensure that model decisions must be explainable against source training records. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?

  1. Monitor schema rejection, data quality and drift by source
  2. Orchestrate data preparation and training with versioned pipeline components
  3. Inspect schema contracts, transformation versions and artifact references
  4. Stage parser updates through validation and checkpointed pipeline runs
  5. Let every pipeline step read and overwrite the same unversioned training table

Explanation

Correct Answers

B:

Orchestrate data preparation and training with versioned pipeline components targets the underlying issue (different dataset formats feed model training but lineage disappears when one parser fails) rather than merely reporting symptoms. It also preserves the required outcome (model decisions must be explainable against source training records), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.

D:

Stage parser updates through validation and checkpointed pipeline runs is a controlled means to introduce the approved architecture while meeting the requirement that model decisions must be explainable against source training records. 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 agentic data preparation for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: different dataset formats feed model training but lineage disappears when one parser fails.

C:

This diagnoses the original issue (different dataset formats feed model training but lineage disappears when one parser fails), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.

E:

Mutable shared state destroys lineage and reproducibility. The shortcut does not supply the requested design and safe rollout for agentic data preparation, where pipeline logs show successful jobs produce artifacts from incompatible schema versions.

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