Google Professional Cloud Architect Practice Test 34
Question 330
E-commerce promotion service plans to update Cloud Run database connection storms. Investigators found that database logs show connection refusals at promotion launch, consistent with the reported problem that a serverless revision scales quickly and exhausts a legacy SQL server's connection pool. The response must satisfy the requirement that backend must remain within database concurrency limits. The design review is over and production introduction is next. Which action is the best fit?
- Stage maximum-instance limits and traffic splitting before peak events
- Allow unlimited cold-start instances to open independent large pools
- Set Cloud Run concurrency and instance limits with appropriate pooling
- Track rejected requests, instance count and DB pool utilization
Explanation
Correct Answer
A:
Stage maximum-instance limits and traffic splitting before peak events is a controlled means to introduce the approved architecture while meeting the requirement that backend must remain within database concurrency limits. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
Unbounded scaling overwhelms a fixed database dependency. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that backend must remain within database concurrency limits.
C:
The alternative “Set Cloud Run concurrency and instance limits with appropriate pooling” describes the chosen design, but not how it is introduced safely. In the reported observation, database logs show connection refusals at promotion launch. The option “Stage maximum-instance limits and traffic splitting before peak events” instead addresses the requested controlled implementation.
D:
The alternative “Track rejected requests, instance count and DB pool utilization” addresses later monitoring rather than the actual controlled deployment. In the reported observation, database logs show connection refusals at promotion launch. The option “Stage maximum-instance limits and traffic splitting before peak events” instead addresses the requested controlled implementation.
Question 331
At Wildlife conservation nonprofit, the Google Cloud design for field-research collection is affected because donor funding requires an inexpensive platform but volunteers collect sensitive species locations. A review found that team interviews identify intermittent connectivity and controlled-location access. The proposed response must account for the requirement that precise nesting coordinates must remain inaccessible to public donors. Which controlled implementation should be used to preserve operational continuity during the change?
- Use offline-capable mobile capture with encrypted private storage and aggregated donor reports
- Pilot one field team with conflict-aware synchronization and revocable researcher identities
- Publish exact endangered-species coordinates to prove collection completeness
- Watch stale devices, data-sharing grants and synchronization conflicts
Explanation
Correct Answer
B:
Pilot one field team with conflict-aware synchronization and revocable researcher identities is a controlled means to introduce the approved architecture while meeting the requirement that precise nesting coordinates must remain inaccessible to public donors. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Use offline-capable mobile capture with encrypted private storage and aggregated donor reports” describes the chosen design, but not how it is introduced safely. In the reported observation, team interviews identify intermittent connectivity and controlled-location access. The option “Pilot one field team with conflict-aware synchronization and revocable researcher identities” instead addresses the requested controlled implementation.
C:
Sensitive location disclosure could enable poaching and defeat privacy requirements. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that precise nesting coordinates must remain inaccessible to public donors.
D:
The alternative “Watch stale devices, data-sharing grants and synchronization conflicts” addresses later monitoring rather than the actual controlled deployment. In the reported observation, team interviews identify intermittent connectivity and controlled-location access. The option “Pilot one field team with conflict-aware synchronization and revocable researcher identities” instead addresses the requested controlled implementation.
Question 332
University astronomy project plans to update temporary sky-image processing. Investigators found that cost report shows accelerator nodes idle more than ninety percent of the time, consistent with the reported problem that large image batch runs only one weekend a month yet reserved VMs are always on. The response must satisfy the requirement that scientific jobs can checkpoint and resume after interruption. 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?
- Exclude the affected dependency from all future tests and incident metrics to simplify reporting
- Assess preemption tolerance, GPU sizing and checkpoint intervals
- Interrupt workers deliberately and verify reproducible processed outputs
- Use spot capacity for the only stateful database with no recovery strategy
- Use job orchestration with Spot VMs for interruptible batch computation
- Track GPU idle hours, interruption rates and batch cost
Explanation
Correct Answers
B:
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. It supplies the pre-design diagnostic evidence requested.
C:
Interrupt workers deliberately and verify reproducible processed outputs is a direct acceptance test of the path implicated by cost report shows accelerator nodes idle more than ninety percent of the time. It checks that the original risk (large image batch runs only one weekend a month yet reserved VMs are always on) has actually been controlled and tests that permitted operations still meet the requirement that scientific jobs can checkpoint and resume after interruption. It supplies the separate post-change acceptance result requested.
F:
Track GPU idle hours, interruption rates and batch cost reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (large image batch runs only one weekend a month yet reserved VMs are always on) rather than treating the first successful test as permanent assurance. It supplies the ongoing observation requested.
Incorrect Answers
A:
Omitting the relevant dependency from testing and monitoring would hide, not correct, recurrence of the failure. In particular, the observed issue was: cost report shows accelerator nodes idle more than ninety percent of the time.
D:
Preemptible nodes are unsuitable as unprotected authoritative state. It cannot satisfy the required evidence stages.
E:
Designing temporary sky-image processing addresses the root cause, but this specific three-part question asks for evidence to diagnose, accept and continuously verify the response to large image batch runs only one weekend a month yet reserved VMs are always on, not another design proposal.
Question 333
Case study: Regional agricultural university: data quality acceptance
Regional agricultural university relies on data quality acceptance to deliver its operational commitments. The current architectural problem is that new analytics pipeline yields numbers that differ from its legacy data warehouse. The team has recorded this evidence: comparison shows altered time-zone grouping around daylight-saving change. Any proposed response must preserve the requirement that published crop reports require correct monthly accounting periods.
At Regional agricultural university, the Google Cloud design for data quality acceptance is affected because new analytics pipeline yields numbers that differ from its legacy data warehouse. A review found that comparison shows altered time-zone grouping around daylight-saving change. The proposed response must account for the requirement that published crop reports require correct monthly accounting periods. A deployment ticket has been closed. What direct evidence would justify solution signoff?
- Replay daylight-saving boundary records and compare approved output totals
- Treat query completion with no SQL errors as proof every aggregate is correct
- Analyze timestamp semantics, join keys and expected report totals
- Roll out quality gates for pipeline partitions with monitored backfill
Explanation
Correct Answer
A:
Replay daylight-saving boundary records and compare approved output totals is a direct acceptance test of the path implicated by comparison shows altered time-zone grouping around daylight-saving change. It checks that the original risk (new analytics pipeline yields numbers that differ from its legacy data warehouse) has actually been controlled and tests that permitted operations still meet the requirement that published crop reports require correct monthly accounting periods.
Incorrect Answers
B:
A syntactically valid query may still group the wrong time periods. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that published crop reports require correct monthly accounting periods.
C:
The alternative “Analyze timestamp semantics, join keys and expected report totals” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, comparison shows altered time-zone grouping around daylight-saving change. The option “Replay daylight-saving boundary records and compare approved output totals” instead addresses the requested acceptance verification.
D:
The alternative “Roll out quality gates for pipeline partitions with monitored backfill” documents change execution but not its operational acceptance result. In the reported observation, comparison shows altered time-zone grouping around daylight-saving change. The option “Replay daylight-saving boundary records and compare approved output totals” instead addresses the requested acceptance verification.
Question 334
Case study: Regional sports venue: deploy-time traffic splitting
Regional sports venue relies on deploy-time traffic splitting to deliver its operational commitments. The current architectural problem is that teams replace a full production service revision in one step before stadium events. The team has recorded this evidence: last release caused 15 minutes of checkout errors during a full swap. Any proposed response must preserve the requirement that ticket scanning must stay available throughout peak admission.
Regional sports venue plans to update deploy-time traffic splitting. Investigators found that last release caused 15 minutes of checkout errors during a full swap, consistent with the reported problem that teams replace a full production service revision in one step before stadium events. The response must satisfy the requirement that ticket scanning must stay available throughout peak admission. The team needs an operations signal rather than another design or one-time test. What should it track?
- Use a full instantaneous replace for every release and observe failures afterward
- Send realistic admission traffic through both versions and verify stability
- Design progressive canary or blue-green release with measurable safety gates
- Watch conversion errors, latency and rollback triggers
Explanation
Correct Answer
D:
Watch conversion errors, latency and rollback triggers reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (teams replace a full production service revision in one step before stadium events) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
A big-bang change concentrates customer impact. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that ticket scanning must stay available throughout peak admission.
B:
The alternative “Send realistic admission traffic through both versions and verify stability” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, last release caused 15 minutes of checkout errors during a full swap. The option “Watch conversion errors, latency and rollback triggers” instead addresses the requested ongoing operational assurance.
C:
The alternative “Design progressive canary or blue-green release with measurable safety gates” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, last release caused 15 minutes of checkout errors during a full swap. The option “Watch conversion errors, latency and rollback triggers” instead addresses the requested ongoing operational assurance.
Question 335
At National delivery marketplace, the Compute Engine API autoscaling workload has a documented risk: a regional instance group has only one VM with no health-based replacement. The review found that zone-outage test stops all public shipment status queries. The architecture must also ensure that shipment tracking needs zone-resilient read service. The team must deliver the approved control safely. Which deployment sequence is most appropriate?
- Roll out an immutable instance template with rolling replacement gates
- Rely on a single large zonal VM with manual restart instructions
- Monitor healthy instance counts, autoscale triggers and rollbacks
- Use a regional managed instance group behind appropriate load balancing
Explanation
Correct Answer
A:
Roll out an immutable instance template with rolling replacement gates is a controlled means to introduce the approved architecture while meeting the requirement that shipment tracking needs zone-resilient read service. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
One oversized VM remains a zonal single point of failure. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that shipment tracking needs zone-resilient read service.
C:
The alternative “Monitor healthy instance counts, autoscale triggers and rollbacks” addresses later monitoring rather than the actual controlled deployment. In the reported observation, zone-outage test stops all public shipment status queries. The option “Roll out an immutable instance template with rolling replacement gates” instead addresses the requested controlled implementation.
D:
The alternative “Use a regional managed instance group behind appropriate load balancing” describes the chosen design, but not how it is introduced safely. In the reported observation, zone-outage test stops all public shipment status queries. The option “Roll out an immutable instance template with rolling replacement gates” instead addresses the requested controlled implementation.
Question 336
Consider Local telecom provider and its VMware-based customer management workload. The issue is that team wants to migrate hundreds of VMware virtual machines with almost no application changes; the current observation is that migration inventory shows tight network coupling and unsupported guest customization. The team must ensure that a contract requires a one-year low-risk transitional hosting period. Which continuous monitoring approach best reveals recurrence or changing dependencies?
- Consider Google Cloud VMware Engine for compatible transitional virtualization
- Verify application behavior, license constraints and VM restore on target
- Delete the existing hypervisor configurations before verifying guest compatibility
- Review transitional cost and per-app refactor/decommission roadmap
Explanation
Correct Answer
D:
Review transitional cost and per-app refactor/decommission roadmap reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (team wants to migrate hundreds of VMware virtual machines with almost no application changes) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Consider Google Cloud VMware Engine for compatible transitional virtualization” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, migration inventory shows tight network coupling and unsupported guest customization. The option “Review transitional cost and per-app refactor/decommission roadmap” instead addresses the requested ongoing operational assurance.
B:
The alternative “Verify application behavior, license constraints and VM restore on target” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, migration inventory shows tight network coupling and unsupported guest customization. The option “Review transitional cost and per-app refactor/decommission roadmap” instead addresses the requested ongoing operational assurance.
C:
Unplanned transformation creates unacceptable migration risk. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that a contract requires a one-year low-risk transitional hosting period.
Question 337
The external identity service onboarding environment at National digital identification office faces this issue: a public API rollout lacks per-agency token audience enforcement. Supporting evidence shows that test shows an agency credential can call unrelated record endpoints. The architect must preserve the requirement that agency access must be least privilege and auditable. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Use audience-scoped tokens and appropriate API authorization checks
- Track token audience drift and unauthorized API attempts
- Try a wrong-audience token and verify no record access
- Allow any signed token from any agency to read all records
Explanation
Correct Answer
B:
Track token audience drift and unauthorized API attempts reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a public API rollout lacks per-agency token audience enforcement) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Use audience-scoped tokens and appropriate API authorization checks” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, test shows an agency credential can call unrelated record endpoints. The option “Track token audience drift and unauthorized API attempts” instead addresses the requested ongoing operational assurance.
C:
The alternative “Try a wrong-audience token and verify no record access” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, test shows an agency credential can call unrelated record endpoints. The option “Track token audience drift and unauthorized API attempts” instead addresses the requested ongoing operational assurance.
D:
Signature validity does not grant access to unrelated applications. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that agency access must be least privilege and auditable.
Question 338
Case study: Telehealth teleconsultation: regulated regional failover
Telehealth teleconsultation relies on regulated regional failover to deliver its operational commitments. The current architectural problem is that the recovery design sends patient consultations to a region forbidden by local processing rules. The team has recorded this evidence: failover plan lists a default backup service on another continent. Any proposed response must preserve the requirement that clinical service must be recoverable inside approved national boundaries.
Telehealth teleconsultation plans to update regulated regional failover. Investigators found that failover plan lists a default backup service on another continent, consistent with the reported problem that the recovery design sends patient consultations to a region forbidden by local processing rules. The response must satisfy the requirement that clinical service must be recoverable inside approved national boundaries. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?
- Assume a foreign backup region is always allowed during emergencies
- Design in-country redundant service and storage with compliant backup
- Review legal location rules and failover data-plane traffic
- Stage a local region failover drill and update runbooks
Explanation
Correct Answer
C:
Review legal location rules and failover data-plane traffic is the appropriate diagnostic because the observation—failover plan lists a default backup service on another continent—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (the recovery design sends patient consultations to a region forbidden by local processing rules) before the design is approved.
Incorrect Answers
A:
Emergency operations do not automatically waive data residency laws. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that clinical service must be recoverable inside approved national boundaries.
B:
The alternative “Design in-country redundant service and storage with compliant backup” is target architecture selection; it does not establish why the observed path failed. In the reported observation, failover plan lists a default backup service on another continent. The option “Review legal location rules and failover data-plane traffic” instead addresses the requested root-cause evidence.
D:
The alternative “Stage a local region failover drill and update runbooks” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, failover plan lists a default backup service on another continent. The option “Review legal location rules and failover data-plane traffic” instead addresses the requested root-cause evidence.
Question 339
Case study: Streaming fitness platform: event analytics ingestion
Streaming fitness platform relies on event analytics ingestion to deliver its operational commitments. The current architectural problem is that incoming device events arrive late and in duplicates and dashboards need windows. The team has recorded this evidence: sample payloads show device clocks skew ten minutes across regions. Any proposed response must preserve the requirement that analytics should not interfere with real-time device safety controls.
The event analytics ingestion environment at Streaming fitness platform faces this issue: incoming device events arrive late and in duplicates and dashboards need windows. Supporting evidence shows that sample payloads show device clocks skew ten minutes across regions. The architect must preserve the requirement that analytics should not interfere with real-time device safety controls. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Monitor watermark lag, discarded events and slot spending
- Use request arrival timestamps as ground truth without clock handling
- Inject late and duplicate device events and check window aggregates
- Use Pub/Sub with Dataflow event-time processing and BigQuery analytics sinks
Explanation
Correct Answer
A:
Monitor watermark lag, discarded events and slot spending reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (incoming device events arrive late and in duplicates and dashboards need windows) rather than treating the first successful test as permanent assurance.
Incorrect Answers
B:
Arrival time alone distorts late-event analytics. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that analytics should not interfere with real-time device safety controls.
C:
The alternative “Inject late and duplicate device events and check window aggregates” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, sample payloads show device clocks skew ten minutes across regions. The option “Monitor watermark lag, discarded events and slot spending” instead addresses the requested ongoing operational assurance.
D:
The alternative “Use Pub/Sub with Dataflow event-time processing and BigQuery analytics sinks” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, sample payloads show device clocks skew ten minutes across regions. The option “Monitor watermark lag, discarded events and slot spending” instead addresses the requested ongoing operational assurance.
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?
- Allow every developer to deploy from a mutable local image tag
- Design gated CI/CD with immutable artifacts, tests, policy checks and deploy approvals
- Monitor skipped gates, broken builds and rollout error budgets
- 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.