Google Professional Cloud Architect Practice Test 38
Question 370
Case study: National pharmacy network: central NAT egress
National pharmacy network relies on central NAT egress to deliver its operational commitments. The current architectural problem is that a vendor allowlist changes every time cloud VMs autoscale with ephemeral external IPs. The team has recorded this evidence: packet trace shows outbound API requests use different VM public addresses. Any proposed response must preserve the requirement that drug inventory partner permits only named stable source addresses.
At National pharmacy network, the Google Cloud design for central NAT egress is affected because a vendor allowlist changes every time cloud VMs autoscale with ephemeral external IPs. A review found that packet trace shows outbound API requests use different VM public addresses. The proposed response must account for the requirement that drug inventory partner permits only named stable source addresses. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?
- Assign a new public IP to every ephemeral VM and email the vendor daily
- Migrate VMs to private instances and update partner allowlists before cutover
- Identify egress flows and where dynamic external addressing is introduced
- Use Cloud NAT with reserved egress IP addresses for private-subnet instances
Explanation
Correct Answer
C:
Identify egress flows and where dynamic external addressing is introduced is the appropriate diagnostic because the observation—packet trace shows outbound API requests use different VM public addresses—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (a vendor allowlist changes every time cloud VMs autoscale with ephemeral external IPs) before the design is approved.
Incorrect Answers
A:
Changing per-instance IPs cannot maintain a stable partner allowlist. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that drug inventory partner permits only named stable source addresses.
B:
The alternative “Migrate VMs to private instances and update partner allowlists before cutover” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, packet trace shows outbound API requests use different VM public addresses. The option “Identify egress flows and where dynamic external addressing is introduced” instead addresses the requested root-cause evidence.
D:
The alternative “Use Cloud NAT with reserved egress IP addresses for private-subnet instances” is target architecture selection; it does not establish why the observed path failed. In the reported observation, packet trace shows outbound API requests use different VM public addresses. The option “Identify egress flows and where dynamic external addressing is introduced” instead addresses the requested root-cause evidence.
Question 371
Public transportation authority plans to update organization location constraint. Investigators found that resource inventory shows unrestricted region creation in folder projects, consistent with the reported problem that test projects in an overseas region unexpectedly receive personal commuter data. The response must satisfy the requirement that all raw rider IDs must remain in the designated country. The approved change has been applied. Which validation provides the clearest evidence the original problem is fixed?
- Document a preferred region but leave cloud APIs unrestricted
- Try deploying a prohibited regional resource and confirm denial
- Stage policy constraints for new projects then move existing assets safely
- Identify data-flow locations and policy inheritance across projects
Explanation
Correct Answer
B:
Try deploying a prohibited regional resource and confirm denial is a direct acceptance test of the path implicated by resource inventory shows unrestricted region creation in folder projects. It checks that the original risk (test projects in an overseas region unexpectedly receive personal commuter data) has actually been controlled and tests that permitted operations still meet the requirement that all raw rider IDs must remain in the designated country.
Incorrect Answers
A:
A recommendation alone does not prevent prohibited region deployments. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that all raw rider IDs must remain in the designated country.
C:
The alternative “Stage policy constraints for new projects then move existing assets safely” documents change execution but not its operational acceptance result. In the reported observation, resource inventory shows unrestricted region creation in folder projects. The option “Try deploying a prohibited regional resource and confirm denial” instead addresses the requested acceptance verification.
D:
The alternative “Identify data-flow locations and policy inheritance across projects” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, resource inventory shows unrestricted region creation in folder projects. The option “Try deploying a prohibited regional resource and confirm denial” instead addresses the requested acceptance verification.
Question 372
University public data project plans to update sensitive research boundary. Investigators found that review finds protected training datasets readable from an unrelated compute project, consistent with the reported problem that the analytics team shares projects with public application workloads. The response must satisfy the requirement that university policy forbids exfiltration of patient-linked samples. The team needs an operations signal rather than another design or one-time test. What should it track?
- Use only object naming conventions to stop exfiltration
- Use VPC Service Controls perimeters around supported sensitive services along with IAM
- Test denied cross-perimeter access and allowed research collaboration paths
- Review perimeter violations, allowed egress exemptions and new projects
Explanation
Correct Answer
D:
Review perimeter violations, allowed egress exemptions and new projects reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (the analytics team shares projects with public application workloads) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
Naming cannot enforce data-access boundaries. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that university policy forbids exfiltration of patient-linked samples.
B:
The alternative “Use VPC Service Controls perimeters around supported sensitive services along with IAM” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, review finds protected training datasets readable from an unrelated compute project. The option “Review perimeter violations, allowed egress exemptions and new projects” instead addresses the requested ongoing operational assurance.
C:
The alternative “Test denied cross-perimeter access and allowed research collaboration paths” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, review finds protected training datasets readable from an unrelated compute project. The option “Review perimeter violations, allowed egress exemptions and new projects” instead addresses the requested ongoing operational assurance.
Question 373
The telemetry collector environment at Smart building portfolio faces this issue: sensor ingestion stops whenever the central analytics service is deployed. Supporting evidence shows that test telemetry shows HTTP sensors retry until devices run out of buffer. The architect must preserve the requirement that devices must keep accepting samples through brief backend maintenance. Which migration or rollout step best manages risk, dependencies and reversibility?
- Migrate sensor groups with schema validation and idempotent delivery
- Decouple device ingestion through durable messaging and independently scaling consumers
- Block sensor writes during every analytics rollout
- Watch oldest pending sample, dead-letter errors and quota headroom
Explanation
Correct Answer
A:
Migrate sensor groups with schema validation and idempotent delivery is a controlled means to introduce the approved architecture while meeting the requirement that devices must keep accepting samples through brief backend maintenance. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
The alternative “Decouple device ingestion through durable messaging and independently scaling consumers” describes the chosen design, but not how it is introduced safely. In the reported observation, test telemetry shows HTTP sensors retry until devices run out of buffer. The option “Migrate sensor groups with schema validation and idempotent delivery” instead addresses the requested controlled implementation.
C:
Tight coupling discards data when a downstream service pauses. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that devices must keep accepting samples through brief backend maintenance.
D:
The alternative “Watch oldest pending sample, dead-letter errors and quota headroom” addresses later monitoring rather than the actual controlled deployment. In the reported observation, test telemetry shows HTTP sensors retry until devices run out of buffer. The option “Migrate sensor groups with schema validation and idempotent delivery” instead addresses the requested controlled implementation.
Question 374
Case study: Rural health provider: patient appointment API
Rural health provider relies on patient appointment API to deliver its operational commitments. The current architectural problem is that one-zone hosting meets average latency but fails an entire zone test. The team has recorded this evidence: chaos test stops a zone and all appointment writes fail. Any proposed response must preserve the requirement that emergency scheduling must recover within five minutes without lost confirmations.
At Rural health provider, the Google Cloud design for patient appointment API is affected because one-zone hosting meets average latency but fails an entire zone test. A review found that chaos test stops a zone and all appointment writes fail. The proposed response must account for the requirement that emergency scheduling must recover within five minutes without lost confirmations. Which controlled implementation should be used to preserve operational continuity during the change?
- Alert on zone health, write failures and recovery latency
- Add a larger instance to the same zone and call it disaster recovery
- Roll out across zones with controlled DNS and session transition
- Design multi-zone stateless services with highly available transactional storage
Explanation
Correct Answer
C:
Roll out across zones with controlled DNS and session transition is a controlled means to introduce the approved architecture while meeting the requirement that emergency scheduling must recover within five minutes without lost confirmations. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Alert on zone health, write failures and recovery latency” addresses later monitoring rather than the actual controlled deployment. In the reported observation, chaos test stops a zone and all appointment writes fail. The option “Roll out across zones with controlled DNS and session transition” instead addresses the requested controlled implementation.
B:
Vertical scaling does not survive loss of an entire zone. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that emergency scheduling must recover within five minutes without lost confirmations.
D:
The alternative “Design multi-zone stateless services with highly available transactional storage” describes the chosen design, but not how it is introduced safely. In the reported observation, chaos test stops a zone and all appointment writes fail. The option “Roll out across zones with controlled DNS and session transition” instead addresses the requested controlled implementation.
Question 375
Case study: Rural health provider: patient appointment API
Rural health provider relies on patient appointment API to deliver its operational commitments. The current architectural problem is that one-zone hosting meets average latency but fails an entire zone test. The team has recorded this evidence: chaos test stops a zone and all appointment writes fail. Any proposed response must preserve the requirement that emergency scheduling must recover within five minutes without lost confirmations.
Consider Rural health provider and its patient appointment API workload. The issue is that one-zone hosting meets average latency but fails an entire zone test; the current observation is that chaos test stops a zone and all appointment writes fail. The team must ensure that emergency scheduling must recover within five minutes without lost confirmations. The team has completed discovery. Which preventive or corrective architecture is most appropriate?
- Measure present zone dependencies, RTO/RPO and database write consistency
- Design multi-zone stateless services with highly available transactional storage
- Alert on zone health, write failures and recovery latency
- Add a larger instance to the same zone and call it disaster recovery
Explanation
Correct Answer
B:
Design multi-zone stateless services with highly available transactional storage targets the underlying issue (one-zone hosting meets average latency but fails an entire zone test) rather than merely reporting symptoms. It also preserves the required outcome (emergency scheduling must recover within five minutes without lost confirmations), which a target-state design must satisfy.
Incorrect Answers
A:
The alternative “Measure present zone dependencies, RTO/RPO and database write consistency” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, chaos test stops a zone and all appointment writes fail. The option “Design multi-zone stateless services with highly available transactional storage” instead addresses the requested architecture selection.
C:
The alternative “Alert on zone health, write failures and recovery latency” measures results without defining the preventive design now required. In the reported observation, chaos test stops a zone and all appointment writes fail. The option “Design multi-zone stateless services with highly available transactional storage” instead addresses the requested architecture selection.
D:
Vertical scaling does not survive loss of an entire zone. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that emergency scheduling must recover within five minutes without lost confirmations.
Question 376
At E-commerce promotion service, the Cloud Run database connection storms workload has a documented risk: a serverless revision scales quickly and exhausts a legacy SQL server's connection pool. The review found that database logs show connection refusals at promotion launch. The architecture must also ensure that backend must remain within database concurrency limits. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Calculate per-instance connection pools, maximum instances and request bursts
- Allow unlimited cold-start instances to open independent large pools
- Stage maximum-instance limits and traffic splitting before peak events
- Set Cloud Run concurrency and instance limits with appropriate pooling
Explanation
Correct Answer
A:
Calculate per-instance connection pools, maximum instances and request bursts is the appropriate diagnostic because the observation—database logs show connection refusals at promotion launch—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (a serverless revision scales quickly and exhausts a legacy SQL server's connection pool) before the design is approved.
Incorrect Answers
B:
Unbounded scaling overwhelms a fixed database dependency. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that backend must remain within database concurrency limits.
C:
The alternative “Stage maximum-instance limits and traffic splitting before peak events” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, database logs show connection refusals at promotion launch. The option “Calculate per-instance connection pools, maximum instances and request bursts” instead addresses the requested root-cause evidence.
D:
The alternative “Set Cloud Run concurrency and instance limits with appropriate pooling” is target architecture selection; it does not establish why the observed path failed. In the reported observation, database logs show connection refusals at promotion launch. The option “Calculate per-instance connection pools, maximum instances and request bursts” instead addresses the requested root-cause evidence.
Question 377
Consider Education analytics cooperative and its data pipeline incident triage workload. The issue is that daily analytics job silently drops events with previously unseen nullable fields; the current observation is that Dataflow error logs show schema deserialization failures after partner update. The team must ensure that approved learning dashboards require source-to-target reconciliation. Which continuous monitoring approach best reveals recurrence or changing dependencies?
- Define versioned schemas with controlled evolution and quarantined invalid events
- Discard all unrecognized events without alerting
- Monitor schema rejection and lag by producer
- Replay rejected records and compare expected aggregate metrics
Explanation
Correct Answer
C:
Monitor schema rejection and lag by producer reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (daily analytics job silently drops events with previously unseen nullable fields) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Define versioned schemas with controlled evolution and quarantined invalid events” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, Dataflow error logs show schema deserialization failures after partner update. The option “Monitor schema rejection and lag by producer” instead addresses the requested ongoing operational assurance.
B:
Silent discards create false analytics that appear complete. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that approved learning dashboards require source-to-target reconciliation.
D:
The alternative “Replay rejected records and compare expected aggregate metrics” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, Dataflow error logs show schema deserialization failures after partner update. The option “Monitor schema rejection and lag by producer” instead addresses the requested ongoing operational assurance.
Question 378
At Regional mapping institute, the Cloud Shell access hygiene workload has a documented risk: analysts share one long-lived service account key inside a notebook for gcloud access. The review found that repository audit finds the key in notebook history. The architecture must also ensure that interactive analysts need attributable access without downloaded secrets. What enduring Google Cloud design should the team choose now that the failure mode is understood?
- Use individual user authentication and short-lived impersonation for scoped tasks
- Monitor downloaded key creation and impersonation events
- Map user identities, command permissions and persistent key copies
- Move the service account JSON into a hidden notebook cell
Explanation
Correct Answer
A:
Use individual user authentication and short-lived impersonation for scoped tasks targets the underlying issue (analysts share one long-lived service account key inside a notebook for gcloud access) rather than merely reporting symptoms. It also preserves the required outcome (interactive analysts need attributable access without downloaded secrets), which a target-state design must satisfy.
Incorrect Answers
B:
The alternative “Monitor downloaded key creation and impersonation events” measures results without defining the preventive design now required. In the reported observation, repository audit finds the key in notebook history. The option “Use individual user authentication and short-lived impersonation for scoped tasks” instead addresses the requested architecture selection.
C:
The alternative “Map user identities, command permissions and persistent key copies” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, repository audit finds the key in notebook history. The option “Use individual user authentication and short-lived impersonation for scoped tasks” instead addresses the requested architecture selection.
D:
A hidden cell does not revoke or protect embedded credentials. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that interactive analysts need attributable access without downloaded secrets.
Question 379
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.
The project-to-project data movement environment at Global research cloud faces this issue: a sensitive BigQuery dataset is read by a broad reporting service account. Supporting evidence shows that query logs show access from an unrelated project outside the research boundary. The architect must preserve the requirement that only approved analytical workloads may join identifiable records. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Combine dataset IAM with supported VPC Service Controls restrictions
- Assume a private IP alone prevents data exfiltration through API calls
- Review cross-perimeter access attempts and exception approvals
- Query from unauthorized service projects and confirm perimeter denial
Explanation
Correct Answer
C:
Review cross-perimeter access attempts and exception approvals reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a sensitive BigQuery dataset is read by a broad reporting service account) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Combine dataset IAM with supported VPC Service Controls restrictions” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, query logs show access from an unrelated project outside the research boundary. The option “Review cross-perimeter access attempts and exception approvals” instead addresses the requested ongoing operational assurance.
B:
Network privacy alone cannot enforce Google API data boundaries. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that only approved analytical workloads may join identifiable records.
D:
The alternative “Query from unauthorized service projects and confirm perimeter denial” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, query logs show access from an unrelated project outside the research boundary. The option “Review cross-perimeter access attempts and exception approvals” instead addresses the requested ongoing operational assurance.
Question 380
At City library data portal, the Google Cloud design for accessibility acceptance is affected because a redesigned public portal uses keyboard-inaccessible chart filters. A review found that accessibility audit finds focus cannot reach essential search fields. The proposed response must account for the requirement that government content must be accessible to assistive technology users. Which controlled implementation should be used to preserve operational continuity during the change?
- Track accessibility regressions and user support reports
- Release fixes behind user-testing feedback and rollback
- Approve launch solely because automated unit tests passed
- Include accessible components and automated/manual quality criteria in release requirements
Explanation
Correct Answer
B:
Release fixes behind user-testing feedback and rollback is a controlled means to introduce the approved architecture while meeting the requirement that government content must be accessible to assistive technology users. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Track accessibility regressions and user support reports” addresses later monitoring rather than the actual controlled deployment. In the reported observation, accessibility audit finds focus cannot reach essential search fields. The option “Release fixes behind user-testing feedback and rollback” instead addresses the requested controlled implementation.
C:
Unit tests do not capture all interactive accessibility barriers. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that government content must be accessible to assistive technology users.
D:
The alternative “Include accessible components and automated/manual quality criteria in release requirements” describes the chosen design, but not how it is introduced safely. In the reported observation, accessibility audit finds focus cannot reach essential search fields. The option “Release fixes behind user-testing feedback and rollback” instead addresses the requested controlled implementation.