Google Professional Cloud Architect Practice Test 13
Question 120
Case study: International automotive retailer: API gateway migration
International automotive retailer relies on API gateway migration to deliver its operational commitments. The current architectural problem is that third-party dealerships expect old JSON fields while a new service removes one required property. The team has recorded this evidence: contract tests show older clients fail when the new revision is published. Any proposed response must preserve the requirement that dealer ordering cannot require simultaneous client upgrades.
International automotive retailer plans to update API gateway migration. Investigators found that contract tests show older clients fail when the new revision is published, consistent with the reported problem that third-party dealerships expect old JSON fields while a new service removes one required property. The response must satisfy the requirement that dealer ordering cannot require simultaneous client upgrades. The design review is over and production introduction is next. Which action is the best fit?
- Remove legacy fields immediately because the provider source code is updated
- Design backward-compatible API versioning and deprecation policy
- Deploy compatibility adapter with parallel metrics and announced migration window
- Track remaining old-client traffic and breaking-response failures
Explanation
Correct Answer
C:
Deploy compatibility adapter with parallel metrics and announced migration window is a controlled means to introduce the approved architecture while meeting the requirement that dealer ordering cannot require simultaneous client upgrades. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
Client contracts are not automatically updated with server code. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that dealer ordering cannot require simultaneous client upgrades.
B:
The alternative “Design backward-compatible API versioning and deprecation policy” describes the chosen design, but not how it is introduced safely. In the reported observation, contract tests show older clients fail when the new revision is published. The option “Deploy compatibility adapter with parallel metrics and announced migration window” instead addresses the requested controlled implementation.
D:
The alternative “Track remaining old-client traffic and breaking-response failures” addresses later monitoring rather than the actual controlled deployment. In the reported observation, contract tests show older clients fail when the new revision is published. The option “Deploy compatibility adapter with parallel metrics and announced migration window” instead addresses the requested controlled implementation.
Question 121
Case study: Medical appointment SaaS: serverless private database access
Medical appointment SaaS relies on serverless private database access to deliver its operational commitments. The current architectural problem is that Cloud Run service has public database IP access though all systems reside in one VPC. The team has recorded this evidence: connection logs show traffic to a globally routable database endpoint. Any proposed response must preserve the requirement that patient database must only accept internal workload connections.
Consider Medical appointment SaaS and its serverless private database access workload. The issue is that Cloud Run service has public database IP access though all systems reside in one VPC; the current observation is that connection logs show traffic to a globally routable database endpoint. The team must ensure that patient database must only accept internal workload connections. Which acceptance test should demonstrate both protection against the failure and continued authorized service?
- Attempt external database connection and verify only authorized service succeeds
- Permit the database to accept all public IPs because TLS is enabled
- Map serverless egress path, database listeners and firewall rules
- Cut over service revision to private egress and remove public listener safely
Explanation
Correct Answer
A:
Attempt external database connection and verify only authorized service succeeds is a direct acceptance test of the path implicated by connection logs show traffic to a globally routable database endpoint. It checks that the original risk (Cloud Run service has public database IP access though all systems reside in one VPC) has actually been controlled and tests that permitted operations still meet the requirement that patient database must only accept internal workload connections.
Incorrect Answers
B:
TLS does not meet the private reachability requirement. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that patient database must only accept internal workload connections.
C:
The alternative “Map serverless egress path, database listeners and firewall rules” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, connection logs show traffic to a globally routable database endpoint. The option “Attempt external database connection and verify only authorized service succeeds” instead addresses the requested acceptance verification.
D:
The alternative “Cut over service revision to private egress and remove public listener safely” documents change execution but not its operational acceptance result. In the reported observation, connection logs show traffic to a globally routable database endpoint. The option “Attempt external database connection and verify only authorized service succeeds” instead addresses the requested acceptance verification.
Question 122
Case study: Insurance document platform: external customer authentication
Insurance document platform relies on external customer authentication to deliver its operational commitments. The current architectural problem is that a business partner requests privileged access using only a static shared API key. The team has recorded this evidence: request log shows the same key used from several external offices. Any proposed response must preserve the requirement that partner access must identify the calling workload and enforce scopes.
At Insurance document platform, the external customer authentication workload has a documented risk: a business partner requests privileged access using only a static shared API key. The review found that request log shows the same key used from several external offices. The architecture must also ensure that partner access must identify the calling workload and enforce scopes. What follow-up metric or alert will identify emerging failures after the initial acceptance test?
- Attempt unapproved claims and confirm access denied while valid tokens work
- Monitor issuer trust changes and anomalous token audience values
- Adopt federated workload identity and scoped authorization with token expiry
- Expand the shared API key to every document endpoint for convenience
Explanation
Correct Answer
B:
Monitor issuer trust changes and anomalous token audience values reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a business partner requests privileged access using only a static shared API key) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Attempt unapproved claims and confirm access denied while valid tokens work” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, request log shows the same key used from several external offices. The option “Monitor issuer trust changes and anomalous token audience values” instead addresses the requested ongoing operational assurance.
C:
The alternative “Adopt federated workload identity and scoped authorization with token expiry” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, request log shows the same key used from several external offices. The option “Monitor issuer trust changes and anomalous token audience values” instead addresses the requested ongoing operational assurance.
D:
Shared keys cannot represent least-privilege workload identity. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that partner access must identify the calling workload and enforce scopes.
Question 123
At Local telecom provider, the VMware-based customer management workload has a documented risk: team wants to migrate hundreds of VMware virtual machines with almost no application changes. The review found that migration inventory shows tight network coupling and unsupported guest customization. The architecture must also ensure that a contract requires a one-year low-risk transitional hosting period. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Map VMware dependencies, supported software versions and network IP collisions
- Delete the existing hypervisor configurations before verifying guest compatibility
- Pilot a VM cohort with private connectivity and validated operational ownership
- Consider Google Cloud VMware Engine for compatible transitional virtualization
- Review transitional cost and per-app refactor/decommission roadmap
Explanation
Correct Answers
C:
Pilot a VM cohort with private connectivity and validated operational ownership is a controlled means to introduce the approved architecture while meeting the requirement that a contract requires a one-year low-risk transitional hosting period. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption. This supplies the controlled-introduction half of the two-action package.
D:
Consider Google Cloud VMware Engine for compatible transitional virtualization targets the underlying issue (team wants to migrate hundreds of VMware virtual machines with almost no application changes) rather than merely reporting symptoms. It also preserves the required outcome (a contract requires a one-year low-risk transitional hosting period), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
Incorrect Answers
A:
This diagnoses the original issue (team wants to migrate hundreds of VMware virtual machines with almost no application changes), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
B:
Unplanned transformation creates unacceptable migration risk. The shortcut does not supply the requested design and safe rollout for VMware-based customer management, where migration inventory shows tight network coupling and unsupported guest customization.
E:
Monitoring VMware-based customer management for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: team wants to migrate hundreds of VMware virtual machines with almost no application changes.
Question 124
Consider Digital archive service and its object version recovery workload. The issue is that a script deleted storage objects and replication copied the deletions to the only backup; the current observation is that restore exercise shows no retained noncurrent version after replication. The team must ensure that a contractual RPO requires recovery from mistaken deletes for 45 days. Which continuous monitoring approach best reveals recurrence or changing dependencies?
- Monitor retention-policy changes and recoverability of sampled objects
- Set lifecycle to delete every previous generation immediately
- Use versioning plus protected retention in a separately controlled recovery bucket
- Delete test objects as an app writer and restore prior protected versions
Explanation
Correct Answer
A:
Monitor retention-policy changes and recoverability of sampled objects reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a script deleted storage objects and replication copied the deletions to the only backup) rather than treating the first successful test as permanent assurance.
Incorrect Answers
B:
Immediate deletion removes the very recovery history required. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that a contractual RPO requires recovery from mistaken deletes for 45 days.
C:
The alternative “Use versioning plus protected retention in a separately controlled recovery bucket” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, restore exercise shows no retained noncurrent version after replication. The option “Monitor retention-policy changes and recoverability of sampled objects” instead addresses the requested ongoing operational assurance.
D:
The alternative “Delete test objects as an app writer and restore prior protected versions” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, restore exercise shows no retained noncurrent version after replication. The option “Monitor retention-policy changes and recoverability of sampled objects” instead addresses the requested ongoing operational assurance.
Question 125
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.
At Regional online pharmacy, the Cloud API quota-aware batching workload has a documented risk: client uploads product catalog through thousands of concurrent write requests and hits API quotas. The review found that errors are 429 and retries synchronize into periodic bursts. The architecture must also ensure that inventory updates must complete without losing products. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Retry every failed request immediately with no backoff or limit
- Ship a rate-aware batch worker with retry and dead-letter handling
- Implement exponential backoff with jitter and bounded concurrency using client libraries
- Inspect quota headers, rate limits and idempotent write behavior
Explanation
Correct Answer
D:
Inspect quota headers, rate limits and idempotent write behavior is the appropriate diagnostic because the observation—errors are 429 and retries synchronize into periodic bursts—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (client uploads product catalog through thousands of concurrent write requests and hits API quotas) before the design is approved.
Incorrect Answers
A:
Synchronized retries amplify quota exhaustion. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that inventory updates must complete without losing products.
B:
The alternative “Ship a rate-aware batch worker with retry and dead-letter handling” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, errors are 429 and retries synchronize into periodic bursts. The option “Inspect quota headers, rate limits and idempotent write behavior” instead addresses the requested root-cause evidence.
C:
The alternative “Implement exponential backoff with jitter and bounded concurrency using client libraries” is target architecture selection; it does not establish why the observed path failed. In the reported observation, errors are 429 and retries synchronize into periodic bursts. The option “Inspect quota headers, rate limits and idempotent write behavior” instead addresses the requested root-cause evidence.
Question 126
Case study: Arctic weather station consortium: IPv6-enabled regional APIs
Arctic weather station consortium relies on IPv6-enabled regional APIs to deliver its operational commitments. The current architectural problem is that mobile clients increasingly use IPv6 but the API ingress accepts IPv4 only. The team has recorded this evidence: synthetic probes show IPv6-only devices time out while IPv4 reaches service. Any proposed response must preserve the requirement that existing IPv4 devices must continue working throughout rollout.
At Arctic weather station consortium, the IPv6-enabled regional APIs workload has a documented risk: mobile clients increasingly use IPv6 but the API ingress accepts IPv4 only. The review found that synthetic probes show IPv6-only devices time out while IPv4 reaches service. The architecture must also ensure that existing IPv4 devices must continue working throughout rollout. The team must deliver the approved control safely. Which deployment sequence is most appropriate?
- Disable IPv4 overnight and assume every remote sensor supports IPv6
- Choose dual-stack ingress and appropriate forwarding with tested IPv6 access controls
- Release IPv6 DNS and load-balancer support gradually with existing IPv4 preserved
- Track per-stack error rates and address exhaustion
Explanation
Correct Answer
C:
Release IPv6 DNS and load-balancer support gradually with existing IPv4 preserved is a controlled means to introduce the approved architecture while meeting the requirement that existing IPv4 devices must continue working throughout rollout. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
A forced protocol cutover strands legacy clients. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that existing IPv4 devices must continue working throughout rollout.
B:
The alternative “Choose dual-stack ingress and appropriate forwarding with tested IPv6 access controls” describes the chosen design, but not how it is introduced safely. In the reported observation, synthetic probes show IPv6-only devices time out while IPv4 reaches service. The option “Release IPv6 DNS and load-balancer support gradually with existing IPv4 preserved” instead addresses the requested controlled implementation.
D:
The alternative “Track per-stack error rates and address exhaustion” addresses later monitoring rather than the actual controlled deployment. In the reported observation, synthetic probes show IPv6-only devices time out while IPv4 reaches service. The option “Release IPv6 DNS and load-balancer support gradually with existing IPv4 preserved” instead addresses the requested controlled implementation.
Question 127
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.
At Industrial distributor, the interwarehouse shipment events workload has a documented risk: orders must trigger independent finance and warehouse actions without a central polling table. The review found that architecture diagram shows tight synchronous calls to five downstream services. The architecture must also ensure that an outage in accounting must not block physical pick requests. The team must deliver the approved control safely. Which deployment sequence is most appropriate?
- Have warehouse service synchronously call every downstream system before confirming an order
- Monitor backlog, dead letters and per-consumer delivery lag
- Publish durable order events to Pub/Sub subscriptions for decoupled consumers
- Introduce an outbox and migrate one downstream consumer at a time
Explanation
Correct Answer
D:
Introduce an outbox and migrate one downstream consumer at a time is a controlled means to introduce the approved architecture while meeting the requirement that an outage in accounting must not block physical pick requests. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
Synchronous fanout propagates a slow consumer into order failures. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that an outage in accounting must not block physical pick requests.
B:
The alternative “Monitor backlog, dead letters and per-consumer delivery lag” addresses later monitoring rather than the actual controlled deployment. In the reported observation, architecture diagram shows tight synchronous calls to five downstream services. The option “Introduce an outbox and migrate one downstream consumer at a time” instead addresses the requested controlled implementation.
C:
The alternative “Publish durable order events to Pub/Sub subscriptions for decoupled consumers” describes the chosen design, but not how it is introduced safely. In the reported observation, architecture diagram shows tight synchronous calls to five downstream services. The option “Introduce an outbox and migrate one downstream consumer at a time” instead addresses the requested controlled implementation.
Question 128
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.
At Cross-border payment provider, the Google Cloud design for regulated retention policy is affected because cloud backups are replicated globally without legal review of data-residency restrictions. A review found that compliance assessment finds a bucket's secondary location is outside allowed jurisdiction. The proposed response must account for the requirement that cardholder data must remain only in approved processing geography. A deployment ticket has been closed. What direct evidence would justify solution signoff?
- Prove primary and recovery copies remain in allowed geography after failover
- Store the most sensitive copies in any multi-region regardless of its constituent locations
- Migrate or recreate noncompliant replicas with regulatory signoff
- Identify all replica and restore locations, policy controls and legal owners
Explanation
Correct Answer
A:
Prove primary and recovery copies remain in allowed geography after failover is a direct acceptance test of the path implicated by compliance assessment finds a bucket's secondary location is outside allowed jurisdiction. It checks that the original risk (cloud backups are replicated globally without legal review of data-residency restrictions) has actually been controlled and tests that permitted operations still meet the requirement that cardholder data must remain only in approved processing geography.
Incorrect Answers
B:
A global location can violate specific geographic transfer restrictions. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that cardholder data must remain only in approved processing geography.
C:
The alternative “Migrate or recreate noncompliant replicas with regulatory signoff” documents change execution but not its operational acceptance result. In the reported observation, compliance assessment finds a bucket's secondary location is outside allowed jurisdiction. The option “Prove primary and recovery copies remain in allowed geography after failover” instead addresses the requested acceptance verification.
D:
The alternative “Identify all replica and restore locations, policy controls and legal owners” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, compliance assessment finds a bucket's secondary location is outside allowed jurisdiction. The option “Prove primary and recovery copies remain in allowed geography after failover” instead addresses the requested acceptance verification.
Question 129
Healthcare payments startup plans to update release regression validation. Investigators found that incident reveals token expiry and cross-tenant access tests were omitted, consistent with the reported problem that team tests only HTTP status after replacing the production authentication component. The response must satisfy the requirement that payments and patient data require safe release acceptance. The design review is over and production introduction is next. Which action is the best fit?
- Build automated integration tests for valid and denied authorization paths
- Treat an HTTP 200 response as proof all identity controls work
- Monitor token failure trends and late regression reports
- Deploy new authentication through canary traffic with rollback on errors
Explanation
Correct Answer
D:
Deploy new authentication through canary traffic with rollback on errors is a controlled means to introduce the approved architecture while meeting the requirement that payments and patient data require safe release acceptance. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Build automated integration tests for valid and denied authorization paths” describes the chosen design, but not how it is introduced safely. In the reported observation, incident reveals token expiry and cross-tenant access tests were omitted. The option “Deploy new authentication through canary traffic with rollback on errors” instead addresses the requested controlled implementation.
B:
A success code says nothing about unauthorized access paths. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that payments and patient data require safe release acceptance.
C:
The alternative “Monitor token failure trends and late regression reports” addresses later monitoring rather than the actual controlled deployment. In the reported observation, incident reveals token expiry and cross-tenant access tests were omitted. The option “Deploy new authentication through canary traffic with rollback on errors” instead addresses the requested controlled implementation.
Question 130
Case study: Coastal logistics firm: Storage API pagination
Coastal logistics firm relies on Storage API pagination to deliver its operational commitments. The current architectural problem is that inventory script processes only the first page of Cloud Storage objects. The team has recorded this evidence: logs show listing stops at 1,000 objects despite millions in bucket. Any proposed response must preserve the requirement that compliance inventory must enumerate all object generations.
At Coastal logistics firm, the Storage API pagination workload has a documented risk: inventory script processes only the first page of Cloud Storage objects. The review found that logs show listing stops at 1,000 objects despite millions in bucket. The architecture must also ensure that compliance inventory must enumerate all object generations. Which post-change test most reliably distinguishes a functioning control from a merely successful installation?
- Deploy incremental inventory with restartable page checkpoints
- Inspect pagination tokens, versions and API quota behavior
- Assume one list call always returns an entire bucket
- Compare script count and generations to independent bucket inventory
Explanation
Correct Answer
D:
Compare script count and generations to independent bucket inventory is a direct acceptance test of the path implicated by logs show listing stops at 1,000 objects despite millions in bucket. It checks that the original risk (inventory script processes only the first page of Cloud Storage objects) has actually been controlled and tests that permitted operations still meet the requirement that compliance inventory must enumerate all object generations.
Incorrect Answers
A:
The alternative “Deploy incremental inventory with restartable page checkpoints” documents change execution but not its operational acceptance result. In the reported observation, logs show listing stops at 1,000 objects despite millions in bucket. The option “Compare script count and generations to independent bucket inventory” instead addresses the requested acceptance verification.
B:
The alternative “Inspect pagination tokens, versions and API quota behavior” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, logs show listing stops at 1,000 objects despite millions in bucket. The option “Compare script count and generations to independent bucket inventory” instead addresses the requested acceptance verification.
C:
Paginated APIs can omit most objects unless continued. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that compliance inventory must enumerate all object generations.