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 36

Question 350

Consider Digital rehabilitation provider and its video consultation storage workload. The issue is that the initial backup design stores both primary recordings and snapshots in one project; the current observation is that access review shows a project editor can delete all versions. The team must ensure that clinical videos require recovery after a compromised administration account. Which continuous monitoring approach best reveals recurrence or changing dependencies?

  1. Attempt deletion with an ordinary project editor and restore a verified sample
  2. Use cross-project immutable retention and scoped recovery identities
  3. Keep backups as deletable snapshots owned by the same compromised principal
  4. Monitor privileged retention changes, backup failures and restore timing

Explanation

Correct Answer

D:

Monitor privileged retention changes, backup failures and restore timing reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (the initial backup design stores both primary recordings and snapshots in one project) rather than treating the first successful test as permanent assurance.

Incorrect Answers

A:

The alternative “Attempt deletion with an ordinary project editor and restore a verified sample” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, access review shows a project editor can delete all versions. The option “Monitor privileged retention changes, backup failures and restore timing” instead addresses the requested ongoing operational assurance.

B:

The alternative “Use cross-project immutable retention and scoped recovery identities” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, access review shows a project editor can delete all versions. The option “Monitor privileged retention changes, backup failures and restore timing” instead addresses the requested ongoing operational assurance.

C:

Shared delete authority destroys recovery independence. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that clinical videos require recovery after a compromised administration account.

Question 351

Case study: Metropolitan bus operator: customer API throttling

Metropolitan bus operator relies on customer API throttling to deliver its operational commitments. The current architectural problem is that one external client causes an overloaded trip-planning API while most users are normal. The team has recorded this evidence: gateway logs show one tenant produces 80% of requests. Any proposed response must preserve the requirement that emergency schedule lookups must remain available to all operators.

Consider Metropolitan bus operator and its customer API throttling workload. The issue is that one external client causes an overloaded trip-planning API while most users are normal; the current observation is that gateway logs show one tenant produces 80% of requests. The team must ensure that emergency schedule lookups must remain available to all operators. The change committee needs to understand the current system rather than install a fix yet. What should it do?

  1. Analyze tenant request distribution, legitimate peak patterns and error rates
  2. Introduce preview quotas and monitor protected emergency routes
  3. Design per-tenant API quotas and fairness policies using Apigee
  4. Apply a single global rate cap that blocks every tenant equally

Explanation

Correct Answer

A:

Analyze tenant request distribution, legitimate peak patterns and error rates is the appropriate diagnostic because the observation—gateway logs show one tenant produces 80% of requests—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (one external client causes an overloaded trip-planning API while most users are normal) before the design is approved.

Incorrect Answers

B:

The alternative “Introduce preview quotas and monitor protected emergency routes” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, gateway logs show one tenant produces 80% of requests. The option “Analyze tenant request distribution, legitimate peak patterns and error rates” instead addresses the requested root-cause evidence.

C:

The alternative “Design per-tenant API quotas and fairness policies using Apigee” is target architecture selection; it does not establish why the observed path failed. In the reported observation, gateway logs show one tenant produces 80% of requests. The option “Analyze tenant request distribution, legitimate peak patterns and error rates” instead addresses the requested root-cause evidence.

D:

A global cap penalizes unaffected users rather than noisy clients. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that emergency schedule lookups must remain available to all operators.

Question 352

University biotech startup plans to update encryption perimeter access. Investigators found that permission requests include objectViewer on clinical sequence data, consistent with the reported problem that developers want to give a vendor direct plaintext bucket access for pipeline debugging. The response must satisfy the requirement that vendor diagnosis must use masked synthetic samples only. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?

  1. Provision time-limited vendor access to sanitized test resources
  2. Use isolated debugging data and conditional IAM instead of production plaintext grants
  3. Inventory vendor operations, dataset classifications and authorized alternatives
  4. Grant the vendor project Owner for a week to simplify debugging

Explanation

Correct Answer

C:

Inventory vendor operations, dataset classifications and authorized alternatives is the appropriate diagnostic because the observation—permission requests include objectViewer on clinical sequence data—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (developers want to give a vendor direct plaintext bucket access for pipeline debugging) before the design is approved.

Incorrect Answers

A:

The alternative “Provision time-limited vendor access to sanitized test resources” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, permission requests include objectViewer on clinical sequence data. The option “Inventory vendor operations, dataset classifications and authorized alternatives” instead addresses the requested root-cause evidence.

B:

The alternative “Use isolated debugging data and conditional IAM instead of production plaintext grants” is target architecture selection; it does not establish why the observed path failed. In the reported observation, permission requests include objectViewer on clinical sequence data. The option “Inventory vendor operations, dataset classifications and authorized alternatives” instead addresses the requested root-cause evidence.

D:

Temporary unrestricted ownership still permits large-scale disclosure. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that vendor diagnosis must use masked synthetic samples only.

Question 353

At National small-business bank, the finops reserved capacity workload has a documented risk: leadership commits all compute to three-year reservations despite demand reduction plans. The review found that forecasts show the main batch system will retire within six months. The architecture must also ensure that reserved spend must not exceed expected future compute usage. What enduring Google Cloud design should the team choose now that the failure mode is understood?

  1. Estimate utilization, confidence of retirement and discount tradeoffs
  2. Choose commitments only for stable baseline needs and leave uncertain capacity flexible
  3. Buy maximal three-year reservations for workloads scheduled for decommission
  4. Monitor commitment utilization and forecast changes

Explanation

Correct Answer

B:

Choose commitments only for stable baseline needs and leave uncertain capacity flexible targets the underlying issue (leadership commits all compute to three-year reservations despite demand reduction plans) rather than merely reporting symptoms. It also preserves the required outcome (reserved spend must not exceed expected future compute usage), which a target-state design must satisfy.

Incorrect Answers

A:

The alternative “Estimate utilization, confidence of retirement and discount tradeoffs” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, forecasts show the main batch system will retire within six months. The option “Choose commitments only for stable baseline needs and leave uncertain capacity flexible” instead addresses the requested architecture selection.

C:

Long obligations can outlast the resource demand. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that reserved spend must not exceed expected future compute usage.

D:

The alternative “Monitor commitment utilization and forecast changes” measures results without defining the preventive design now required. In the reported observation, forecasts show the main batch system will retire within six months. The option “Choose commitments only for stable baseline needs and leave uncertain capacity flexible” instead addresses the requested architecture selection.

Question 354

Case study: Online ticket lottery: reservation API

Online ticket lottery relies on reservation API to deliver its operational commitments. The current architectural problem is that the planned single service is sized for ordinary traffic but purchases arrive in minute-long surges. The team has recorded this evidence: load tests show 40x burst with a limited pool of unique seats. Any proposed response must preserve the requirement that a seat must not be reserved twice under concurrent requests.

Consider Online ticket lottery and its reservation API workload. The issue is that the planned single service is sized for ordinary traffic but purchases arrive in minute-long surges; the current observation is that load tests show 40x burst with a limited pool of unique seats. The team must ensure that a seat must not be reserved twice under concurrent requests. The target architecture is approved; execution without disruption is the remaining decision. Which rollout action is best?

  1. Cache seat ownership only in eventually consistent edge storage
  2. Track queue admission, reservation conflicts and failed checkout rate
  3. Canary the new path with bounded traffic and rollback under load
  4. Choose elastic stateless entrypoints with atomic reservation storage and admission control

Explanation

Correct Answer

C:

Canary the new path with bounded traffic and rollback under load is a controlled means to introduce the approved architecture while meeting the requirement that a seat must not be reserved twice under concurrent requests. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.

Incorrect Answers

A:

Stale edge ownership cannot prevent double booking. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that a seat must not be reserved twice under concurrent requests.

B:

The alternative “Track queue admission, reservation conflicts and failed checkout rate” addresses later monitoring rather than the actual controlled deployment. In the reported observation, load tests show 40x burst with a limited pool of unique seats. The option “Canary the new path with bounded traffic and rollback under load” instead addresses the requested controlled implementation.

D:

The alternative “Choose elastic stateless entrypoints with atomic reservation storage and admission control” describes the chosen design, but not how it is introduced safely. In the reported observation, load tests show 40x burst with a limited pool of unique seats. The option “Canary the new path with bounded traffic and rollback under load” instead addresses the requested controlled implementation.

Question 355

At Industrial maintenance provider, the Google Cloud design for equipment-manual visual search is affected because staff send photos of parts and want to find matching safety documents. A review found that sample images are noisy while text identifiers are only partly visible. The proposed response must account for the requirement that manual search must not invent equipment safety instructions. Which controlled implementation should be used to preserve operational continuity during the change?

  1. Let a generative model invent manufacturer safety procedures without retrieved evidence
  2. Pilot a small catalog with human review for low-confidence matches
  3. Combine suitable Vision API extraction with grounded document search against approved manuals
  4. Track image extraction errors and obsolete manual versions

Explanation

Correct Answer

B:

Pilot a small catalog with human review for low-confidence matches is a controlled means to introduce the approved architecture while meeting the requirement that manual search must not invent equipment safety instructions. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.

Incorrect Answers

A:

Hallucinated safety instructions can create physical risk. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that manual search must not invent equipment safety instructions.

C:

The alternative “Combine suitable Vision API extraction with grounded document search against approved manuals” describes the chosen design, but not how it is introduced safely. In the reported observation, sample images are noisy while text identifiers are only partly visible. The option “Pilot a small catalog with human review for low-confidence matches” instead addresses the requested controlled implementation.

D:

The alternative “Track image extraction errors and obsolete manual versions” addresses later monitoring rather than the actual controlled deployment. In the reported observation, sample images are noisy while text identifiers are only partly visible. The option “Pilot a small catalog with human review for low-confidence matches” instead addresses the requested controlled implementation.

Question 356

Case study: Insurance document platform: external customer authentication

Insurance document platform relies on external customer authentication to deliver its operational commitments. The current architectural problem is that a business partner requests privileged access using only a static shared API key. The team has recorded this evidence: request log shows the same key used from several external offices. Any proposed response must preserve the requirement that partner access must identify the calling workload and enforce scopes.

The external customer authentication environment at Insurance document platform faces this issue: a business partner requests privileged access using only a static shared API key. Supporting evidence shows that request log shows the same key used from several external offices. The architect must preserve the requirement that partner access must identify the calling workload and enforce scopes. Before approving a solution, which analysis most directly clarifies the underlying dependency or control gap?

  1. Onboard partner issuers with trust conditions and retire the static key
  2. Discover partner identity provider, claims and least-privilege API operations
  3. Adopt federated workload identity and scoped authorization with token expiry
  4. Expand the shared API key to every document endpoint for convenience

Explanation

Correct Answer

B:

Discover partner identity provider, claims and least-privilege API operations is the appropriate diagnostic because the observation—request log shows the same key used from several external offices—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (a business partner requests privileged access using only a static shared API key) before the design is approved.

Incorrect Answers

A:

The alternative “Onboard partner issuers with trust conditions and retire the static key” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, request log shows the same key used from several external offices. The option “Discover partner identity provider, claims and least-privilege API operations” instead addresses the requested root-cause evidence.

C:

The alternative “Adopt federated workload identity and scoped authorization with token expiry” is target architecture selection; it does not establish why the observed path failed. In the reported observation, request log shows the same key used from several external offices. The option “Discover partner identity provider, claims and least-privilege API operations” instead addresses the requested root-cause evidence.

D:

Shared keys cannot represent least-privilege workload identity. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that partner access must identify the calling workload and enforce scopes.

Question 357

At Hospital payments administrator, the Google Cloud design for database point-in-time recovery is affected because an operator accidentally ran a broad UPDATE against the claims settlement database. A review found that audit shows thousands of records changed before detection. The proposed response must account for the requirement that finance requires restoration to immediately before the erroneous transaction. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?

  1. Restore from a week-old cold snapshot and overwrite new valid payments blindly
  2. Track log-retention windows, backup gaps and restore test age
  3. Identify commit timestamps, backup settings and business replay obligations
  4. Enable recovery policy and rehearse isolated restore before relying on it
  5. Set continuous backup/PITR where supported and segregated recovery permissions

Explanation

Correct Answers

D:

Enable recovery policy and rehearse isolated restore before relying on it is a controlled means to introduce the approved architecture while meeting the requirement that finance requires restoration to immediately before the erroneous transaction. 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:

Set continuous backup/PITR where supported and segregated recovery permissions targets the underlying issue (an operator accidentally ran a broad UPDATE against the claims settlement database) rather than merely reporting symptoms. It also preserves the required outcome (finance requires restoration to immediately before the erroneous transaction), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.

Incorrect Answers

A:

An old snapshot without transaction reconciliation can discard legitimate payments. The shortcut does not supply the requested design and safe rollout for database point-in-time recovery, where audit shows thousands of records changed before detection.

B:

Monitoring database point-in-time recovery for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: an operator accidentally ran a broad UPDATE against the claims settlement database.

C:

This diagnoses the original issue (an operator accidentally ran a broad UPDATE against the claims settlement database), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.

Question 358

Consider Automotive warranty platform and its parts inventory read API workload. The issue is that a global rollout uses one master inventory database for every dealership lookup; the current observation is that traces show cross-ocean reads dominate response time. The team must ensure that inventory commitments must remain serializable where parts are scarce. The team has completed discovery. Which preventive or corrective architecture is most appropriate?

  1. Segment inventory reads, allocation writes and region-specific SLA needs
  2. Create region-proximate read views while keeping authoritative reservation writes consistent
  3. Use independent writable inventory databases without conflict handling
  4. Track replica lag, order conflicts and cross-region read costs

Explanation

Correct Answer

B:

Create region-proximate read views while keeping authoritative reservation writes consistent targets the underlying issue (a global rollout uses one master inventory database for every dealership lookup) rather than merely reporting symptoms. It also preserves the required outcome (inventory commitments must remain serializable where parts are scarce), which a target-state design must satisfy.

Incorrect Answers

A:

The alternative “Segment inventory reads, allocation writes and region-specific SLA needs” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, traces show cross-ocean reads dominate response time. The option “Create region-proximate read views while keeping authoritative reservation writes consistent” instead addresses the requested architecture selection.

C:

Uncoordinated writable replicas can oversell scarce parts. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that inventory commitments must remain serializable where parts are scarce.

D:

The alternative “Track replica lag, order conflicts and cross-region read costs” measures results without defining the preventive design now required. In the reported observation, traces show cross-ocean reads dominate response time. The option “Create region-proximate read views while keeping authoritative reservation writes consistent” instead addresses the requested architecture selection.

Question 359

At Regional airline, the crew roster API workload has a documented risk: a database primary restart causes regional crews to lose schedules for an entire shift. The review found that failure logs show read-only standby exists but application uses only one endpoint. The architecture must also ensure that dispatch must read the last approved crew plan during recovery. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?

  1. Use high-availability database failover and a validated read-only contingency view
  2. Classify read/write operations, acceptable staleness and failover dependencies
  3. Stage client reconnection and crew-cache refresh before database switchover
  4. Point every client to an unreplicated local file as the only source

Explanation

Correct Answer

B:

Classify read/write operations, acceptable staleness and failover dependencies is the appropriate diagnostic because the observation—failure logs show read-only standby exists but application uses only one endpoint—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (a database primary restart causes regional crews to lose schedules for an entire shift) before the design is approved.

Incorrect Answers

A:

The alternative “Use high-availability database failover and a validated read-only contingency view” is target architecture selection; it does not establish why the observed path failed. In the reported observation, failure logs show read-only standby exists but application uses only one endpoint. The option “Classify read/write operations, acceptable staleness and failover dependencies” instead addresses the requested root-cause evidence.

C:

The alternative “Stage client reconnection and crew-cache refresh before database switchover” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, failure logs show read-only standby exists but application uses only one endpoint. The option “Classify read/write operations, acceptable staleness and failover dependencies” instead addresses the requested root-cause evidence.

D:

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

Question 360

At Multinational consulting alliance, the shared IAM inheritance workload has a documented risk: a merger added interns to a group that has editor permission on financial-production resources. The review found that IAM policy audit shows project roles inherited from the organization root. The architecture must also ensure that production access must be limited to verified operational duties. What enduring Google Cloud design should the team choose now that the failure mode is understood?

  1. Create a new group but keep the old wildcard organization binding
  2. Watch group membership changes and inherited privilege escalation
  3. Move broad grants to scoped groups and use conditional role bindings where appropriate
  4. Identify inherited member groups and smallest needed job privileges

Explanation

Correct Answer

C:

Move broad grants to scoped groups and use conditional role bindings where appropriate targets the underlying issue (a merger added interns to a group that has editor permission on financial-production resources) rather than merely reporting symptoms. It also preserves the required outcome (production access must be limited to verified operational duties), which a target-state design must satisfy.

Incorrect Answers

A:

A new group does not negate an existing broad inherited permission. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that production access must be limited to verified operational duties.

B:

The alternative “Watch group membership changes and inherited privilege escalation” measures results without defining the preventive design now required. In the reported observation, IAM policy audit shows project roles inherited from the organization root. The option “Move broad grants to scoped groups and use conditional role bindings where appropriate” instead addresses the requested architecture selection.

D:

The alternative “Identify inherited member groups and smallest needed job privileges” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, IAM policy audit shows project roles inherited from the organization root. The option “Move broad grants to scoped groups and use conditional role bindings where appropriate” instead addresses the requested architecture selection.

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