Google Professional Cloud Architect Practice Test 42
Question 410
Case study: Cross-border payment provider: regulated retention policy
Cross-border payment provider relies on regulated retention policy to deliver its operational commitments. The current architectural problem is that cloud backups are replicated globally without legal review of data-residency restrictions. The team has recorded this evidence: compliance assessment finds a bucket's secondary location is outside allowed jurisdiction. Any proposed response must preserve the requirement that cardholder data must remain only in approved processing geography.
Cross-border payment provider plans to update regulated retention policy. Investigators found that compliance assessment finds a bucket's secondary location is outside allowed jurisdiction, consistent with the reported problem that cloud backups are replicated globally without legal review of data-residency restrictions. The response must satisfy the requirement that cardholder data must remain only in approved processing geography. Which target-state design is best justified by the evidence and required business outcome?
- Store the most sensitive copies in any multi-region regardless of its constituent locations
- Identify all replica and restore locations, policy controls and legal owners
- Use region-restricted storage, key policies and authenticated retention records
- Review location-policy changes, recovery tests and retention deviations
Explanation
Correct Answer
C:
Use region-restricted storage, key policies and authenticated retention records targets the underlying issue (cloud backups are replicated globally without legal review of data-residency restrictions) rather than merely reporting symptoms. It also preserves the required outcome (cardholder data must remain only in approved processing geography), which a target-state design must satisfy.
Incorrect Answers
A:
A global location can violate specific geographic transfer restrictions. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that cardholder data must remain only in approved processing geography.
B:
The alternative “Identify all replica and restore locations, policy controls and legal owners” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, compliance assessment finds a bucket's secondary location is outside allowed jurisdiction. The option “Use region-restricted storage, key policies and authenticated retention records” instead addresses the requested architecture selection.
D:
The alternative “Review location-policy changes, recovery tests and retention deviations” measures results without defining the preventive design now required. In the reported observation, compliance assessment finds a bucket's secondary location is outside allowed jurisdiction. The option “Use region-restricted storage, key policies and authenticated retention records” instead addresses the requested architecture selection.
Question 411
The Windows compatibility hosting environment at Vehicle warranty analytics company faces this issue: a proprietary claims executable needs Windows COM objects not supported in Linux containers. Supporting evidence shows that vendor test fails on Linux libraries despite unchanged program behavior. The architect must preserve the requirement that temporary hosting must keep vendor support and monthly patch controls. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Run the COM-dependent workflow and verify monthly patch recovery
- Repackage the unchanged Windows binary into an Alpine Linux container
- Choose Compute Engine Windows instances for an interim supported host
- Track Windows image age, license use and support deadlines
Explanation
Correct Answer
D:
Track Windows image age, license use and support deadlines reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a proprietary claims executable needs Windows COM objects not supported in Linux containers) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Run the COM-dependent workflow and verify monthly patch recovery” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, vendor test fails on Linux libraries despite unchanged program behavior. The option “Track Windows image age, license use and support deadlines” instead addresses the requested ongoing operational assurance.
B:
Repackaging does not remove Windows-only executable dependencies. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that temporary hosting must keep vendor support and monthly patch controls.
C:
The alternative “Choose Compute Engine Windows instances for an interim supported host” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, vendor test fails on Linux libraries despite unchanged program behavior. The option “Track Windows image age, license use and support deadlines” instead addresses the requested ongoing operational assurance.
Question 412
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.
Consider Regional agricultural university and its data quality acceptance workload. The issue is that new analytics pipeline yields numbers that differ from its legacy data warehouse; the current observation is that comparison shows altered time-zone grouping around daylight-saving change. The team must ensure that published crop reports require correct monthly accounting periods. The target architecture is approved; execution without disruption is the remaining decision. Which rollout action is best?
- Roll out quality gates for pipeline partitions with monitored backfill
- Treat query completion with no SQL errors as proof every aggregate is correct
- Watch late-arriving data, schema drift and quality-rule exceptions
- Set explicit temporal normalization and documented data quality invariants
Explanation
Correct Answer
A:
Roll out quality gates for pipeline partitions with monitored backfill is a controlled means to introduce the approved architecture while meeting the requirement that published crop reports require correct monthly accounting periods. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
A syntactically valid query may still group the wrong time periods. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that published crop reports require correct monthly accounting periods.
C:
The alternative “Watch late-arriving data, schema drift and quality-rule exceptions” addresses later monitoring rather than the actual controlled deployment. In the reported observation, comparison shows altered time-zone grouping around daylight-saving change. The option “Roll out quality gates for pipeline partitions with monitored backfill” instead addresses the requested controlled implementation.
D:
The alternative “Set explicit temporal normalization and documented data quality invariants” describes the chosen design, but not how it is introduced safely. In the reported observation, comparison shows altered time-zone grouping around daylight-saving change. The option “Roll out quality gates for pipeline partitions with monitored backfill” instead addresses the requested controlled implementation.
Question 413
International digital learning network plans to update Cloud Trace bottleneck. Investigators found that trace spans reveal sequential requests to a distant analytics service, consistent with the reported problem that users see slow lesson page load but service-level metrics show each component as healthy. The response must satisfy the requirement that lesson pages must remain responsive if nonessential analytics pauses. The team needs an operations signal rather than another design or one-time test. What should it track?
- Move optional analytics off the synchronous critical path with trace instrumentation
- Increase every VM size without checking span-level critical path
- Induce slow analytics and verify lesson latency remains within target
- Watch trace critical-path latency and queued analytics backlog
Explanation
Correct Answer
D:
Watch trace critical-path latency and queued analytics backlog reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (users see slow lesson page load but service-level metrics show each component as healthy) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Move optional analytics off the synchronous critical path with trace instrumentation” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, trace spans reveal sequential requests to a distant analytics service. The option “Watch trace critical-path latency and queued analytics backlog” instead addresses the requested ongoing operational assurance.
B:
Generic scaling need not solve avoidable synchronous waiting. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that lesson pages must remain responsive if nonessential analytics pauses.
C:
The alternative “Induce slow analytics and verify lesson latency remains within target” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, trace spans reveal sequential requests to a distant analytics service. The option “Watch trace critical-path latency and queued analytics backlog” instead addresses the requested ongoing operational assurance.
Question 414
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.
The interruptible research training environment at University HPC consortium faces this issue: lab runs preemptible VMs for long training without checkpoints and loses weeks of progress. Supporting evidence shows that job logs show instances interrupted after capacity reclaim. The architect must preserve the requirement that researcher budget is constrained but results must be reproducible. Which migration or rollout step best manages risk, dependencies and reversibility?
- Run the authoritative metadata database only on unreplicated Spot VMs
- Deploy workflow retries and checkpoint recovery in a controlled subset
- Use Spot VMs for restartable segments with durable checkpoints
- Monitor preemption loss, checkpoint staleness and cost per experiment
Explanation
Correct Answer
B:
Deploy workflow retries and checkpoint recovery in a controlled subset is a controlled means to introduce the approved architecture while meeting the requirement that researcher budget is constrained but results must be reproducible. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The database cannot tolerate unmanaged interruption and state loss. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that researcher budget is constrained but results must be reproducible.
C:
The alternative “Use Spot VMs for restartable segments with durable checkpoints” describes the chosen design, but not how it is introduced safely. In the reported observation, job logs show instances interrupted after capacity reclaim. The option “Deploy workflow retries and checkpoint recovery in a controlled subset” instead addresses the requested controlled implementation.
D:
The alternative “Monitor preemption loss, checkpoint staleness and cost per experiment” addresses later monitoring rather than the actual controlled deployment. In the reported observation, job logs show instances interrupted after capacity reclaim. The option “Deploy workflow retries and checkpoint recovery in a controlled subset” instead addresses the requested controlled implementation.
Question 415
Consider Clinical imaging archive and its large immutable scans workload. The issue is that imaging staff need object retention but architects chose a file share for infrequently accessed studies; the current observation is that inventory shows petabytes of immutable DICOM objects with annual reads. The team must ensure that specific clinical records have mandatory retention and legal hold. The team has completed discovery. Which preventive or corrective architecture is most appropriate?
- Monitor lifecycle transitions, retention exceptions and retrieval charges
- Use Cloud Storage with appropriate storage classes and retention policies for immutable objects
- Use only an ephemeral instance boot disk for the master archive
- Review object access, retrieval latency and regulated retention classes
Explanation
Correct Answer
B:
Use Cloud Storage with appropriate storage classes and retention policies for immutable objects targets the underlying issue (imaging staff need object retention but architects chose a file share for infrequently accessed studies) rather than merely reporting symptoms. It also preserves the required outcome (specific clinical records have mandatory retention and legal hold), which a target-state design must satisfy.
Incorrect Answers
A:
The alternative “Monitor lifecycle transitions, retention exceptions and retrieval charges” measures results without defining the preventive design now required. In the reported observation, inventory shows petabytes of immutable DICOM objects with annual reads. The option “Use Cloud Storage with appropriate storage classes and retention policies for immutable objects” instead addresses the requested architecture selection.
C:
Boot disks lack appropriate durable retention and lifecycle governance. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that specific clinical records have mandatory retention and legal hold.
D:
The alternative “Review object access, retrieval latency and regulated retention classes” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, inventory shows petabytes of immutable DICOM objects with annual reads. The option “Use Cloud Storage with appropriate storage classes and retention policies for immutable objects” instead addresses the requested architecture selection.
Question 416
Case study: Coastal emergency response unit: on-prem data warehouse
Coastal emergency response unit relies on on-prem data warehouse to deliver its operational commitments. The current architectural problem is that warehouse queries depend on nightly CSV copies with missing change history. The team has recorded this evidence: profile shows source records revised after files are exported. Any proposed response must preserve the requirement that emergency operations need reproducible data not stale extracts.
At Coastal emergency response unit, the on-prem data warehouse workload has a documented risk: warehouse queries depend on nightly CSV copies with missing change history. The review found that profile shows source records revised after files are exported. The architecture must also ensure that emergency operations need reproducible data not stale extracts. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Run source and target in parallel across a full monthly correction cycle
- Assess source CDC availability, schema drift and acceptable analytical lag
- Copy the same static CSV once and label it a real-time migration
- Design controlled CDC or incremental warehouse ingestion with lineage
Explanation
Correct Answer
B:
Assess source CDC availability, schema drift and acceptable analytical lag is the appropriate diagnostic because the observation—profile shows source records revised after files are exported—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (warehouse queries depend on nightly CSV copies with missing change history) before the design is approved.
Incorrect Answers
A:
The alternative “Run source and target in parallel across a full monthly correction cycle” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, profile shows source records revised after files are exported. The option “Assess source CDC availability, schema drift and acceptable analytical lag” instead addresses the requested root-cause evidence.
C:
A one-time extract cannot propagate later corrections. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that emergency operations need reproducible data not stale extracts.
D:
The alternative “Design controlled CDC or incremental warehouse ingestion with lineage” is target architecture selection; it does not establish why the observed path failed. In the reported observation, profile shows source records revised after files are exported. The option “Assess source CDC availability, schema drift and acceptable analytical lag” instead addresses the requested root-cause evidence.
Question 417
At University student services, the support cost decision workload has a documented risk: finance wants to optimize Cloud Run spending by terminating instances during exam registration. The review found that cost report shows request demand peaks 20x within minutes. The architecture must also ensure that students must be able to submit registration before hard deadlines. What enduring Google Cloud design should the team choose now that the failure mode is understood?
- Set min and max instances to zero during the announced registration peak
- Model workload demand, latency cost of cold starts and peak business value
- Watch error budgets, cold-start latency and cost anomaly alerts
- Set spending guardrails compatible with required minimum capacity and scaling
Explanation
Correct Answer
D:
Set spending guardrails compatible with required minimum capacity and scaling targets the underlying issue (finance wants to optimize Cloud Run spending by terminating instances during exam registration) rather than merely reporting symptoms. It also preserves the required outcome (students must be able to submit registration before hard deadlines), which a target-state design must satisfy.
Incorrect Answers
A:
A blanket shutdown destroys the core business outcome. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that students must be able to submit registration before hard deadlines.
B:
The alternative “Model workload demand, latency cost of cold starts and peak business value” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, cost report shows request demand peaks 20x within minutes. The option “Set spending guardrails compatible with required minimum capacity and scaling” instead addresses the requested architecture selection.
C:
The alternative “Watch error budgets, cold-start latency and cost anomaly alerts” measures results without defining the preventive design now required. In the reported observation, cost report shows request demand peaks 20x within minutes. The option “Set spending guardrails compatible with required minimum capacity and scaling” instead addresses the requested architecture selection.
Question 418
Case study: Global research cloud: project-to-project data movement
Global research cloud relies on project-to-project data movement to deliver its operational commitments. The current architectural problem is that a sensitive BigQuery dataset is read by a broad reporting service account. The team has recorded this evidence: query logs show access from an unrelated project outside the research boundary. Any proposed response must preserve the requirement that only approved analytical workloads may join identifiable records.
Consider Global research cloud and its project-to-project data movement workload. The issue is that a sensitive BigQuery dataset is read by a broad reporting service account; the current observation is that query logs show access from an unrelated project outside the research boundary. The team must ensure that only approved analytical workloads may join identifiable records. The team has completed discovery. Which preventive or corrective architecture is most appropriate?
- Review cross-perimeter access attempts and exception approvals
- Combine dataset IAM with supported VPC Service Controls restrictions
- Assume a private IP alone prevents data exfiltration through API calls
- Inspect principals, service perimeter scope and destination datasets
Explanation
Correct Answer
B:
Combine dataset IAM with supported VPC Service Controls restrictions targets the underlying issue (a sensitive BigQuery dataset is read by a broad reporting service account) rather than merely reporting symptoms. It also preserves the required outcome (only approved analytical workloads may join identifiable records), which a target-state design must satisfy.
Incorrect Answers
A:
The alternative “Review cross-perimeter access attempts and exception approvals” measures results without defining the preventive design now required. In the reported observation, query logs show access from an unrelated project outside the research boundary. The option “Combine dataset IAM with supported VPC Service Controls restrictions” instead addresses the requested architecture selection.
C:
Network privacy alone cannot enforce Google API data boundaries. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that only approved analytical workloads may join identifiable records.
D:
The alternative “Inspect principals, service perimeter scope and destination datasets” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, query logs show access from an unrelated project outside the research boundary. The option “Combine dataset IAM with supported VPC Service Controls restrictions” instead addresses the requested architecture selection.
Question 419
Case study: Regional outpatient clinics: clinical application identity
Regional outpatient clinics relies on clinical application identity to deliver its operational commitments. The current architectural problem is that container workloads use downloadable service-account keys in application configuration. The team has recorded this evidence: repository scan finds a private key committed in a build manifest. Any proposed response must preserve the requirement that production services require no long-lived exportable keys.
At Regional outpatient clinics, the Google Cloud design for clinical application identity is affected because container workloads use downloadable service-account keys in application configuration. A review found that repository scan finds a private key committed in a build manifest. The proposed response must account for the requirement that production services require no long-lived exportable keys. Which controlled implementation should be used to preserve operational continuity during the change?
- Alert on new service-account keys, token abuse and excessive role bindings
- Store the JSON key in a differently named repository folder
- Rotate exposed keys and migrate workloads to short-lived identity tokens safely
- Use Workload Identity Federation for GKE and narrowly scoped Google service accounts
Explanation
Correct Answer
C:
Rotate exposed keys and migrate workloads to short-lived identity tokens safely is a controlled means to introduce the approved architecture while meeting the requirement that production services require no long-lived exportable keys. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Alert on new service-account keys, token abuse and excessive role bindings” addresses later monitoring rather than the actual controlled deployment. In the reported observation, repository scan finds a private key committed in a build manifest. The option “Rotate exposed keys and migrate workloads to short-lived identity tokens safely” instead addresses the requested controlled implementation.
B:
Renaming credentials does not protect or revoke them. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that production services require no long-lived exportable keys.
D:
The alternative “Use Workload Identity Federation for GKE and narrowly scoped Google service accounts” describes the chosen design, but not how it is introduced safely. In the reported observation, repository scan finds a private key committed in a build manifest. The option “Rotate exposed keys and migrate workloads to short-lived identity tokens safely” instead addresses the requested controlled implementation.
Question 420
Consider Healthcare workflow vendor and its model-data residency workload. The issue is that a generative AI workflow proposes calling a model endpoint in a prohibited region; the current observation is that architecture diagram shows document prompts cross an international boundary. The team must ensure that health records must stay in their legally allowed data locations. Which acceptance test should demonstrate both protection against the failure and continued authorized service?
- Check logs and network traces show no prompt data leaves the allowed geography
- Assume encryption during transfer makes an illegal cross-border export compliant
- Map model endpoints, logging, caching and prompt-processing locations
- Pilot regional model routing with private data pipelines and disabled unapproved exports
Explanation
Correct Answer
A:
Check logs and network traces show no prompt data leaves the allowed geography is a direct acceptance test of the path implicated by architecture diagram shows document prompts cross an international boundary. It checks that the original risk (a generative AI workflow proposes calling a model endpoint in a prohibited region) has actually been controlled and tests that permitted operations still meet the requirement that health records must stay in their legally allowed data locations.
Incorrect Answers
B:
Encryption does not itself satisfy geographic processing restrictions. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that health records must stay in their legally allowed data locations.
C:
The alternative “Map model endpoints, logging, caching and prompt-processing locations” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, architecture diagram shows document prompts cross an international boundary. The option “Check logs and network traces show no prompt data leaves the allowed geography” instead addresses the requested acceptance verification.
D:
The alternative “Pilot regional model routing with private data pipelines and disabled unapproved exports” documents change execution but not its operational acceptance result. In the reported observation, architecture diagram shows document prompts cross an international boundary. The option “Check logs and network traces show no prompt data leaves the allowed geography” instead addresses the requested acceptance verification.