Google Professional Cloud Architect Practice Test 40
Question 390
At Automotive safety modeling startup, the reinforcement model evaluation workload has a documented risk: engineering wants to deploy a new model before proving corner-case behavior. The review found that evaluation report covers average accuracy but no rare safety-critical maneuvers. The architecture must also ensure that safety review requires rigorous offline evaluation and rollback. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Introduce shadow inference before any controlled production promotion
- Approve the model solely because aggregate accuracy rose one percent
- Design model lifecycle gates with offline evaluation and isolated acceptance
- Define rare-event evaluation cases, adversarial tests and traceability
Explanation
Correct Answer
D:
Define rare-event evaluation cases, adversarial tests and traceability is the appropriate diagnostic because the observation—evaluation report covers average accuracy but no rare safety-critical maneuvers—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (engineering wants to deploy a new model before proving corner-case behavior) before the design is approved.
Incorrect Answers
A:
The alternative “Introduce shadow inference before any controlled production promotion” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, evaluation report covers average accuracy but no rare safety-critical maneuvers. The option “Define rare-event evaluation cases, adversarial tests and traceability” instead addresses the requested root-cause evidence.
B:
Mean accuracy can hide unacceptable safety-regression tails. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that safety review requires rigorous offline evaluation and rollback.
C:
The alternative “Design model lifecycle gates with offline evaluation and isolated acceptance” is target architecture selection; it does not establish why the observed path failed. In the reported observation, evaluation report covers average accuracy but no rare safety-critical maneuvers. The option “Define rare-event evaluation cases, adversarial tests and traceability” instead addresses the requested root-cause evidence.
Question 391
Case study: Regional maritime operator: shared VPC service projects
Regional maritime operator relies on shared VPC service projects to deliver its operational commitments. The current architectural problem is that each harbor app team creates duplicate subnets with conflicting ranges. The team has recorded this evidence: IPAM report shows two VPCs contain identical 10.40.0.0/16 networks. Any proposed response must preserve the requirement that network security must be owned centrally while applications manage their services.
Regional maritime operator plans to update shared VPC service projects. Investigators found that IPAM report shows two VPCs contain identical 10.40.0.0/16 networks, consistent with the reported problem that each harbor app team creates duplicate subnets with conflicting ranges. The response must satisfy the requirement that network security must be owned centrally while applications manage their services. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?
- Migrate one service project and adjust routes/firewalls with rollback
- Peer overlapping address spaces and assume routes propagate transitively
- Map overlapping allocations and separation of network and application roles
- Use a centrally administered Shared VPC host with nonoverlapping subnets and delegated attachment
Explanation
Correct Answer
C:
Map overlapping allocations and separation of network and application roles is the appropriate diagnostic because the observation—IPAM report shows two VPCs contain identical 10.40.0.0/16 networks—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (each harbor app team creates duplicate subnets with conflicting ranges) before the design is approved.
Incorrect Answers
A:
The alternative “Migrate one service project and adjust routes/firewalls with rollback” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, IPAM report shows two VPCs contain identical 10.40.0.0/16 networks. The option “Map overlapping allocations and separation of network and application roles” instead addresses the requested root-cause evidence.
B:
VPC peering does not solve overlapping ranges or provide arbitrary transitive routing. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that network security must be owned centrally while applications manage their services.
D:
The alternative “Use a centrally administered Shared VPC host with nonoverlapping subnets and delegated attachment” is target architecture selection; it does not establish why the observed path failed. In the reported observation, IPAM report shows two VPCs contain identical 10.40.0.0/16 networks. The option “Map overlapping allocations and separation of network and application roles” instead addresses the requested root-cause evidence.
Question 392
National retail cooperative plans to update audit log preservation. Investigators found that audit exercise shows log sinks owned by the affected project, consistent with the reported problem that a project owner can disable or delete local logging after an unauthorized configuration change. The response must satisfy the requirement that investigations require independently retained administrative events. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Aggregate audit logs into a protected central project with minimal deletion rights
- Watch logging exclusions, sink failures and retention violations
- Store the only audit copy in a bucket controlled by the investigated project owner
- Stage organization-level sinks and validate destination authorization
- Map log routing permissions, sink exclusions and retention requirements
Explanation
Correct Answers
A:
Aggregate audit logs into a protected central project with minimal deletion rights targets the underlying issue (a project owner can disable or delete local logging after an unauthorized configuration change) rather than merely reporting symptoms. It also preserves the required outcome (investigations require independently retained administrative events), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
D:
Stage organization-level sinks and validate destination authorization is a controlled means to introduce the approved architecture while meeting the requirement that investigations require independently retained administrative events. 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.
Incorrect Answers
B:
Monitoring audit log preservation for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: a project owner can disable or delete local logging after an unauthorized configuration change.
C:
Shared deletion authority undermines evidentiary independence. The shortcut does not supply the requested design and safe rollout for audit log preservation, where audit exercise shows log sinks owned by the affected project.
E:
This diagnoses the original issue (a project owner can disable or delete local logging after an unauthorized configuration change), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
Question 393
Case study: International bank holding company: regulated data-center extension
International bank holding company relies on regulated data-center extension to deliver its operational commitments. The current architectural problem is that the proposed Dedicated Interconnect lacks a backup location and depends on a single metro facility. The team has recorded this evidence: site survey lists one colocation provider and a common power feed for both links. Any proposed response must preserve the requirement that settlement services require redundant connectivity with predictable private latency.
At International bank holding company, the Google Cloud design for regulated data-center extension is affected because the proposed Dedicated Interconnect lacks a backup location and depends on a single metro facility. A review found that site survey lists one colocation provider and a common power feed for both links. The proposed response must account for the requirement that settlement services require redundant connectivity with predictable private latency. Which controlled implementation should be used to preserve operational continuity during the change?
- Track circuit utilization, BGP flaps and SLA breaches
- Coordinate circuit turn-up and route preference in staged change windows
- Design geographically separated Interconnect circuits with independent BGP sessions and failover
- Install two ports in the same rack and call them regionally redundant
Explanation
Correct Answer
B:
Coordinate circuit turn-up and route preference in staged change windows is a controlled means to introduce the approved architecture while meeting the requirement that settlement services require redundant connectivity with predictable private latency. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Track circuit utilization, BGP flaps and SLA breaches” addresses later monitoring rather than the actual controlled deployment. In the reported observation, site survey lists one colocation provider and a common power feed for both links. The option “Coordinate circuit turn-up and route preference in staged change windows” instead addresses the requested controlled implementation.
C:
The alternative “Design geographically separated Interconnect circuits with independent BGP sessions and failover” describes the chosen design, but not how it is introduced safely. In the reported observation, site survey lists one colocation provider and a common power feed for both links. The option “Coordinate circuit turn-up and route preference in staged change windows” instead addresses the requested controlled implementation.
D:
Common power and facility dependencies defeat geographic resilience. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that settlement services require redundant connectivity with predictable private latency.
Question 394
At Industrial parts distributor, the Google Cloud design for container rollout traceability is affected because multiple teams manually push the same mutable image tag between environments. A review found that deployment journal cannot identify which digest passed integration testing. The proposed response must account for the requirement that production packages must have provable origin and approved owners. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?
- Use immutable Artifact Registry digests and attested release promotion
- Deploy the exact validated digest through staged environments
- Trace artifact digests, promotions and signer authority
- Treat the latest tag string as immutable evidence of software identity
Explanation
Correct Answer
C:
Trace artifact digests, promotions and signer authority is the appropriate diagnostic because the observation—deployment journal cannot identify which digest passed integration testing—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (multiple teams manually push the same mutable image tag between environments) before the design is approved.
Incorrect Answers
A:
The alternative “Use immutable Artifact Registry digests and attested release promotion” is target architecture selection; it does not establish why the observed path failed. In the reported observation, deployment journal cannot identify which digest passed integration testing. The option “Trace artifact digests, promotions and signer authority” instead addresses the requested root-cause evidence.
B:
The alternative “Deploy the exact validated digest through staged environments” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, deployment journal cannot identify which digest passed integration testing. The option “Trace artifact digests, promotions and signer authority” instead addresses the requested root-cause evidence.
D:
A mutable tag does not establish release provenance. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that production packages must have provable origin and approved owners.
Question 395
At Emergency response simulation unit, the Firestore emulator testing workload has a documented risk: developers test access rules only against the live production database. The review found that test activity creates real private user documents. The architecture must also ensure that simulations must avoid affecting production patient or responder data. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Switch CI to emulator endpoints and isolated test projects
- Use production service credentials for every local emulator test
- Use the Firestore emulator for rules and app integration tests with synthetic data
- Identify test datasets, rules behavior and environment boundaries
Explanation
Correct Answer
D:
Identify test datasets, rules behavior and environment boundaries is the appropriate diagnostic because the observation—test activity creates real private user documents—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (developers test access rules only against the live production database) before the design is approved.
Incorrect Answers
A:
The alternative “Switch CI to emulator endpoints and isolated test projects” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, test activity creates real private user documents. The option “Identify test datasets, rules behavior and environment boundaries” instead addresses the requested root-cause evidence.
B:
Production credentials destroy the isolation expected from testing. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that simulations must avoid affecting production patient or responder data.
C:
The alternative “Use the Firestore emulator for rules and app integration tests with synthetic data” is target architecture selection; it does not establish why the observed path failed. In the reported observation, test activity creates real private user documents. The option “Identify test datasets, rules behavior and environment boundaries” instead addresses the requested root-cause evidence.
Question 396
At Large airline revenue group, the service account impersonation workload has a documented risk: automation assumes project Editor role is required to invoke one reporting job. The review found that permission audit shows callers can create keys and change unrelated resources. The architecture must also ensure that billing reads must use auditable least privilege. The team must deliver the approved control safely. Which deployment sequence is most appropriate?
- Grant narrowly scoped service-account impersonation and resource-specific reader roles
- Migrate callers to short-lived access tokens and disable downloaded keys
- Monitor impersonation events and newly created service account keys
- Use a downloaded project Owner key for every reporting job
Explanation
Correct Answer
B:
Migrate callers to short-lived access tokens and disable downloaded keys is a controlled means to introduce the approved architecture while meeting the requirement that billing reads must use auditable least privilege. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Grant narrowly scoped service-account impersonation and resource-specific reader roles” describes the chosen design, but not how it is introduced safely. In the reported observation, permission audit shows callers can create keys and change unrelated resources. The option “Migrate callers to short-lived access tokens and disable downloaded keys” instead addresses the requested controlled implementation.
C:
The alternative “Monitor impersonation events and newly created service account keys” addresses later monitoring rather than the actual controlled deployment. In the reported observation, permission audit shows callers can create keys and change unrelated resources. The option “Migrate callers to short-lived access tokens and disable downloaded keys” instead addresses the requested controlled implementation.
D:
Overprivileged permanent keys greatly increase compromise impact. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that billing reads must use auditable least privilege.
Question 397
Consider National rail passenger service and its disaster recovery runbook workload. The issue is that backup jobs report success but operational teams have never restored ticket data; the current observation is that DR rehearsal cannot identify who owns recovery steps. The team must ensure that tickets must be sold again within 30 minutes after a primary failure. The target architecture is approved; execution without disruption is the remaining decision. Which rollout action is best?
- Monitor drill age, ownership gaps and recovery time trends
- Increase the backup frequency and skip every restoration exercise
- Build owner-assigned DR procedures with restoration priorities and decision gates
- Schedule isolated recovery drills and sign off runbook changes
Explanation
Correct Answer
D:
Schedule isolated recovery drills and sign off runbook changes is a controlled means to introduce the approved architecture while meeting the requirement that tickets must be sold again within 30 minutes after a primary failure. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Monitor drill age, ownership gaps and recovery time trends” addresses later monitoring rather than the actual controlled deployment. In the reported observation, DR rehearsal cannot identify who owns recovery steps. The option “Schedule isolated recovery drills and sign off runbook changes” instead addresses the requested controlled implementation.
B:
Backup completion does not prove recoverability or an executable procedure. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that tickets must be sold again within 30 minutes after a primary failure.
C:
The alternative “Build owner-assigned DR procedures with restoration priorities and decision gates” describes the chosen design, but not how it is introduced safely. In the reported observation, DR rehearsal cannot identify who owns recovery steps. The option “Schedule isolated recovery drills and sign off runbook changes” instead addresses the requested controlled implementation.
Question 398
Medical translation nonprofit plans to update speech-to-text triage. Investigators found that audio samples vary in background noise and language code switching, consistent with the reported problem that clinics need transcripts of spoken patient questions and multilingual summaries. The response must satisfy the requirement that patient data must be handled under consent and short retention. The team needs an operations signal rather than another design or one-time test. What should it track?
- Measure word error rate and translation fidelity on consented samples
- Monitor failed transcriptions, language bias and data-deletion completions
- Use an appropriate speech recognition API with separate governed translation and summarization stages
- Use an image-labeling API as the only audio transcriber
Explanation
Correct Answer
B:
Monitor failed transcriptions, language bias and data-deletion completions reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (clinics need transcripts of spoken patient questions and multilingual summaries) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Measure word error rate and translation fidelity on consented samples” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, audio samples vary in background noise and language code switching. The option “Monitor failed transcriptions, language bias and data-deletion completions” instead addresses the requested ongoing operational assurance.
C:
The alternative “Use an appropriate speech recognition API with separate governed translation and summarization stages” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, audio samples vary in background noise and language code switching. The option “Monitor failed transcriptions, language bias and data-deletion completions” instead addresses the requested ongoing operational assurance.
D:
An image classification service does not provide speech transcripts. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that patient data must be handled under consent and short retention.
Question 399
Case study: Regional electric utility: production support handoff
Regional electric utility relies on production support handoff to deliver its operational commitments. The current architectural problem is that platform team deploys new observability agents without defining who handles alerts. The team has recorded this evidence: incident rehearsal finds metrics present but no pager owner. Any proposed response must preserve the requirement that grid control support must remain staffed around the clock.
Consider Regional electric utility and its production support handoff workload. The issue is that platform team deploys new observability agents without defining who handles alerts; the current observation is that incident rehearsal finds metrics present but no pager owner. The team must ensure that grid control support must remain staffed around the clock. Which acceptance test should demonstrate both protection against the failure and continued authorized service?
- Identify alert severities, runbook gaps and on-call ownership
- Introduce new alarms to a trained response cohort with simulated pages
- Enable thousands of pages with no routing or training
- Trigger a critical service alert and confirm correct acknowledgement and escalation
Explanation
Correct Answer
D:
Trigger a critical service alert and confirm correct acknowledgement and escalation is a direct acceptance test of the path implicated by incident rehearsal finds metrics present but no pager owner. It checks that the original risk (platform team deploys new observability agents without defining who handles alerts) has actually been controlled and tests that permitted operations still meet the requirement that grid control support must remain staffed around the clock.
Incorrect Answers
A:
The alternative “Identify alert severities, runbook gaps and on-call ownership” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, incident rehearsal finds metrics present but no pager owner. The option “Trigger a critical service alert and confirm correct acknowledgement and escalation” instead addresses the requested acceptance verification.
B:
The alternative “Introduce new alarms to a trained response cohort with simulated pages” documents change execution but not its operational acceptance result. In the reported observation, incident rehearsal finds metrics present but no pager owner. The option “Trigger a critical service alert and confirm correct acknowledgement and escalation” instead addresses the requested acceptance verification.
C:
Unowned alert volume does not create actionable operations. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that grid control support must remain staffed around the clock.
Question 400
At Digital archive service, the object version recovery workload has a documented risk: a script deleted storage objects and replication copied the deletions to the only backup. The review found that restore exercise shows no retained noncurrent version after replication. The architecture must also ensure that a contractual RPO requires recovery from mistaken deletes for 45 days. What enduring Google Cloud design should the team choose now that the failure mode is understood?
- Use versioning plus protected retention in a separately controlled recovery bucket
- Monitor retention-policy changes and recoverability of sampled objects
- Trace versioning, retention, replication and administrator delete permissions
- Set lifecycle to delete every previous generation immediately
Explanation
Correct Answer
A:
Use versioning plus protected retention in a separately controlled recovery bucket targets the underlying issue (a script deleted storage objects and replication copied the deletions to the only backup) rather than merely reporting symptoms. It also preserves the required outcome (a contractual RPO requires recovery from mistaken deletes for 45 days), which a target-state design must satisfy.
Incorrect Answers
B:
The alternative “Monitor retention-policy changes and recoverability of sampled objects” measures results without defining the preventive design now required. In the reported observation, restore exercise shows no retained noncurrent version after replication. The option “Use versioning plus protected retention in a separately controlled recovery bucket” instead addresses the requested architecture selection.
C:
The alternative “Trace versioning, retention, replication and administrator delete permissions” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, restore exercise shows no retained noncurrent version after replication. The option “Use versioning plus protected retention in a separately controlled recovery bucket” instead addresses the requested architecture selection.
D:
Immediate deletion removes the very recovery history required. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that a contractual RPO requires recovery from mistaken deletes for 45 days.