Google Professional Cloud Architect Practice Test 55
Question 540
At Automotive safety modeling startup, the Google Cloud design for reinforcement model evaluation is affected because engineering wants to deploy a new model before proving corner-case behavior. A review found that evaluation report covers average accuracy but no rare safety-critical maneuvers. The proposed response must account for the requirement that safety review requires rigorous offline evaluation and rollback. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?
- Replay corner-case simulation corpus and verify failure thresholds before release
- Design model lifecycle gates with offline evaluation and isolated acceptance
- Approve the model solely because aggregate accuracy rose one percent
- Track model decision drift and post-release safety exceptions
Explanation
Correct Answer
D:
Track model decision drift and post-release safety exceptions reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (engineering wants to deploy a new model before proving corner-case behavior) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Replay corner-case simulation corpus and verify failure thresholds before release” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, evaluation report covers average accuracy but no rare safety-critical maneuvers. The option “Track model decision drift and post-release safety exceptions” instead addresses the requested ongoing operational assurance.
B:
The alternative “Design model lifecycle gates with offline evaluation and isolated acceptance” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, evaluation report covers average accuracy but no rare safety-critical maneuvers. The option “Track model decision drift and post-release safety exceptions” instead addresses the requested ongoing operational assurance.
C:
Mean accuracy can hide unacceptable safety-regression tails. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that safety review requires rigorous offline evaluation and rollback.
Question 541
International renewable energy fund plans to update cost governance of abandoned environments. Investigators found that billing export shows idle infrastructure without current cost owner, consistent with the reported problem that unused development clusters persist after quarter-end project closures. The response must satisfy the requirement that audit requirements retain records but not unused compute. The design review is over and production introduction is next. Which action is the best fit?
- Delete every project including protected regulatory evidence without review
- Set lifecycle policies and project budgets with approved archival before deletion
- Run owner-approved cleanup on tagged nonproduction environments
- Watch stale projects, budget alerts and reactivated resources
Explanation
Correct Answer
C:
Run owner-approved cleanup on tagged nonproduction environments is a controlled means to introduce the approved architecture while meeting the requirement that audit requirements retain records but not unused compute. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
Unreviewed cleanup can destroy necessary retained records. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that audit requirements retain records but not unused compute.
B:
The alternative “Set lifecycle policies and project budgets with approved archival before deletion” describes the chosen design, but not how it is introduced safely. In the reported observation, billing export shows idle infrastructure without current cost owner. The option “Run owner-approved cleanup on tagged nonproduction environments” instead addresses the requested controlled implementation.
D:
The alternative “Watch stale projects, budget alerts and reactivated resources” addresses later monitoring rather than the actual controlled deployment. In the reported observation, billing export shows idle infrastructure without current cost owner. The option “Run owner-approved cleanup on tagged nonproduction environments” instead addresses the requested controlled implementation.
Question 542
Regional trucking marketplace plans to update custom business metrics. Investigators found that business reconciliation finds missing delivery events despite healthy pods, consistent with the reported problem that application metrics show 200 responses even as delivery confirmations are silently dropped. The response must satisfy the requirement that the service must confirm each accepted shipment within five minutes. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?
- Publish business delivery-success metrics and SLOs with trace correlation
- Instrument the critical workflow and pilot actionable alerting
- Use only VM CPU to measure whether shipments were delivered
- Compare infrastructure telemetry with event-level customer outcome metrics
Explanation
Correct Answer
D:
Compare infrastructure telemetry with event-level customer outcome metrics is the appropriate diagnostic because the observation—business reconciliation finds missing delivery events despite healthy pods—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (application metrics show 200 responses even as delivery confirmations are silently dropped) before the design is approved.
Incorrect Answers
A:
The alternative “Publish business delivery-success metrics and SLOs with trace correlation” is target architecture selection; it does not establish why the observed path failed. In the reported observation, business reconciliation finds missing delivery events despite healthy pods. The option “Compare infrastructure telemetry with event-level customer outcome metrics” instead addresses the requested root-cause evidence.
B:
The alternative “Instrument the critical workflow and pilot actionable alerting” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, business reconciliation finds missing delivery events despite healthy pods. The option “Compare infrastructure telemetry with event-level customer outcome metrics” instead addresses the requested root-cause evidence.
C:
Healthy CPU is not evidence of successful business transactions. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that the service must confirm each accepted shipment within five minutes.
Question 543
The streaming pipeline deployment environment at Municipal environmental sensors faces this issue: operators change sensor parsers directly in production and corrupt previously valid samples. Supporting evidence shows that new parser interprets temperature units differently from prior version. The architect must preserve the requirement that environmental alerts must preserve accurate measurements. What test must pass before the business accepts the remediated architecture?
- Deploy new parsers in shadow mode and compare to existing pipeline
- Treat all sensor readings as degrees Celsius regardless of source metadata
- Replay mixed unit messages and prove normalized readings match expected values
- Review schema fields, unit provenance and historical interpretation
Explanation
Correct Answer
C:
Replay mixed unit messages and prove normalized readings match expected values is a direct acceptance test of the path implicated by new parser interprets temperature units differently from prior version. It checks that the original risk (operators change sensor parsers directly in production and corrupt previously valid samples) has actually been controlled and tests that permitted operations still meet the requirement that environmental alerts must preserve accurate measurements.
Incorrect Answers
A:
The alternative “Deploy new parsers in shadow mode and compare to existing pipeline” documents change execution but not its operational acceptance result. In the reported observation, new parser interprets temperature units differently from prior version. The option “Replay mixed unit messages and prove normalized readings match expected values” instead addresses the requested acceptance verification.
B:
Ignoring units changes physical meaning of measurements. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that environmental alerts must preserve accurate measurements.
D:
The alternative “Review schema fields, unit provenance and historical interpretation” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, new parser interprets temperature units differently from prior version. The option “Replay mixed unit messages and prove normalized readings match expected values” instead addresses the requested acceptance verification.
Question 544
At Clinical imaging archive, the large immutable scans workload has a documented risk: imaging staff need object retention but architects chose a file share for infrequently accessed studies. The review found that inventory shows petabytes of immutable DICOM objects with annual reads. The architecture must also ensure that specific clinical records have mandatory retention and legal hold. Select THREE evidence activities to cover (1) diagnosis before design, (2) direct post-change acceptance, and (3) continued operational monitoring. Which THREE fit those stages?
- Use Cloud Storage with appropriate storage classes and retention policies for immutable objects
- Restore random samples and confirm legal hold denies unauthorized deletions
- Review object access, retrieval latency and regulated retention classes
- Use only an ephemeral instance boot disk for the master archive
- Monitor lifecycle transitions, retention exceptions and retrieval charges
- Exclude the affected dependency from all future tests and incident metrics to simplify reporting
Explanation
Correct Answers
B:
Restore random samples and confirm legal hold denies unauthorized deletions is a direct acceptance test of the path implicated by inventory shows petabytes of immutable DICOM objects with annual reads. It checks that the original risk (imaging staff need object retention but architects chose a file share for infrequently accessed studies) has actually been controlled and tests that permitted operations still meet the requirement that specific clinical records have mandatory retention and legal hold. It supplies the separate post-change acceptance result requested.
C:
Review object access, retrieval latency and regulated retention classes is the appropriate diagnostic because the observation—inventory shows petabytes of immutable DICOM objects with annual reads—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (imaging staff need object retention but architects chose a file share for infrequently accessed studies) before the design is approved. It supplies the pre-design diagnostic evidence requested.
E:
Monitor lifecycle transitions, retention exceptions and retrieval charges reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (imaging staff need object retention but architects chose a file share for infrequently accessed studies) rather than treating the first successful test as permanent assurance. It supplies the ongoing observation requested.
Incorrect Answers
A:
Designing large immutable scans addresses the root cause, but this specific three-part question asks for evidence to diagnose, accept and continuously verify the response to imaging staff need object retention but architects chose a file share for infrequently accessed studies, not another design proposal.
D:
Boot disks lack appropriate durable retention and lifecycle governance. It cannot satisfy the required evidence stages.
F:
Omitting the relevant dependency from testing and monitoring would hide, not correct, recurrence of the failure. In particular, the observed issue was: inventory shows petabytes of immutable DICOM objects with annual reads.
Question 545
At Manufacturing telemetry provider, the private partner services workload has a documented risk: partners traverse the public internet to reach an internal metrics API. The review found that packet traces show traffic exposed through an unnecessary external load balancer. The architecture must also ensure that service access must be private and restricted to approved consumer networks. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Create a broad public IP allowlist for all partner subnets
- Map producer VPC, consumer networks and allowed endpoint semantics
- Use Private Service Connect for scoped private service consumption
- Cut over partners through approved endpoints and DNS changes in phases
Explanation
Correct Answer
B:
Map producer VPC, consumer networks and allowed endpoint semantics is the appropriate diagnostic because the observation—packet traces show traffic exposed through an unnecessary external load balancer—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (partners traverse the public internet to reach an internal metrics API) before the design is approved.
Incorrect Answers
A:
A public allowlist does not provide an intrinsically private service endpoint. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that service access must be private and restricted to approved consumer networks.
C:
The alternative “Use Private Service Connect for scoped private service consumption” is target architecture selection; it does not establish why the observed path failed. In the reported observation, packet traces show traffic exposed through an unnecessary external load balancer. The option “Map producer VPC, consumer networks and allowed endpoint semantics” instead addresses the requested root-cause evidence.
D:
The alternative “Cut over partners through approved endpoints and DNS changes in phases” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, packet traces show traffic exposed through an unnecessary external load balancer. The option “Map producer VPC, consumer networks and allowed endpoint semantics” instead addresses the requested root-cause evidence.
Question 546
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.
The API gateway migration environment at International automotive retailer faces this issue: third-party dealerships expect old JSON fields while a new service removes one required property. Supporting evidence shows that contract tests show older clients fail when the new revision is published. The architect must preserve the requirement that dealer ordering cannot require simultaneous client upgrades. Choose the architecture that resolves the documented weakness without breaching the operational constraint.
- Remove legacy fields immediately because the provider source code is updated
- Design backward-compatible API versioning and deprecation policy
- Identify required fields, version agreements and client deployment windows
- Track remaining old-client traffic and breaking-response failures
Explanation
Correct Answer
B:
Design backward-compatible API versioning and deprecation policy targets the underlying issue (third-party dealerships expect old JSON fields while a new service removes one required property) rather than merely reporting symptoms. It also preserves the required outcome (dealer ordering cannot require simultaneous client upgrades), which a target-state design must satisfy.
Incorrect Answers
A:
Client contracts are not automatically updated with server code. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that dealer ordering cannot require simultaneous client upgrades.
C:
The alternative “Identify required fields, version agreements and client deployment windows” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, contract tests show older clients fail when the new revision is published. The option “Design backward-compatible API versioning and deprecation policy” instead addresses the requested architecture selection.
D:
The alternative “Track remaining old-client traffic and breaking-response failures” measures results without defining the preventive design now required. In the reported observation, contract tests show older clients fail when the new revision is published. The option “Design backward-compatible API versioning and deprecation policy” instead addresses the requested architecture selection.
Question 547
At Mobile banking wallet, the Google Cloud design for payments rollback coordination is affected because CI tool can roll back app pods but cannot reverse a one-way database ledger migration. A review found that release plan contains no financial reconciliation procedure. The proposed response must account for the requirement that posted transactions cannot be duplicated or silently lost. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?
- Treat a code rollback as automatically reversing every committed financial transaction
- Test dual-version database support before deploying new billing code
- Map irreversible state updates and rollback versus forward-fix choices
- Design backward-compatible ledger migration and auditable compensation patterns
Explanation
Correct Answer
C:
Map irreversible state updates and rollback versus forward-fix choices is the appropriate diagnostic because the observation—release plan contains no financial reconciliation procedure—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (CI tool can roll back app pods but cannot reverse a one-way database ledger migration) before the design is approved.
Incorrect Answers
A:
Financial state changes need explicit reconciliation, not just application rollback. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that posted transactions cannot be duplicated or silently lost.
B:
The alternative “Test dual-version database support before deploying new billing code” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, release plan contains no financial reconciliation procedure. The option “Map irreversible state updates and rollback versus forward-fix choices” instead addresses the requested root-cause evidence.
D:
The alternative “Design backward-compatible ledger migration and auditable compensation patterns” is target architecture selection; it does not establish why the observed path failed. In the reported observation, release plan contains no financial reconciliation procedure. The option “Map irreversible state updates and rollback versus forward-fix choices” instead addresses the requested root-cause evidence.
Question 548
The field-research collection environment at Wildlife conservation nonprofit faces this issue: donor funding requires an inexpensive platform but volunteers collect sensitive species locations. Supporting evidence shows that team interviews identify intermittent connectivity and controlled-location access. The architect must preserve the requirement that precise nesting coordinates must remain inaccessible to public donors. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Publish exact endangered-species coordinates to prove collection completeness
- Watch stale devices, data-sharing grants and synchronization conflicts
- Validate conflicting offline edits and confirm public reports cannot expose nest coordinates
- Use offline-capable mobile capture with encrypted private storage and aggregated donor reports
Explanation
Correct Answer
B:
Watch stale devices, data-sharing grants and synchronization conflicts reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (donor funding requires an inexpensive platform but volunteers collect sensitive species locations) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
Sensitive location disclosure could enable poaching and defeat privacy requirements. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that precise nesting coordinates must remain inaccessible to public donors.
C:
The alternative “Validate conflicting offline edits and confirm public reports cannot expose nest coordinates” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, team interviews identify intermittent connectivity and controlled-location access. The option “Watch stale devices, data-sharing grants and synchronization conflicts” instead addresses the requested ongoing operational assurance.
D:
The alternative “Use offline-capable mobile capture with encrypted private storage and aggregated donor reports” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, team interviews identify intermittent connectivity and controlled-location access. The option “Watch stale devices, data-sharing grants and synchronization conflicts” instead addresses the requested ongoing operational assurance.
Question 549
Consider Multinational travel support service and its multilingual customer request assistant workload. The issue is that an architecture team confuses basic FAQ retrieval with an agent allowed to change reservations; the current observation is that requirements show ticket search and refund actions have different authorization obligations. The team must ensure that refunds require authenticated approval and audit. The target architecture is approved; execution without disruption is the remaining decision. Which rollout action is best?
- Deploy read-only answers first and then gated action flows
- Monitor action denials, groundedness and escalated human approvals
- Use a grounded search-based assistant and keep refund execution behind an authenticated tool policy
- Give every search result direct permission to execute refund APIs
Explanation
Correct Answer
A:
Deploy read-only answers first and then gated action flows is a controlled means to introduce the approved architecture while meeting the requirement that refunds require authenticated approval and audit. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
The alternative “Monitor action denials, groundedness and escalated human approvals” addresses later monitoring rather than the actual controlled deployment. In the reported observation, requirements show ticket search and refund actions have different authorization obligations. The option “Deploy read-only answers first and then gated action flows” instead addresses the requested controlled implementation.
C:
The alternative “Use a grounded search-based assistant and keep refund execution behind an authenticated tool policy” describes the chosen design, but not how it is introduced safely. In the reported observation, requirements show ticket search and refund actions have different authorization obligations. The option “Deploy read-only answers first and then gated action flows” instead addresses the requested controlled implementation.
D:
Retrieved text is untrusted input, not authorization. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that refunds require authenticated approval and audit.
Question 550
National health data exchange plans to update service risk prioritization. Investigators found that error-budget report shows clinical file import has the worst user impact, consistent with the reported problem that engineering spends most reliability effort on cosmetic dashboard errors while core clinical imports fail. The response must satisfy the requirement that clinical data delivery requires a time-bound recovery process. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?
- Choose the task with the largest number of low-impact tickets only
- Reallocate the next reliability work period with cross-team approval
- Prioritize operational improvements based on SLOs and measurable error budgets
- Quantify customer impact and SLO breaches by service criticality
Explanation
Correct Answer
D:
Quantify customer impact and SLO breaches by service criticality is the appropriate diagnostic because the observation—error-budget report shows clinical file import has the worst user impact—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (engineering spends most reliability effort on cosmetic dashboard errors while core clinical imports fail) before the design is approved.
Incorrect Answers
A:
Ticket volume is a poor substitute for consequence and SLO impact. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that clinical data delivery requires a time-bound recovery process.
B:
The alternative “Reallocate the next reliability work period with cross-team approval” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, error-budget report shows clinical file import has the worst user impact. The option “Quantify customer impact and SLO breaches by service criticality” instead addresses the requested root-cause evidence.
C:
The alternative “Prioritize operational improvements based on SLOs and measurable error budgets” is target architecture selection; it does not establish why the observed path failed. In the reported observation, error-budget report shows clinical file import has the worst user impact. The option “Quantify customer impact and SLO breaches by service criticality” instead addresses the requested root-cause evidence.