Google Professional Cloud Architect Practice Test 75
Question 740
The BigQuery scripted exports environment at Digital university archive faces this issue: a nightly bq CLI export uses wildcard datasets and leaks unrelated faculty research. Supporting evidence shows that audit log shows query scope expanded after a new dataset was added. The architect must preserve the requirement that exports must include only approved course statistics. Before approving a solution, which analysis most directly clarifies the underlying dependency or control gap?
- Give the export service account BigQuery Admin over the whole organization
- Identify exact dataset boundaries, IAM roles and query requirements
- Use parameterized explicit BigQuery dataset/table scope with read-only job identity
- Deploy export script with bounded project context and approved schedules
Explanation
Correct Answer
B:
Identify exact dataset boundaries, IAM roles and query requirements is the appropriate diagnostic because the observation—audit log shows query scope expanded after a new dataset was added—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (a nightly bq CLI export uses wildcard datasets and leaks unrelated faculty research) before the design is approved.
Incorrect Answers
A:
Broad admin rights violate the limited read-only extraction purpose. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that exports must include only approved course statistics.
C:
The alternative “Use parameterized explicit BigQuery dataset/table scope with read-only job identity” is target architecture selection; it does not establish why the observed path failed. In the reported observation, audit log shows query scope expanded after a new dataset was added. The option “Identify exact dataset boundaries, IAM roles and query requirements” instead addresses the requested root-cause evidence.
D:
The alternative “Deploy export script with bounded project context and approved schedules” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, audit log shows query scope expanded after a new dataset was added. The option “Identify exact dataset boundaries, IAM roles and query requirements” instead addresses the requested root-cause evidence.
Question 741
International renewable grid data service plans to update penetration-test remediation. Investigators found that retest finds cross-tenant API access still possible with valid token, consistent with the reported problem that last penetration test found an IDOR flaw but the team marked it fixed after updating documentation. The response must satisfy the requirement that commercial clients require strict account isolation. The design review is over and production introduction is next. Which action is the best fit?
- Use object-level auth enforcement with independent negative-case tests
- Close the security finding based only on a signed policy memo
- Monitor new unauthorized access attempts and API route drift
- Deploy fixes under tenant-scoped canary and revoke vulnerable paths
Explanation
Correct Answer
D:
Deploy fixes under tenant-scoped canary and revoke vulnerable paths is a controlled means to introduce the approved architecture while meeting the requirement that commercial clients require strict account isolation. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Use object-level auth enforcement with independent negative-case tests” describes the chosen design, but not how it is introduced safely. In the reported observation, retest finds cross-tenant API access still possible with valid token. The option “Deploy fixes under tenant-scoped canary and revoke vulnerable paths” instead addresses the requested controlled implementation.
B:
Documentation cannot replace verified access-control enforcement. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that commercial clients require strict account isolation.
C:
The alternative “Monitor new unauthorized access attempts and API route drift” addresses later monitoring rather than the actual controlled deployment. In the reported observation, retest finds cross-tenant API access still possible with valid token. The option “Deploy fixes under tenant-scoped canary and revoke vulnerable paths” instead addresses the requested controlled implementation.
Question 742
Case study: Regional online pharmacy: Cloud API quota-aware batching
Regional online pharmacy relies on Cloud API quota-aware batching to deliver its operational commitments. The current architectural problem is that client uploads product catalog through thousands of concurrent write requests and hits API quotas. The team has recorded this evidence: errors are 429 and retries synchronize into periodic bursts. Any proposed response must preserve the requirement that inventory updates must complete without losing products.
Regional online pharmacy plans to update Cloud API quota-aware batching. Investigators found that errors are 429 and retries synchronize into periodic bursts, consistent with the reported problem that client uploads product catalog through thousands of concurrent write requests and hits API quotas. The response must satisfy the requirement that inventory updates must complete without losing products. The design review is over and production introduction is next. Which action is the best fit?
- Implement exponential backoff with jitter and bounded concurrency using client libraries
- Track retry age, permanent failures and quota change requests
- Ship a rate-aware batch worker with retry and dead-letter handling
- Retry every failed request immediately with no backoff or limit
Explanation
Correct Answer
C:
Ship a rate-aware batch worker with retry and dead-letter handling is a controlled means to introduce the approved architecture while meeting the requirement that inventory updates must complete without losing products. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Implement exponential backoff with jitter and bounded concurrency using client libraries” describes the chosen design, but not how it is introduced safely. In the reported observation, errors are 429 and retries synchronize into periodic bursts. The option “Ship a rate-aware batch worker with retry and dead-letter handling” instead addresses the requested controlled implementation.
B:
The alternative “Track retry age, permanent failures and quota change requests” addresses later monitoring rather than the actual controlled deployment. In the reported observation, errors are 429 and retries synchronize into periodic bursts. The option “Ship a rate-aware batch worker with retry and dead-letter handling” instead addresses the requested controlled implementation.
D:
Synchronized retries amplify quota exhaustion. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that inventory updates must complete without losing products.
Question 743
Consider Medical supply chain and its CDC job performance regression workload. The issue is that a nightly database export finishes late despite unchanged source volume; the current observation is that telemetry shows a new transformation now triggers full-table reloads. The team must ensure that hospital inventory reports must arrive before morning replenishment. Which acceptance test should demonstrate both protection against the failure and continued authorized service?
- Measure end-to-end finish time and exact record-level parity
- Provision more dashboard servers while keeping the full reload
- Canary revised pipeline and reconcile late-arriving updates
- Compare pipeline execution plan, input cardinality and transformation deltas
Explanation
Correct Answer
A:
Measure end-to-end finish time and exact record-level parity is a direct acceptance test of the path implicated by telemetry shows a new transformation now triggers full-table reloads. It checks that the original risk (a nightly database export finishes late despite unchanged source volume) has actually been controlled and tests that permitted operations still meet the requirement that hospital inventory reports must arrive before morning replenishment.
Incorrect Answers
B:
Dashboard compute does not correct an inefficient ingestion path. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that hospital inventory reports must arrive before morning replenishment.
C:
The alternative “Canary revised pipeline and reconcile late-arriving updates” documents change execution but not its operational acceptance result. In the reported observation, telemetry shows a new transformation now triggers full-table reloads. The option “Measure end-to-end finish time and exact record-level parity” instead addresses the requested acceptance verification.
D:
The alternative “Compare pipeline execution plan, input cardinality and transformation deltas” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, telemetry shows a new transformation now triggers full-table reloads. The option “Measure end-to-end finish time and exact record-level parity” instead addresses the requested acceptance verification.
Question 744
At International legal services company, the cross-border document collaboration workload has a documented risk: client files are copied to consumer accounts without contractual evidence ownership. The review found that storage audit finds externally shared matter documents with no expiry. The architecture must also ensure that case confidentiality requires explicit client-purpose authorization. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Publish a universally accessible link and rely on legal disclaimers
- Revoke legacy broad grants and migrate valid collaborators through reviewed access
- Apply scoped sharing, purpose labels and time-limited grants with legal approval
- Map data owners, contract purpose and external identities
Explanation
Correct Answer
D:
Map data owners, contract purpose and external identities is the appropriate diagnostic because the observation—storage audit finds externally shared matter documents with no expiry—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (client files are copied to consumer accounts without contractual evidence ownership) before the design is approved.
Incorrect Answers
A:
Disclaimers cannot enforce confidential document access. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that case confidentiality requires explicit client-purpose authorization.
B:
The alternative “Revoke legacy broad grants and migrate valid collaborators through reviewed access” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, storage audit finds externally shared matter documents with no expiry. The option “Map data owners, contract purpose and external identities” instead addresses the requested root-cause evidence.
C:
The alternative “Apply scoped sharing, purpose labels and time-limited grants with legal approval” is target architecture selection; it does not establish why the observed path failed. In the reported observation, storage audit finds externally shared matter documents with no expiry. The option “Map data owners, contract purpose and external identities” instead addresses the requested root-cause evidence.
Question 745
Consider Mobile banking wallet and its payments rollback coordination workload. The issue is that CI tool can roll back app pods but cannot reverse a one-way database ledger migration; the current observation is that release plan contains no financial reconciliation procedure. The team must ensure that posted transactions cannot be duplicated or silently lost. Which continuous monitoring approach best reveals recurrence or changing dependencies?
- Fail deployment mid-cutover and verify ledger consistency after recovery
- Track reconciliation variances and unfinished compensating actions
- Treat a code rollback as automatically reversing every committed financial transaction
- Design backward-compatible ledger migration and auditable compensation patterns
Explanation
Correct Answer
B:
Track reconciliation variances and unfinished compensating actions reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (CI tool can roll back app pods but cannot reverse a one-way database ledger migration) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Fail deployment mid-cutover and verify ledger consistency after recovery” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, release plan contains no financial reconciliation procedure. The option “Track reconciliation variances and unfinished compensating actions” instead addresses the requested ongoing operational assurance.
C:
Financial state changes need explicit reconciliation, not just application rollback. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that posted transactions cannot be duplicated or silently lost.
D:
The alternative “Design backward-compatible ledger migration and auditable compensation patterns” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, release plan contains no financial reconciliation procedure. The option “Track reconciliation variances and unfinished compensating actions” instead addresses the requested ongoing operational assurance.
Question 746
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.
At Global research cloud, the project-to-project data movement workload has a documented risk: a sensitive BigQuery dataset is read by a broad reporting service account. The review found that query logs show access from an unrelated project outside the research boundary. The architecture must also ensure that only approved analytical workloads may join identifiable records. Which post-change test most reliably distinguishes a functioning control from a merely successful installation?
- Inspect principals, service perimeter scope and destination datasets
- Apply access changes in dry-run and validate legitimate research exports
- Assume a private IP alone prevents data exfiltration through API calls
- Query from unauthorized service projects and confirm perimeter denial
Explanation
Correct Answer
D:
Query from unauthorized service projects and confirm perimeter denial is a direct acceptance test of the path implicated by query logs show access from an unrelated project outside the research boundary. It checks that the original risk (a sensitive BigQuery dataset is read by a broad reporting service account) has actually been controlled and tests that permitted operations still meet the requirement that only approved analytical workloads may join identifiable records.
Incorrect Answers
A:
The alternative “Inspect principals, service perimeter scope and destination datasets” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, query logs show access from an unrelated project outside the research boundary. The option “Query from unauthorized service projects and confirm perimeter denial” instead addresses the requested acceptance verification.
B:
The alternative “Apply access changes in dry-run and validate legitimate research exports” documents change execution but not its operational acceptance result. In the reported observation, query logs show access from an unrelated project outside the research boundary. The option “Query from unauthorized service projects and confirm perimeter denial” instead addresses the requested acceptance verification.
C:
Network privacy alone cannot enforce Google API data boundaries. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that only approved analytical workloads may join identifiable records.
Question 747
At National meteorological lab, the distributed foundation-model training workload has a documented risk: the team requests ad hoc GPU VMs spread across zones with slow checkpoint synchronization. The review found that training trace shows workers idle waiting for cross-zone gradient transfer. The architecture must also ensure that accelerator capacity is limited and checkpoint recovery is mandatory. The team must deliver the approved control safely. Which deployment sequence is most appropriate?
- Track utilization, failed checkpoints and accelerator reservation burn
- Stage training cohorts with approved reservations and rollback of resource plans
- Use topology-aware AI Hypercomputer training architecture with durable checkpoints
- Spread training workers across unrelated low-bandwidth VMs without topology planning
Explanation
Correct Answer
B:
Stage training cohorts with approved reservations and rollback of resource plans is a controlled means to introduce the approved architecture while meeting the requirement that accelerator capacity is limited and checkpoint recovery is mandatory. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Track utilization, failed checkpoints and accelerator reservation burn” addresses later monitoring rather than the actual controlled deployment. In the reported observation, training trace shows workers idle waiting for cross-zone gradient transfer. The option “Stage training cohorts with approved reservations and rollback of resource plans” instead addresses the requested controlled implementation.
C:
The alternative “Use topology-aware AI Hypercomputer training architecture with durable checkpoints” describes the chosen design, but not how it is introduced safely. In the reported observation, training trace shows workers idle waiting for cross-zone gradient transfer. The option “Stage training cohorts with approved reservations and rollback of resource plans” instead addresses the requested controlled implementation.
D:
Communication overhead can dominate distributed training. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that accelerator capacity is limited and checkpoint recovery is mandatory.
Question 748
At International sports league, the video storage tiers workload has a documented risk: all raw broadcasts remain in premium storage though almost never retrieved. The review found that access report shows 94% of footage is only viewed once per year. The architecture must also ensure that rights owners require published clips to stay fast while raw footage is protected. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Apply separate Cloud Storage lifecycle classes for streaming clips and cold originals
- Classify object hot/cold access patterns, retention and retrieval cost
- Migrate aged objects after permission and retrieval-time validation
- Move the currently streaming clips into long-retrieval archives unconditionally
Explanation
Correct Answer
B:
Classify object hot/cold access patterns, retention and retrieval cost is the appropriate diagnostic because the observation—access report shows 94% of footage is only viewed once per year—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (all raw broadcasts remain in premium storage though almost never retrieved) before the design is approved.
Incorrect Answers
A:
The alternative “Apply separate Cloud Storage lifecycle classes for streaming clips and cold originals” is target architecture selection; it does not establish why the observed path failed. In the reported observation, access report shows 94% of footage is only viewed once per year. The option “Classify object hot/cold access patterns, retention and retrieval cost” instead addresses the requested root-cause evidence.
C:
The alternative “Migrate aged objects after permission and retrieval-time validation” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, access report shows 94% of footage is only viewed once per year. The option “Classify object hot/cold access patterns, retention and retrieval cost” instead addresses the requested root-cause evidence.
D:
Cold retrieval economics and latency do not fit hot video playback. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that rights owners require published clips to stay fast while raw footage is protected.
Question 749
Case study: National agricultural extension office: drought forecasts
National agricultural extension office relies on drought forecasts to deliver its operational commitments. The current architectural problem is that satellite datasets will multiply as climate partners join and current retention assumes fixed volume. The team has recorded this evidence: forecast identifies increasing seasonal data and changing external contracts. Any proposed response must preserve the requirement that field staff still need affordable offline reports.
National agricultural extension office plans to update drought forecasts. Investigators found that forecast identifies increasing seasonal data and changing external contracts, consistent with the reported problem that satellite datasets will multiply as climate partners join and current retention assumes fixed volume. The response must satisfy the requirement that field staff still need affordable offline reports. The team needs an operations signal rather than another design or one-time test. What should it track?
- Keep every raw satellite capture indefinitely in the highest-price storage class
- Retrieve old seasonal maps and publish offline reports within the stated budget
- Adopt lifecycle-based object storage and decoupled batch product publishing
- Monitor storage class transitions and data license expirations
Explanation
Correct Answer
D:
Monitor storage class transitions and data license expirations reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (satellite datasets will multiply as climate partners join and current retention assumes fixed volume) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
A fixed hot-storage policy wastes funds and ignores changing licenses. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that field staff still need affordable offline reports.
B:
The alternative “Retrieve old seasonal maps and publish offline reports within the stated budget” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, forecast identifies increasing seasonal data and changing external contracts. The option “Monitor storage class transitions and data license expirations” instead addresses the requested ongoing operational assurance.
C:
The alternative “Adopt lifecycle-based object storage and decoupled batch product publishing” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, forecast identifies increasing seasonal data and changing external contracts. The option “Monitor storage class transitions and data license expirations” instead addresses the requested ongoing operational assurance.
Question 750
At National digital identification office, the Google Cloud design for external identity service onboarding is affected because a public API rollout lacks per-agency token audience enforcement. A review found that test shows an agency credential can call unrelated record endpoints. The proposed response must account for the requirement that agency access must be least privilege and auditable. Which controlled implementation should be used to preserve operational continuity during the change?
- Allow any signed token from any agency to read all records
- Track token audience drift and unauthorized API attempts
- Use audience-scoped tokens and appropriate API authorization checks
- Onboard agencies incrementally with policy tests and request logs
Explanation
Correct Answer
D:
Onboard agencies incrementally with policy tests and request logs is a controlled means to introduce the approved architecture while meeting the requirement that agency access must be least privilege and auditable. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
Signature validity does not grant access to unrelated applications. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that agency access must be least privilege and auditable.
B:
The alternative “Track token audience drift and unauthorized API attempts” addresses later monitoring rather than the actual controlled deployment. In the reported observation, test shows an agency credential can call unrelated record endpoints. The option “Onboard agencies incrementally with policy tests and request logs” instead addresses the requested controlled implementation.
C:
The alternative “Use audience-scoped tokens and appropriate API authorization checks” describes the chosen design, but not how it is introduced safely. In the reported observation, test shows an agency credential can call unrelated record endpoints. The option “Onboard agencies incrementally with policy tests and request logs” instead addresses the requested controlled implementation.