Google Professional Cloud Architect Practice Test 62
Question 610
Case study: University HPC consortium: interruptible research training
University HPC consortium relies on interruptible research training to deliver its operational commitments. The current architectural problem is that lab runs preemptible VMs for long training without checkpoints and loses weeks of progress. The team has recorded this evidence: job logs show instances interrupted after capacity reclaim. Any proposed response must preserve the requirement that researcher budget is constrained but results must be reproducible.
Consider University HPC consortium and its interruptible research training workload. The issue is that lab runs preemptible VMs for long training without checkpoints and loses weeks of progress; the current observation is that job logs show instances interrupted after capacity reclaim. The team must ensure that researcher budget is constrained but results must be reproducible. Which continuous monitoring approach best reveals recurrence or changing dependencies?
- Use Spot VMs for restartable segments with durable checkpoints
- Interrupt a worker and compare resumed metrics with expected state
- Run the authoritative metadata database only on unreplicated Spot VMs
- Monitor preemption loss, checkpoint staleness and cost per experiment
Explanation
Correct Answer
D:
Monitor preemption loss, checkpoint staleness and cost per experiment reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (lab runs preemptible VMs for long training without checkpoints and loses weeks of progress) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Use Spot VMs for restartable segments with durable checkpoints” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, job logs show instances interrupted after capacity reclaim. The option “Monitor preemption loss, checkpoint staleness and cost per experiment” instead addresses the requested ongoing operational assurance.
B:
The alternative “Interrupt a worker and compare resumed metrics with expected state” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, job logs show instances interrupted after capacity reclaim. The option “Monitor preemption loss, checkpoint staleness and cost per experiment” instead addresses the requested ongoing operational assurance.
C:
The database cannot tolerate unmanaged interruption and state loss. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that researcher budget is constrained but results must be reproducible.
Question 611
Legal discovery cooperative plans to update regulated document holds. Investigators found that records show retention rules expire before litigation review completes, consistent with the reported problem that a scheduled lifecycle deletion overlaps a court-ordered legal hold. The response must satisfy the requirement that legal-hold protected files must not be removed by application writers. Which target-state design is best justified by the evidence and required business outcome?
- Review hold expirations, privileged overrides and lifecycle audit
- Inspect retention settings, hold authority and lifecycle job behavior
- Apply object holds and retention configurations that respect verified legal orders
- Grant all document uploaders permission to release legal holds
Explanation
Correct Answer
C:
Apply object holds and retention configurations that respect verified legal orders targets the underlying issue (a scheduled lifecycle deletion overlaps a court-ordered legal hold) rather than merely reporting symptoms. It also preserves the required outcome (legal-hold protected files must not be removed by application writers), which a target-state design must satisfy.
Incorrect Answers
A:
The alternative “Review hold expirations, privileged overrides and lifecycle audit” measures results without defining the preventive design now required. In the reported observation, records show retention rules expire before litigation review completes. The option “Apply object holds and retention configurations that respect verified legal orders” instead addresses the requested architecture selection.
B:
The alternative “Inspect retention settings, hold authority and lifecycle job behavior” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, records show retention rules expire before litigation review completes. The option “Apply object holds and retention configurations that respect verified legal orders” instead addresses the requested architecture selection.
D:
Uncontrolled release rights defeat binding preservation orders. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that legal-hold protected files must not be removed by application writers.
Question 612
The container rollout traceability environment at Industrial parts distributor faces this issue: multiple teams manually push the same mutable image tag between environments. Supporting evidence shows that deployment journal cannot identify which digest passed integration testing. The architect must preserve the requirement that production packages must have provable origin and approved owners. Which migration or rollout step best manages risk, dependencies and reversibility?
- Deploy the exact validated digest through staged environments
- Monitor unapproved digest changes and skipped attestation gates
- Use immutable Artifact Registry digests and attested release promotion
- Treat the latest tag string as immutable evidence of software identity
Explanation
Correct Answer
A:
Deploy the exact validated digest through staged environments is a controlled means to introduce the approved architecture while meeting the requirement that production packages must have provable origin and approved owners. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
The alternative “Monitor unapproved digest changes and skipped attestation gates” addresses later monitoring rather than the actual controlled deployment. In the reported observation, deployment journal cannot identify which digest passed integration testing. The option “Deploy the exact validated digest through staged environments” instead addresses the requested controlled implementation.
C:
The alternative “Use immutable Artifact Registry digests and attested release promotion” describes the chosen design, but not how it is introduced safely. In the reported observation, deployment journal cannot identify which digest passed integration testing. The option “Deploy the exact validated digest through staged environments” instead addresses the requested controlled implementation.
D:
A mutable tag does not establish release provenance. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that production packages must have provable origin and approved owners.
Question 613
Multinational auto-insurer plans to update third-party risk boundary. Investigators found that contract review shows its audit excludes the in-app analytics SDK, consistent with the reported problem that a data processor claims SOC 2 coverage for a separate custom mobile collection app. The response must satisfy the requirement that customer consent and app data handling require independent assessment. The approved change has been applied. Which validation provides the clearest evidence the original problem is fixed?
- Map coverage of supplier attestations versus app and SDK control ownership
- Roll out SDK controls under contractual and app store change review
- Verify sensitive fields cannot leave the app without required consent
- Treat the processor's SOC 2 report as certification of every unrelated mobile SDK
Explanation
Correct Answer
C:
Verify sensitive fields cannot leave the app without required consent is a direct acceptance test of the path implicated by contract review shows its audit excludes the in-app analytics SDK. It checks that the original risk (a data processor claims SOC 2 coverage for a separate custom mobile collection app) has actually been controlled and tests that permitted operations still meet the requirement that customer consent and app data handling require independent assessment.
Incorrect Answers
A:
The alternative “Map coverage of supplier attestations versus app and SDK control ownership” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, contract review shows its audit excludes the in-app analytics SDK. The option “Verify sensitive fields cannot leave the app without required consent” instead addresses the requested acceptance verification.
B:
The alternative “Roll out SDK controls under contractual and app store change review” documents change execution but not its operational acceptance result. In the reported observation, contract review shows its audit excludes the in-app analytics SDK. The option “Verify sensitive fields cannot leave the app without required consent” instead addresses the requested acceptance verification.
D:
Attestation scope cannot be extended to unexamined components. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that customer consent and app data handling require independent assessment.
Question 614
At Global language-learning company, the live audio lessons workload has a documented risk: users in two continents see 400ms voice round trips to the only application region. The review found that distributed probes isolate high WAN latency while codec processing is fast. The architecture must also ensure that lesson audio requires interactive latency and instructor privacy. The team must deliver the approved control safely. Which deployment sequence is most appropriate?
- Only increase CPU in the distant region
- Move cohorts gradually with traffic steering and compliant regional logging
- Distribute regional media ingress and place user sessions close to participants
- Monitor packet loss, jitter, quality scores and egress charges
Explanation
Correct Answer
B:
Move cohorts gradually with traffic steering and compliant regional logging is a controlled means to introduce the approved architecture while meeting the requirement that lesson audio requires interactive latency and instructor privacy. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
Extra CPU cannot remove long-haul network propagation delay. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that lesson audio requires interactive latency and instructor privacy.
C:
The alternative “Distribute regional media ingress and place user sessions close to participants” describes the chosen design, but not how it is introduced safely. In the reported observation, distributed probes isolate high WAN latency while codec processing is fast. The option “Move cohorts gradually with traffic steering and compliant regional logging” instead addresses the requested controlled implementation.
D:
The alternative “Monitor packet loss, jitter, quality scores and egress charges” addresses later monitoring rather than the actual controlled deployment. In the reported observation, distributed probes isolate high WAN latency while codec processing is fast. The option “Move cohorts gradually with traffic steering and compliant regional logging” instead addresses the requested controlled implementation.
Question 615
Consider Regional financial adviser and its private research assistant workload. The issue is that employees want document-grounded answers without granting a chatbot access to privileged trading APIs; the current observation is that demo agent follows instructions embedded in retrieved research PDFs. The team must ensure that approved internal reports must be cited and trading authorization separate. Which continuous monitoring approach best reveals recurrence or changing dependencies?
- Watch tool-denial logs, citation fidelity and document-access grants
- Treat every retrieved document as an instruction from the security administrator
- Ground answers in vetted enterprise search and isolate actions behind explicit identity checks
- Inject malicious retrieved instructions and verify no trading call executes
Explanation
Correct Answer
A:
Watch tool-denial logs, citation fidelity and document-access grants reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (employees want document-grounded answers without granting a chatbot access to privileged trading APIs) rather than treating the first successful test as permanent assurance.
Incorrect Answers
B:
Untrusted document content cannot grant privileged tool authority. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that approved internal reports must be cited and trading authorization separate.
C:
The alternative “Ground answers in vetted enterprise search and isolate actions behind explicit identity checks” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, demo agent follows instructions embedded in retrieved research PDFs. The option “Watch tool-denial logs, citation fidelity and document-access grants” instead addresses the requested ongoing operational assurance.
D:
The alternative “Inject malicious retrieved instructions and verify no trading call executes” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, demo agent follows instructions embedded in retrieved research PDFs. The option “Watch tool-denial logs, citation fidelity and document-access grants” instead addresses the requested ongoing operational assurance.
Question 616
At Municipal parking authority, the legacy Oracle billing workload has a documented risk: a tightly coupled database license cannot run cost-effectively in a naive VM lift-and-shift. The review found that license assessment shows processor-based fees exceed projected cloud infrastructure savings. The architecture must also ensure that metered invoices must reconcile across cutover. What follow-up metric or alert will identify emerging failures after the initial acceptance test?
- Select a phased database disposition using compatibility and total cost, not VM price alone
- Monitor license exposure, query regressions and reconciliation failures
- Reconcile tax calculation, invoice IDs and payment postings before decommission
- Ignore license rights because compute is billed hourly
Explanation
Correct Answer
B:
Monitor license exposure, query regressions and reconciliation failures reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a tightly coupled database license cannot run cost-effectively in a naive VM lift-and-shift) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Select a phased database disposition using compatibility and total cost, not VM price alone” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, license assessment shows processor-based fees exceed projected cloud infrastructure savings. The option “Monitor license exposure, query regressions and reconciliation failures” instead addresses the requested ongoing operational assurance.
C:
The alternative “Reconcile tax calculation, invoice IDs and payment postings before decommission” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, license assessment shows processor-based fees exceed projected cloud infrastructure savings. The option “Monitor license exposure, query regressions and reconciliation failures” instead addresses the requested ongoing operational assurance.
D:
Cloud billing does not nullify software licensing obligations. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that metered invoices must reconcile across cutover.
Question 617
At Public sports streaming provider, the Cloud Monitoring latency alert workload has a documented risk: the team alerts on average latency while p99 playback start delays exceed 20 seconds. The review found that histogram shows rare severe stalls hidden by low median. The architecture must also ensure that users need a low tail-latency start experience. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Roll out new alert thresholds in shadow mode with owner acknowledgement
- Alert only when average latency crosses a broad threshold
- Analyze histogram tails, percentiles, demand cohorts and SLO impact
- Define percentile-based latency SLO and burn-rate alert policy
Explanation
Correct Answer
C:
Analyze histogram tails, percentiles, demand cohorts and SLO impact is the appropriate diagnostic because the observation—histogram shows rare severe stalls hidden by low median—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (the team alerts on average latency while p99 playback start delays exceed 20 seconds) before the design is approved.
Incorrect Answers
A:
The alternative “Roll out new alert thresholds in shadow mode with owner acknowledgement” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, histogram shows rare severe stalls hidden by low median. The option “Analyze histogram tails, percentiles, demand cohorts and SLO impact” instead addresses the requested root-cause evidence.
B:
An average hides a small but severely affected user cohort. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that users need a low tail-latency start experience.
D:
The alternative “Define percentile-based latency SLO and burn-rate alert policy” is target architecture selection; it does not establish why the observed path failed. In the reported observation, histogram shows rare severe stalls hidden by low median. The option “Analyze histogram tails, percentiles, demand cohorts and SLO impact” instead addresses the requested root-cause evidence.
Question 618
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.
The shared VPC service projects environment at Regional maritime operator faces this issue: each harbor app team creates duplicate subnets with conflicting ranges. Supporting evidence shows that IPAM report shows two VPCs contain identical 10.40.0.0/16 networks. The architect must preserve the requirement that network security must be owned centrally while applications manage their services. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Track IP utilization, unauthorized routes and service-project changes
- Peer overlapping address spaces and assume routes propagate transitively
- Test least-privilege subnet use and communication without peering overlap
- Use a centrally administered Shared VPC host with nonoverlapping subnets and delegated attachment
Explanation
Correct Answer
A:
Track IP utilization, unauthorized routes and service-project changes reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (each harbor app team creates duplicate subnets with conflicting ranges) rather than treating the first successful test as permanent assurance.
Incorrect Answers
B:
VPC peering does not solve overlapping ranges or provide arbitrary transitive routing. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that network security must be owned centrally while applications manage their services.
C:
The alternative “Test least-privilege subnet use and communication without peering overlap” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, IPAM report shows two VPCs contain identical 10.40.0.0/16 networks. The option “Track IP utilization, unauthorized routes and service-project changes” instead addresses the requested ongoing operational assurance.
D:
The alternative “Use a centrally administered Shared VPC host with nonoverlapping subnets and delegated attachment” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, IPAM report shows two VPCs contain identical 10.40.0.0/16 networks. The option “Track IP utilization, unauthorized routes and service-project changes” instead addresses the requested ongoing operational assurance.
Question 619
Case study: Industrial distributor: interwarehouse shipment events
Industrial distributor relies on interwarehouse shipment events to deliver its operational commitments. The current architectural problem is that orders must trigger independent finance and warehouse actions without a central polling table. The team has recorded this evidence: architecture diagram shows tight synchronous calls to five downstream services. Any proposed response must preserve the requirement that an outage in accounting must not block physical pick requests.
The interwarehouse shipment events environment at Industrial distributor faces this issue: orders must trigger independent finance and warehouse actions without a central polling table. Supporting evidence shows that architecture diagram shows tight synchronous calls to five downstream services. The architect must preserve the requirement that an outage in accounting must not block physical pick requests. What test must pass before the business accepts the remediated architecture?
- Introduce an outbox and migrate one downstream consumer at a time
- Disconnect accounting and verify warehouse consumers continue and replay later
- Have warehouse service synchronously call every downstream system before confirming an order
- Identify event ownership, delivery guarantees and independent consumer SLOs
Explanation
Correct Answer
B:
Disconnect accounting and verify warehouse consumers continue and replay later is a direct acceptance test of the path implicated by architecture diagram shows tight synchronous calls to five downstream services. It checks that the original risk (orders must trigger independent finance and warehouse actions without a central polling table) has actually been controlled and tests that permitted operations still meet the requirement that an outage in accounting must not block physical pick requests.
Incorrect Answers
A:
The alternative “Introduce an outbox and migrate one downstream consumer at a time” documents change execution but not its operational acceptance result. In the reported observation, architecture diagram shows tight synchronous calls to five downstream services. The option “Disconnect accounting and verify warehouse consumers continue and replay later” instead addresses the requested acceptance verification.
C:
Synchronous fanout propagates a slow consumer into order failures. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that an outage in accounting must not block physical pick requests.
D:
The alternative “Identify event ownership, delivery guarantees and independent consumer SLOs” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, architecture diagram shows tight synchronous calls to five downstream services. The option “Disconnect accounting and verify warehouse consumers continue and replay later” instead addresses the requested acceptance verification.
Question 620
National energy balancing platform plans to update regional failure rehearsal. Investigators found that chaos rehearsal shows all dispatch messages stop when broker restarts, consistent with the reported problem that a multi-zone app still relies on a single regional message broker. The response must satisfy the requirement that grid dispatch must recover within a documented time objective. The team needs an operations signal rather than another design or one-time test. What should it track?
- Fail the active broker and measure dispatch message recovery and duplication
- Add more web replicas while retaining the unreplicated broker
- Monitor lag, broker health and RTO breaches
- Design redundant durable messaging with proper consumer reconciliation
Explanation
Correct Answer
C:
Monitor lag, broker health and RTO breaches reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a multi-zone app still relies on a single regional message broker) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Fail the active broker and measure dispatch message recovery and duplication” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, chaos rehearsal shows all dispatch messages stop when broker restarts. The option “Monitor lag, broker health and RTO breaches” instead addresses the requested ongoing operational assurance.
B:
Web redundancy cannot compensate for a single broker dependency. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that grid dispatch must recover within a documented time objective.
D:
The alternative “Design redundant durable messaging with proper consumer reconciliation” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, chaos rehearsal shows all dispatch messages stop when broker restarts. The option “Monitor lag, broker health and RTO breaches” instead addresses the requested ongoing operational assurance.