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 30

Question 290

Case study: National airport lounge operator: managed Prometheus scraping

National airport lounge operator relies on managed Prometheus scraping to deliver its operational commitments. The current architectural problem is that several GKE services expose metrics but the monitoring system has blind spots after namespace moves. The team has recorded this evidence: scrape health shows targets disappeared when Kubernetes labels changed. Any proposed response must preserve the requirement that capacity alerts must remain tied to actual service discovery.

At National airport lounge operator, the managed Prometheus scraping workload has a documented risk: several GKE services expose metrics but the monitoring system has blind spots after namespace moves. The review found that scrape health shows targets disappeared when Kubernetes labels changed. The architecture must also ensure that capacity alerts must remain tied to actual service discovery. What enduring Google Cloud design should the team choose now that the failure mode is understood?

  1. Treat all unlabeled zero metrics as healthy application inactivity
  2. Watch missing targets, cardinality growth and failed scrapes
  3. Configure Managed Service for Prometheus collectors with stable target discovery
  4. Inspect Kubernetes service selectors, relabeling and scrape permissions

Explanation

Correct Answer

C:

Configure Managed Service for Prometheus collectors with stable target discovery targets the underlying issue (several GKE services expose metrics but the monitoring system has blind spots after namespace moves) rather than merely reporting symptoms. It also preserves the required outcome (capacity alerts must remain tied to actual service discovery), which a target-state design must satisfy.

Incorrect Answers

A:

Missing scrape targets can look like falsely healthy zeros. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that capacity alerts must remain tied to actual service discovery.

B:

The alternative “Watch missing targets, cardinality growth and failed scrapes” measures results without defining the preventive design now required. In the reported observation, scrape health shows targets disappeared when Kubernetes labels changed. The option “Configure Managed Service for Prometheus collectors with stable target discovery” instead addresses the requested architecture selection.

D:

The alternative “Inspect Kubernetes service selectors, relabeling and scrape permissions” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, scrape health shows targets disappeared when Kubernetes labels changed. The option “Configure Managed Service for Prometheus collectors with stable target discovery” instead addresses the requested architecture selection.

Question 291

Large airline revenue group plans to update service account impersonation. Investigators found that permission audit shows callers can create keys and change unrelated resources, consistent with the reported problem that automation assumes project Editor role is required to invoke one reporting job. The response must satisfy the requirement that billing reads must use auditable least privilege. The team needs an operations signal rather than another design or one-time test. What should it track?

  1. Prove the job runs but cannot modify unrelated billing data
  2. Use a downloaded project Owner key for every reporting job
  3. Grant narrowly scoped service-account impersonation and resource-specific reader roles
  4. Monitor impersonation events and newly created service account keys

Explanation

Correct Answer

D:

Monitor impersonation events and newly created service account keys reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (automation assumes project Editor role is required to invoke one reporting job) rather than treating the first successful test as permanent assurance.

Incorrect Answers

A:

The alternative “Prove the job runs but cannot modify unrelated billing data” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, permission audit shows callers can create keys and change unrelated resources. The option “Monitor impersonation events and newly created service account keys” instead addresses the requested ongoing operational assurance.

B:

Overprivileged permanent keys greatly increase compromise impact. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that billing reads must use auditable least privilege.

C:

The alternative “Grant narrowly scoped service-account impersonation and resource-specific reader roles” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, permission audit shows callers can create keys and change unrelated resources. The option “Monitor impersonation events and newly created service account keys” instead addresses the requested ongoing operational assurance.

Question 292

At Neighborhood banking cooperative, the loan-origination approval service workload has a documented risk: the planned monolith migration promises lower costs but omits the regulatory audit and branch-outage requirements. The review found that business interviews reveal a four-hour branch outage limit and an immutable decision-history obligation. The architecture must also ensure that branches need approvals even when a regional WAN circuit fails. What follow-up metric or alert will identify emerging failures after the initial acceptance test?

  1. Track queue age, replay conflicts and branch recovery objectives
  2. Choose the cheapest single-zone VM and discard decision events once the API responds
  3. Exercise a WAN partition and reconcile approval events against immutable records after recovery
  4. Design a regional approval API with durable event logging and a tested local queue for temporary disconnection

Explanation

Correct Answer

A:

Track queue age, replay conflicts and branch recovery objectives reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (the planned monolith migration promises lower costs but omits the regulatory audit and branch-outage requirements) rather than treating the first successful test as permanent assurance.

Incorrect Answers

B:

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

C:

The alternative “Exercise a WAN partition and reconcile approval events against immutable records after recovery” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, business interviews reveal a four-hour branch outage limit and an immutable decision-history obligation. The option “Track queue age, replay conflicts and branch recovery objectives” instead addresses the requested ongoing operational assurance.

D:

The alternative “Design a regional approval API with durable event logging and a tested local queue for temporary disconnection” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, business interviews reveal a four-hour branch outage limit and an immutable decision-history obligation. The option “Track queue age, replay conflicts and branch recovery objectives” instead addresses the requested ongoing operational assurance.

Question 293

At National retailer, the Google Cloud design for SOC 2 assurance evidence is affected because cloud service roles change without retaining approval artifacts for audit. A review found that internal audit finds no linkage between IAM grants and access requests. The proposed response must account for the requirement that auditor must reconstruct who authorized production privileges. 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. Treat an informal verbal confirmation as complete access audit evidence
  2. Exclude the affected dependency from all future tests and incident metrics to simplify reporting
  3. Map evidence sources, authorization workflow and retained approvals
  4. Sample privileged grant changes and trace each to a valid approved request
  5. Track orphan grants, missing approvals and retained evidence coverage
  6. Design traceable access approval, just-in-time privileges and immutable change records

Explanation

Correct Answers

C:

Map evidence sources, authorization workflow and retained approvals is the appropriate diagnostic because the observation—internal audit finds no linkage between IAM grants and access requests—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (cloud service roles change without retaining approval artifacts for audit) before the design is approved. It supplies the pre-design diagnostic evidence requested.

D:

Sample privileged grant changes and trace each to a valid approved request is a direct acceptance test of the path implicated by internal audit finds no linkage between IAM grants and access requests. It checks that the original risk (cloud service roles change without retaining approval artifacts for audit) has actually been controlled and tests that permitted operations still meet the requirement that auditor must reconstruct who authorized production privileges. It supplies the separate post-change acceptance result requested.

E:

Track orphan grants, missing approvals and retained evidence coverage reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (cloud service roles change without retaining approval artifacts for audit) rather than treating the first successful test as permanent assurance. It supplies the ongoing observation requested.

Incorrect Answers

A:

Unrecorded approvals cannot support reproducible assurance. It cannot satisfy the required evidence stages.

B:

Omitting the relevant dependency from testing and monitoring would hide, not correct, recurrence of the failure. In particular, the observed issue was: internal audit finds no linkage between IAM grants and access requests.

F:

Designing SOC 2 assurance evidence addresses the root cause, but this specific three-part question asks for evidence to diagnose, accept and continuously verify the response to cloud service roles change without retaining approval artifacts for audit, not another design proposal.

Question 294

Case study: State licensing agency: multi-vendor service ownership

State licensing agency relies on multi-vendor service ownership to deliver its operational commitments. The current architectural problem is that two suppliers both claim the other owns an expired security certificate. The team has recorded this evidence: contract maps have no accountable production certificate owner. Any proposed response must preserve the requirement that public licensing cannot lose authentication on renewal day.

Consider State licensing agency and its multi-vendor service ownership workload. The issue is that two suppliers both claim the other owns an expired security certificate; the current observation is that contract maps have no accountable production certificate owner. The team must ensure that public licensing cannot lose authentication on renewal day. The change committee needs to understand the current system rather than install a fix yet. What should it do?

  1. Assign one operational certificate owner with explicit supplier escalation
  2. Map contractual RACI, certificate dependencies and escalation paths
  3. Introduce shared change calendar and renewal notifications
  4. Wait for whichever supplier notices expiry first

Explanation

Correct Answer

B:

Map contractual RACI, certificate dependencies and escalation paths is the appropriate diagnostic because the observation—contract maps have no accountable production certificate owner—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (two suppliers both claim the other owns an expired security certificate) before the design is approved.

Incorrect Answers

A:

The alternative “Assign one operational certificate owner with explicit supplier escalation” is target architecture selection; it does not establish why the observed path failed. In the reported observation, contract maps have no accountable production certificate owner. The option “Map contractual RACI, certificate dependencies and escalation paths” instead addresses the requested root-cause evidence.

C:

The alternative “Introduce shared change calendar and renewal notifications” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, contract maps have no accountable production certificate owner. The option “Map contractual RACI, certificate dependencies and escalation paths” instead addresses the requested root-cause evidence.

D:

Unassigned renewal responsibility causes preventable outages. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that public licensing cannot lose authentication on renewal day.

Question 295

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 encryption key governance workload has a documented risk: payment data uses default encryption but contract requires customer control over key rotation. The review found that key inventory shows provider-managed keys with no customer-managed lifecycle. The architecture must also ensure that regulated card records require tracked access and planned key retirement. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?

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

Explanation

Correct Answers

A:

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

E:

Choose Cloud KMS CMEK where supported with separated key administrators and encryption users targets the underlying issue (payment data uses default encryption but contract requires customer control over key rotation) rather than merely reporting symptoms. It also preserves the required outcome (regulated card records require tracked access and planned key retirement), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.

Incorrect Answers

B:

This diagnoses the original issue (payment data uses default encryption but contract requires customer control over key rotation), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.

C:

Monitoring encryption key governance for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: payment data uses default encryption but contract requires customer control over key rotation.

D:

Shared metadata does not provide protected KMS custody. The shortcut does not supply the requested design and safe rollout for encryption key governance, where key inventory shows provider-managed keys with no customer-managed lifecycle.

Question 296

At National investment office, the emergency break-glass access workload has a documented risk: a single admin group controls production recovery and can also edit security logs. The review found that tabletop shows no independent emergency account if primary IdP fails. The architecture must also ensure that recovery access must be auditable and tightly time-bound. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?

  1. Map critical emergency actions, alternative identities and audit paths
  2. Provision sealed emergency accounts with quarterly practice and credential rotation
  3. Share one break-glass password in the team chat channel
  4. Define protected break-glass identities with separated ownership and alerts

Explanation

Correct Answer

A:

Map critical emergency actions, alternative identities and audit paths is the appropriate diagnostic because the observation—tabletop shows no independent emergency account if primary IdP fails—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (a single admin group controls production recovery and can also edit security logs) before the design is approved.

Incorrect Answers

B:

The alternative “Provision sealed emergency accounts with quarterly practice and credential rotation” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, tabletop shows no independent emergency account if primary IdP fails. The option “Map critical emergency actions, alternative identities and audit paths” instead addresses the requested root-cause evidence.

C:

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

D:

The alternative “Define protected break-glass identities with separated ownership and alerts” is target architecture selection; it does not establish why the observed path failed. In the reported observation, tabletop shows no independent emergency account if primary IdP fails. The option “Map critical emergency actions, alternative identities and audit paths” instead addresses the requested root-cause evidence.

Question 297

Consider International digital learning network and its Cloud Trace bottleneck workload. The issue is that users see slow lesson page load but service-level metrics show each component as healthy; the current observation is that trace spans reveal sequential requests to a distant analytics service. The team must ensure that lesson pages must remain responsive if nonessential analytics pauses. The change committee needs to understand the current system rather than install a fix yet. What should it do?

  1. Move optional analytics off the synchronous critical path with trace instrumentation
  2. Increase every VM size without checking span-level critical path
  3. Introduce asynchronous recording and gradually shift user cohorts
  4. Capture representative distributed traces and latency contributions

Explanation

Correct Answer

D:

Capture representative distributed traces and latency contributions is the appropriate diagnostic because the observation—trace spans reveal sequential requests to a distant analytics service—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (users see slow lesson page load but service-level metrics show each component as healthy) before the design is approved.

Incorrect Answers

A:

The alternative “Move optional analytics off the synchronous critical path with trace instrumentation” is target architecture selection; it does not establish why the observed path failed. In the reported observation, trace spans reveal sequential requests to a distant analytics service. The option “Capture representative distributed traces and latency contributions” instead addresses the requested root-cause evidence.

B:

Generic scaling need not solve avoidable synchronous waiting. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that lesson pages must remain responsive if nonessential analytics pauses.

C:

The alternative “Introduce asynchronous recording and gradually shift user cohorts” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, trace spans reveal sequential requests to a distant analytics service. The option “Capture representative distributed traces and latency contributions” instead addresses the requested root-cause evidence.

Question 298

At Agricultural crop analysis firm, the Google Cloud design for agentic data preparation is affected because different dataset formats feed model training but lineage disappears when one parser fails. A review found that pipeline logs show successful jobs produce artifacts from incompatible schema versions. The proposed response must account for the requirement that model decisions must be explainable against source training records. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?

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

Explanation

Correct Answer

C:

Inspect schema contracts, transformation versions and artifact references is the appropriate diagnostic because the observation—pipeline logs show successful jobs produce artifacts from incompatible schema versions—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (different dataset formats feed model training but lineage disappears when one parser fails) before the design is approved.

Incorrect Answers

A:

Mutable shared state destroys lineage and reproducibility. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that model decisions must be explainable against source training records.

B:

The alternative “Stage parser updates through validation and checkpointed pipeline runs” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, pipeline logs show successful jobs produce artifacts from incompatible schema versions. The option “Inspect schema contracts, transformation versions and artifact references” instead addresses the requested root-cause evidence.

D:

The alternative “Orchestrate data preparation and training with versioned pipeline components” is target architecture selection; it does not establish why the observed path failed. In the reported observation, pipeline logs show successful jobs produce artifacts from incompatible schema versions. The option “Inspect schema contracts, transformation versions and artifact references” instead addresses the requested root-cause evidence.

Question 299

Consider Manufacturer predictive maintenance team and its Agent Platform ML pipelines workload. The issue is that each retraining run uses a different preprocessing notebook with no lineage; the current observation is that model results diverge even when training data IDs match. The team must ensure that factory anomaly models need reproducible releases and operator approval. The target architecture is approved; execution without disruption is the remaining decision. Which rollout action is best?

  1. Use versioned ML pipelines with recorded artifacts and reproducible evaluation gates
  2. Migrate manual retraining into an approved Agent Platform pipeline in shadow mode
  3. Train directly on mutable shared notebooks without tracking artifact versions
  4. Monitor pipeline failures, model drift and promotion exceptions

Explanation

Correct Answer

B:

Migrate manual retraining into an approved Agent Platform pipeline in shadow mode is a controlled means to introduce the approved architecture while meeting the requirement that factory anomaly models need reproducible releases and operator approval. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.

Incorrect Answers

A:

The alternative “Use versioned ML pipelines with recorded artifacts and reproducible evaluation gates” describes the chosen design, but not how it is introduced safely. In the reported observation, model results diverge even when training data IDs match. The option “Migrate manual retraining into an approved Agent Platform pipeline in shadow mode” instead addresses the requested controlled implementation.

C:

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

D:

The alternative “Monitor pipeline failures, model drift and promotion exceptions” addresses later monitoring rather than the actual controlled deployment. In the reported observation, model results diverge even when training data IDs match. The option “Migrate manual retraining into an approved Agent Platform pipeline in shadow mode” instead addresses the requested controlled implementation.

Question 300

At University astronomy project, the Google Cloud design for temporary sky-image processing is affected because large image batch runs only one weekend a month yet reserved VMs are always on. A review found that cost report shows accelerator nodes idle more than ninety percent of the time. The proposed response must account for the requirement that scientific jobs can checkpoint and resume after interruption. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?

  1. Assess preemption tolerance, GPU sizing and checkpoint intervals
  2. Test checkpoint restoration and quota-aware job retries before scaling
  3. Use job orchestration with Spot VMs for interruptible batch computation
  4. Use spot capacity for the only stateful database with no recovery strategy

Explanation

Correct Answer

A:

Assess preemption tolerance, GPU sizing and checkpoint intervals is the appropriate diagnostic because the observation—cost report shows accelerator nodes idle more than ninety percent of the time—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (large image batch runs only one weekend a month yet reserved VMs are always on) before the design is approved.

Incorrect Answers

B:

The alternative “Test checkpoint restoration and quota-aware job retries before scaling” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, cost report shows accelerator nodes idle more than ninety percent of the time. The option “Assess preemption tolerance, GPU sizing and checkpoint intervals” instead addresses the requested root-cause evidence.

C:

The alternative “Use job orchestration with Spot VMs for interruptible batch computation” is target architecture selection; it does not establish why the observed path failed. In the reported observation, cost report shows accelerator nodes idle more than ninety percent of the time. The option “Assess preemption tolerance, GPU sizing and checkpoint intervals” instead addresses the requested root-cause evidence.

D:

Preemptible nodes are unsuitable as unprotected authoritative state. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that scientific jobs can checkpoint and resume after interruption.

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