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 35

Question 340

At International health insurer, the Cloud Build release flow workload has a documented risk: a deployment pipeline places unreviewed images into production after every commit. The review found that release logs show no artifact promotion or security scan before a production deploy. The architecture must also ensure that production releases require signed approval and a reversible rollout. What follow-up metric or alert will identify emerging failures after the initial acceptance test?

  1. Allow every developer to deploy from a mutable local image tag
  2. Design gated CI/CD with immutable artifacts, tests, policy checks and deploy approvals
  3. Monitor skipped gates, broken builds and rollout error budgets
  4. Attempt promotion of an unsigned build and verify it is rejected

Explanation

Correct Answer

C:

Monitor skipped gates, broken builds and rollout error budgets reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a deployment pipeline places unreviewed images into production after every commit) rather than treating the first successful test as permanent assurance.

Incorrect Answers

A:

Mutable unreviewed releases cannot provide attributable production control. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that production releases require signed approval and a reversible rollout.

B:

The alternative “Design gated CI/CD with immutable artifacts, tests, policy checks and deploy approvals” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, release logs show no artifact promotion or security scan before a production deploy. The option “Monitor skipped gates, broken builds and rollout error budgets” instead addresses the requested ongoing operational assurance.

D:

The alternative “Attempt promotion of an unsigned build and verify it is rejected” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, release logs show no artifact promotion or security scan before a production deploy. The option “Monitor skipped gates, broken builds and rollout error budgets” instead addresses the requested ongoing operational assurance.

Question 341

International sports league plans to update video storage tiers. Investigators found that access report shows 94% of footage is only viewed once per year, consistent with the reported problem that all raw broadcasts remain in premium storage though almost never retrieved. The response must satisfy the requirement that rights owners require published clips to stay fast while raw footage is protected. The design review is over and production introduction is next. Which action is the best fit?

  1. Migrate aged objects after permission and retrieval-time validation
  2. Apply separate Cloud Storage lifecycle classes for streaming clips and cold originals
  3. Track storage-class mix, unexpected retrieval spend and policy exceptions
  4. Move the currently streaming clips into long-retrieval archives unconditionally

Explanation

Correct Answer

A:

Migrate aged objects after permission and retrieval-time validation is a controlled means to introduce the approved architecture while meeting the requirement that rights owners require published clips to stay fast while raw footage is protected. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.

Incorrect Answers

B:

The alternative “Apply separate Cloud Storage lifecycle classes for streaming clips and cold originals” describes the chosen design, but not how it is introduced safely. In the reported observation, access report shows 94% of footage is only viewed once per year. The option “Migrate aged objects after permission and retrieval-time validation” instead addresses the requested controlled implementation.

C:

The alternative “Track storage-class mix, unexpected retrieval spend and policy exceptions” addresses later monitoring rather than the actual controlled deployment. In the reported observation, access report shows 94% of footage is only viewed once per year. The option “Migrate aged objects after permission and retrieval-time validation” instead addresses the requested controlled implementation.

D:

Cold retrieval economics and latency do not fit hot video playback. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that rights owners require published clips to stay fast while raw footage is protected.

Question 342

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.

The global artifact web gallery environment at Regional museum faces this issue: public image delivery overloads the origin service on exhibit announcement days. Supporting evidence shows that traces show the same static media repeatedly retrieved by remote browsers. The architect must preserve the requirement that private curator uploads must remain restricted while published assets are cacheable. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?

  1. Validate authorized editor access and global image cache hit improvements
  2. Serve public assets through Cloud CDN while keeping private edit APIs uncached
  3. Cache authenticated curator endpoints for every visitor under a shared key
  4. Monitor cache invalidations, origin egress and signed-access errors

Explanation

Correct Answer

D:

Monitor cache invalidations, origin egress and signed-access errors reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (public image delivery overloads the origin service on exhibit announcement days) rather than treating the first successful test as permanent assurance.

Incorrect Answers

A:

The alternative “Validate authorized editor access and global image cache hit improvements” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, traces show the same static media repeatedly retrieved by remote browsers. The option “Monitor cache invalidations, origin egress and signed-access errors” instead addresses the requested ongoing operational assurance.

B:

The alternative “Serve public assets through Cloud CDN while keeping private edit APIs uncached” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, traces show the same static media repeatedly retrieved by remote browsers. The option “Monitor cache invalidations, origin egress and signed-access errors” instead addresses the requested ongoing operational assurance.

C:

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

Question 343

At Public library consortium, the digital borrowing portal workload has a documented risk: the proposed cloud rebuild treats video and catalog traffic as one workload. The review found that access logs show evening video bursts while catalog reservations require strict consistency. The architecture must also ensure that reserving a scarce book must never succeed twice. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?

  1. Cut over media browsing first and migrate reservations after replay and integrity testing
  2. Store the unique-book counter in a stale CDN cache as the system of record
  3. Separate catalog transaction SLOs from media delivery and licensing costs
  4. Choose strongly consistent reservation storage with cacheable media delivery isolated from checkout
  5. Watch reservation conflicts and streaming egress against allocated budgets

Explanation

Correct Answers

A:

Cut over media browsing first and migrate reservations after replay and integrity testing is a controlled means to introduce the approved architecture while meeting the requirement that reserving a scarce book must never succeed twice. 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.

D:

Choose strongly consistent reservation storage with cacheable media delivery isolated from checkout targets the underlying issue (the proposed cloud rebuild treats video and catalog traffic as one workload) rather than merely reporting symptoms. It also preserves the required outcome (reserving a scarce book must never succeed twice), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.

Incorrect Answers

B:

An edge cache cannot enforce atomic reservation updates. The shortcut does not supply the requested design and safe rollout for digital borrowing portal, where access logs show evening video bursts while catalog reservations require strict consistency.

C:

This diagnoses the original issue (the proposed cloud rebuild treats video and catalog traffic as one workload), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.

E:

Monitoring digital borrowing portal for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: the proposed cloud rebuild treats video and catalog traffic as one workload.

Question 344

At National telecommunications provider, the cloud quality-gate metrics workload has a documented risk: team approves new infrastructure because Terraform plan succeeded even though application SLO regressed. The review found that postrelease metrics show connection drops after a firewall change. The architecture must also ensure that subscriber sessions must retain a minimum availability target. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?

  1. Accept every infrastructure plan without service tests
  2. Define functional, security and SLO quality checks for infrastructure changes
  3. Identify acceptance criteria linking config, function and reliability
  4. Add quality checks to release pipeline with rollback criteria

Explanation

Correct Answer

C:

Identify acceptance criteria linking config, function and reliability is the appropriate diagnostic because the observation—postrelease metrics show connection drops after a firewall change—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (team approves new infrastructure because Terraform plan succeeded even though application SLO regressed) before the design is approved.

Incorrect Answers

A:

Successful resource creation does not prove adequate user outcomes. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that subscriber sessions must retain a minimum availability target.

B:

The alternative “Define functional, security and SLO quality checks for infrastructure changes” is target architecture selection; it does not establish why the observed path failed. In the reported observation, postrelease metrics show connection drops after a firewall change. The option “Identify acceptance criteria linking config, function and reliability” instead addresses the requested root-cause evidence.

D:

The alternative “Add quality checks to release pipeline with rollback criteria” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, postrelease metrics show connection drops after a firewall change. The option “Identify acceptance criteria linking config, function and reliability” instead addresses the requested root-cause evidence.

Question 345

At Retail airline reservations, the load-test realism workload has a documented risk: capacity tests generate simple GET requests but real transactions require multiple write steps. The review found that peak production incident shows locks on seat inventory despite low GET latency. The architecture must also ensure that holiday purchase flow must sustain transactional volume without overselling. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?

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

Explanation

Correct Answers

A:

Introduce production-like synthetic traffic safely before peak season is a controlled means to introduce the approved architecture while meeting the requirement that holiday purchase flow must sustain transactional volume without overselling. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption. This supplies the controlled-introduction half of the two-action package.

E:

Design capacity and admission control around realistic end-to-end flows targets the underlying issue (capacity tests generate simple GET requests but real transactions require multiple write steps) rather than merely reporting symptoms. It also preserves the required outcome (holiday purchase flow must sustain transactional volume without overselling), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.

Incorrect Answers

B:

Monitoring load-test realism for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: capacity tests generate simple GET requests but real transactions require multiple write steps.

C:

This diagnoses the original issue (capacity tests generate simple GET requests but real transactions require multiple write steps), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.

D:

Read-only performance does not establish transactional capacity. The shortcut does not supply the requested design and safe rollout for load-test realism, where peak production incident shows locks on seat inventory despite low GET latency.

Question 346

Case study: Regional maritime operator: shared VPC service projects

Regional maritime operator relies on shared VPC service projects to deliver its operational commitments. The current architectural problem is that each harbor app team creates duplicate subnets with conflicting ranges. The team has recorded this evidence: IPAM report shows two VPCs contain identical 10.40.0.0/16 networks. Any proposed response must preserve the requirement that network security must be owned centrally while applications manage their services.

At Regional maritime operator, the shared VPC service projects workload has a documented risk: each harbor app team creates duplicate subnets with conflicting ranges. The review found that IPAM report shows two VPCs contain identical 10.40.0.0/16 networks. The architecture must also ensure that network security must be owned centrally while applications manage their services. Which post-change test most reliably distinguishes a functioning control from a merely successful installation?

  1. Peer overlapping address spaces and assume routes propagate transitively
  2. Migrate one service project and adjust routes/firewalls with rollback
  3. Test least-privilege subnet use and communication without peering overlap
  4. Map overlapping allocations and separation of network and application roles

Explanation

Correct Answer

C:

Test least-privilege subnet use and communication without peering overlap is a direct acceptance test of the path implicated by IPAM report shows two VPCs contain identical 10.40.0.0/16 networks. It checks that the original risk (each harbor app team creates duplicate subnets with conflicting ranges) has actually been controlled and tests that permitted operations still meet the requirement that network security must be owned centrally while applications manage their services.

Incorrect Answers

A:

VPC peering does not solve overlapping ranges or provide arbitrary transitive routing. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that network security must be owned centrally while applications manage their services.

B:

The alternative “Migrate one service project and adjust routes/firewalls with rollback” documents change execution but not its operational acceptance result. In the reported observation, IPAM report shows two VPCs contain identical 10.40.0.0/16 networks. The option “Test least-privilege subnet use and communication without peering overlap” instead addresses the requested acceptance verification.

D:

The alternative “Map overlapping allocations and separation of network and application roles” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, IPAM report shows two VPCs contain identical 10.40.0.0/16 networks. The option “Test least-privilege subnet use and communication without peering overlap” instead addresses the requested acceptance verification.

Question 347

The checkout cost modernization environment at Multinational retailer faces this issue: a newly acquired brand will double country coverage and tax interfaces after migration. Supporting evidence shows that requirements show separate national tax authorities and holiday peak profiles. The architect must preserve the requirement that checkout must preserve local residency and transparent tax audit. Which migration or rollout step best manages risk, dependencies and reversibility?

  1. Use modular regional tax integration boundaries with portable checkout contracts
  2. Track change requests, country-level latency and tax-policy drift
  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

D:

Onboard one new country with shadow invoices and local compliance signoff is a controlled means to introduce the approved architecture while meeting the requirement that checkout must preserve local residency and transparent tax audit. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.

Incorrect Answers

A:

The alternative “Use modular regional tax integration boundaries with portable checkout contracts” describes the chosen design, but not how it is introduced safely. In the reported observation, requirements show separate national tax authorities and holiday peak profiles. The option “Onboard one new country with shadow invoices and local compliance signoff” instead addresses the requested controlled implementation.

B:

The alternative “Track change requests, country-level latency and tax-policy drift” addresses later monitoring rather than the actual controlled deployment. In the reported observation, requirements show separate national tax authorities and holiday peak profiles. The option “Onboard one new country with shadow invoices and local compliance signoff” instead addresses the requested controlled implementation.

C:

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

Question 348

The loan-origination approval service environment at Neighborhood banking cooperative faces this issue: the planned monolith migration promises lower costs but omits the regulatory audit and branch-outage requirements. Supporting evidence shows that business interviews reveal a four-hour branch outage limit and an immutable decision-history obligation. The architect must preserve the requirement that branches need approvals even when a regional WAN circuit fails. Before approving a solution, which analysis most directly clarifies the underlying dependency or control gap?

  1. Design a regional approval API with durable event logging and a tested local queue for temporary disconnection
  2. Migrate one branch at a time with reconciled event replay and rollback
  3. Map branch dependencies, decision-record retention and acceptable outage duration with risk owners
  4. Choose the cheapest single-zone VM and discard decision events once the API responds

Explanation

Correct Answer

C:

Map branch dependencies, decision-record retention and acceptable outage duration with risk owners is the appropriate diagnostic because the observation—business interviews reveal a four-hour branch outage limit and an immutable decision-history obligation—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (the planned monolith migration promises lower costs but omits the regulatory audit and branch-outage requirements) before the design is approved.

Incorrect Answers

A:

The alternative “Design a regional approval API with durable event logging and a tested local queue for temporary disconnection” is target architecture selection; it does not establish why the observed path failed. In the reported observation, business interviews reveal a four-hour branch outage limit and an immutable decision-history obligation. The option “Map branch dependencies, decision-record retention and acceptable outage duration with risk owners” instead addresses the requested root-cause evidence.

B:

The alternative “Migrate one branch at a time with reconciled event replay and rollback” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, business interviews reveal a four-hour branch outage limit and an immutable decision-history obligation. The option “Map branch dependencies, decision-record retention and acceptable outage duration with risk owners” instead addresses the requested root-cause evidence.

D:

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

Question 349

Case study: Public school admissions portal: release version safety

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

Public school admissions portal plans to update release version safety. Investigators found that incident shows new clients send unsupported enrollment fields, consistent with the reported problem that frontend rollout references a backend schema that is not yet deployed. The response must satisfy the requirement that admission forms cannot break during deadline week. The team needs an operations signal rather than another design or one-time test. What should it track?

  1. Run old and new frontend versions against the transitional schema
  2. Track 4xx schema errors and version skew
  3. Design backward-compatible API contracts and staged deployments
  4. Deploy breaking frontend and database schema simultaneously without canary

Explanation

Correct Answer

B:

Track 4xx schema errors and version skew reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (frontend rollout references a backend schema that is not yet deployed) rather than treating the first successful test as permanent assurance.

Incorrect Answers

A:

The alternative “Run old and new frontend versions against the transitional schema” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, incident shows new clients send unsupported enrollment fields. The option “Track 4xx schema errors and version skew” instead addresses the requested ongoing operational assurance.

C:

The alternative “Design backward-compatible API contracts and staged deployments” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, incident shows new clients send unsupported enrollment fields. The option “Track 4xx schema errors and version skew” instead addresses the requested ongoing operational assurance.

D:

A coupled big-bang change creates untested integration failures. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that admission forms cannot break during deadline week.

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.

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