Google Professional Cloud Architect Practice Test 46
Question 450
At Public library consortium, the Google Cloud design for digital borrowing portal is affected because the proposed cloud rebuild treats video and catalog traffic as one workload. A review found that access logs show evening video bursts while catalog reservations require strict consistency. The proposed response must account for the requirement that reserving a scarce book must never succeed twice. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?
- Separate catalog transaction SLOs from media delivery and licensing costs
- Cut over media browsing first and migrate reservations after replay and integrity testing
- Store the unique-book counter in a stale CDN cache as the system of record
- Choose strongly consistent reservation storage with cacheable media delivery isolated from checkout
Explanation
Correct Answer
A:
Separate catalog transaction SLOs from media delivery and licensing costs is the appropriate diagnostic because the observation—access logs show evening video bursts while catalog reservations require strict consistency—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (the proposed cloud rebuild treats video and catalog traffic as one workload) before the design is approved.
Incorrect Answers
B:
The alternative “Cut over media browsing first and migrate reservations after replay and integrity testing” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, access logs show evening video bursts while catalog reservations require strict consistency. The option “Separate catalog transaction SLOs from media delivery and licensing costs” instead addresses the requested root-cause evidence.
C:
An edge cache cannot enforce atomic reservation updates. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that reserving a scarce book must never succeed twice.
D:
The alternative “Choose strongly consistent reservation storage with cacheable media delivery isolated from checkout” is target architecture selection; it does not establish why the observed path failed. In the reported observation, access logs show evening video bursts while catalog reservations require strict consistency. The option “Separate catalog transaction SLOs from media delivery and licensing costs” instead addresses the requested root-cause evidence.
Question 451
Consider Telecom customer portal and its Google Cloud SDK workload identity workload. The issue is that a deployment script has a static JSON key checked into a Git repository; the current observation is that commit scan reveals key reuse across three build agents. The team must ensure that deployments need constrained short-lived credentials. The target architecture is approved; execution without disruption is the remaining decision. Which rollout action is best?
- Transition build jobs to federation and revoke leaked keys
- Monitor federation changes and unexpected credential usage
- Use Workload Identity Federation with constrained provider attributes
- Copy the static key into the CI variable store without revoking it
Explanation
Correct Answer
A:
Transition build jobs to federation and revoke leaked keys is a controlled means to introduce the approved architecture while meeting the requirement that deployments need constrained short-lived credentials. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
The alternative “Monitor federation changes and unexpected credential usage” addresses later monitoring rather than the actual controlled deployment. In the reported observation, commit scan reveals key reuse across three build agents. The option “Transition build jobs to federation and revoke leaked keys” instead addresses the requested controlled implementation.
C:
The alternative “Use Workload Identity Federation with constrained provider attributes” describes the chosen design, but not how it is introduced safely. In the reported observation, commit scan reveals key reuse across three build agents. The option “Transition build jobs to federation and revoke leaked keys” instead addresses the requested controlled implementation.
D:
Relocating the leaked credential does not eliminate its misuse risk. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that deployments need constrained short-lived credentials.
Question 452
Case study: Community telehealth provider: clinical deployment training
Community telehealth provider relies on clinical deployment training to deliver its operational commitments. The current architectural problem is that a platform modernization plan assigns unfamiliar GKE on-call duties without staff enablement. The team has recorded this evidence: postmortems show alerts ignored because responders lack cluster permissions. Any proposed response must preserve the requirement that patient scheduling must be supported around the clock.
At Community telehealth provider, the Google Cloud design for clinical deployment training is affected because a platform modernization plan assigns unfamiliar GKE on-call duties without staff enablement. A review found that postmortems show alerts ignored because responders lack cluster permissions. The proposed response must account for the requirement that patient scheduling must be supported around the clock. A deployment ticket has been closed. What direct evidence would justify solution signoff?
- Run a simulated critical incident and verify correct escalation and resolution
- Assess team skills, access gaps and incident handoff requirements
- Train a pilot response rotation and rehearse common failures
- Give production Owner to everyone as an alternative to training
Explanation
Correct Answer
A:
Run a simulated critical incident and verify correct escalation and resolution is a direct acceptance test of the path implicated by postmortems show alerts ignored because responders lack cluster permissions. It checks that the original risk (a platform modernization plan assigns unfamiliar GKE on-call duties without staff enablement) has actually been controlled and tests that permitted operations still meet the requirement that patient scheduling must be supported around the clock.
Incorrect Answers
B:
The alternative “Assess team skills, access gaps and incident handoff requirements” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, postmortems show alerts ignored because responders lack cluster permissions. The option “Run a simulated critical incident and verify correct escalation and resolution” instead addresses the requested acceptance verification.
C:
The alternative “Train a pilot response rotation and rehearse common failures” documents change execution but not its operational acceptance result. In the reported observation, postmortems show alerts ignored because responders lack cluster permissions. The option “Run a simulated critical incident and verify correct escalation and resolution” instead addresses the requested acceptance verification.
D:
Broad privilege does not create operational competence. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that patient scheduling must be supported around the clock.
Question 453
Case study: National airport regulator: programmatic audit exports
National airport regulator relies on programmatic audit exports to deliver its operational commitments. The current architectural problem is that a Python client uses user ADC with project Owner and downloads more logs than needed. The team has recorded this evidence: code review finds broad filterless audit queries. Any proposed response must preserve the requirement that regulator requires a bounded report for one certified airport.
The programmatic audit exports environment at National airport regulator faces this issue: a Python client uses user ADC with project Owner and downloads more logs than needed. Supporting evidence shows that code review finds broad filterless audit queries. The architect must preserve the requirement that regulator requires a bounded report for one certified airport. Which migration or rollout step best manages risk, dependencies and reversibility?
- Monitor access scope changes and missing export windows
- Deploy export as an audited scheduled job with bounded destination
- Run unfiltered organization-wide log downloads with superadmin credentials
- Use scoped service identity and paginated filtered API requests
Explanation
Correct Answer
B:
Deploy export as an audited scheduled job with bounded destination is a controlled means to introduce the approved architecture while meeting the requirement that regulator requires a bounded report for one certified airport. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Monitor access scope changes and missing export windows” addresses later monitoring rather than the actual controlled deployment. In the reported observation, code review finds broad filterless audit queries. The option “Deploy export as an audited scheduled job with bounded destination” instead addresses the requested controlled implementation.
C:
Overbroad access and exports exceed the audit's authorized scope. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that regulator requires a bounded report for one certified airport.
D:
The alternative “Use scoped service identity and paginated filtered API requests” describes the chosen design, but not how it is introduced safely. In the reported observation, code review finds broad filterless audit queries. The option “Deploy export as an audited scheduled job with bounded destination” instead addresses the requested controlled implementation.
Question 454
Healthcare workflow vendor plans to update model-data residency. Investigators found that architecture diagram shows document prompts cross an international boundary, consistent with the reported problem that a generative AI workflow proposes calling a model endpoint in a prohibited region. The response must satisfy the requirement that health records must stay in their legally allowed data locations. The design review is over and production introduction is next. Which action is the best fit?
- Pilot regional model routing with private data pipelines and disabled unapproved exports
- Assume encryption during transfer makes an illegal cross-border export compliant
- Monitor model endpoint region changes and prompt storage controls
- Choose approved region-specific AI processing with enforceable data-access restrictions
Explanation
Correct Answer
A:
Pilot regional model routing with private data pipelines and disabled unapproved exports is a controlled means to introduce the approved architecture while meeting the requirement that health records must stay in their legally allowed data locations. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
Encryption does not itself satisfy geographic processing restrictions. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that health records must stay in their legally allowed data locations.
C:
The alternative “Monitor model endpoint region changes and prompt storage controls” addresses later monitoring rather than the actual controlled deployment. In the reported observation, architecture diagram shows document prompts cross an international boundary. The option “Pilot regional model routing with private data pipelines and disabled unapproved exports” instead addresses the requested controlled implementation.
D:
The alternative “Choose approved region-specific AI processing with enforceable data-access restrictions” describes the chosen design, but not how it is introduced safely. In the reported observation, architecture diagram shows document prompts cross an international boundary. The option “Pilot regional model routing with private data pipelines and disabled unapproved exports” instead addresses the requested controlled implementation.
Question 455
At Municipal tax office, the database migration testing workload has a documented risk: an automated migration passes row counts even though currency fields lose decimal precision. The review found that comparison shows several tax invoices differ by one cent after import. The architecture must also ensure that legal tax computations require exact financial arithmetic. Which post-change test most reliably distinguishes a functioning control from a merely successful installation?
- Compare cents and aggregates for individual invoices before cutover
- Apply migration fixes to a representative historical subset first
- Accept equal row count as proof that amounts are unchanged
- Inspect source column types, transformation rules and reconciliation coverage
Explanation
Correct Answer
A:
Compare cents and aggregates for individual invoices before cutover is a direct acceptance test of the path implicated by comparison shows several tax invoices differ by one cent after import. It checks that the original risk (an automated migration passes row counts even though currency fields lose decimal precision) has actually been controlled and tests that permitted operations still meet the requirement that legal tax computations require exact financial arithmetic.
Incorrect Answers
B:
The alternative “Apply migration fixes to a representative historical subset first” documents change execution but not its operational acceptance result. In the reported observation, comparison shows several tax invoices differ by one cent after import. The option “Compare cents and aggregates for individual invoices before cutover” instead addresses the requested acceptance verification.
C:
Row totals cannot detect corrupted financial values. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that legal tax computations require exact financial arithmetic.
D:
The alternative “Inspect source column types, transformation rules and reconciliation coverage” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, comparison shows several tax invoices differ by one cent after import. The option “Compare cents and aggregates for individual invoices before cutover” instead addresses the requested acceptance verification.
Question 456
At Municipal permit office, the digital permit filing workload has a documented risk: stakeholders propose a simple document store without cross-department approval traceability. The review found that a discovery workshop finds six approval signatures and statutory retention deadlines. The architecture must also ensure that citizens must see accurate permit status across agencies. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Document approval workflow, record lifecycle, access roles and integration requirements
- Replace all human approvals with a single anonymous automated approval
- Phase department onboarding with dual reporting and reconciliation
- Use an auditable workflow with durable state transitions and immutable original attachments
Explanation
Correct Answer
A:
Document approval workflow, record lifecycle, access roles and integration requirements is the appropriate diagnostic because the observation—a discovery workshop finds six approval signatures and statutory retention deadlines—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (stakeholders propose a simple document store without cross-department approval traceability) before the design is approved.
Incorrect Answers
B:
An unaccountable shortcut cannot satisfy multi-agency statutory approval. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that citizens must see accurate permit status across agencies.
C:
The alternative “Phase department onboarding with dual reporting and reconciliation” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, a discovery workshop finds six approval signatures and statutory retention deadlines. The option “Document approval workflow, record lifecycle, access roles and integration requirements” instead addresses the requested root-cause evidence.
D:
The alternative “Use an auditable workflow with durable state transitions and immutable original attachments” is target architecture selection; it does not establish why the observed path failed. In the reported observation, a discovery workshop finds six approval signatures and statutory retention deadlines. The option “Document approval workflow, record lifecycle, access roles and integration requirements” instead addresses the requested root-cause evidence.
Question 457
At Regional trucking marketplace, the custom business metrics workload has a documented risk: application metrics show 200 responses even as delivery confirmations are silently dropped. The review found that business reconciliation finds missing delivery events despite healthy pods. The architecture must also ensure that the service must confirm each accepted shipment within five minutes. 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 only VM CPU to measure whether shipments were delivered
- Drop a synthetic event and ensure its missing completion alerts
- Track unconfirmed shipments and processing delay by customer cohort
- Compare infrastructure telemetry with event-level customer outcome metrics
- Exclude the affected dependency from all future tests and incident metrics to simplify reporting
- Publish business delivery-success metrics and SLOs with trace correlation
Explanation
Correct Answers
B:
Drop a synthetic event and ensure its missing completion alerts is a direct acceptance test of the path implicated by business reconciliation finds missing delivery events despite healthy pods. It checks that the original risk (application metrics show 200 responses even as delivery confirmations are silently dropped) has actually been controlled and tests that permitted operations still meet the requirement that the service must confirm each accepted shipment within five minutes. It supplies the separate post-change acceptance result requested.
C:
Track unconfirmed shipments and processing delay by customer cohort reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (application metrics show 200 responses even as delivery confirmations are silently dropped) rather than treating the first successful test as permanent assurance. It supplies the ongoing observation requested.
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. It supplies the pre-design diagnostic evidence requested.
Incorrect Answers
A:
Healthy CPU is not evidence of successful business transactions. It cannot satisfy the required evidence stages.
E:
Omitting the relevant dependency from testing and monitoring would hide, not correct, recurrence of the failure. In particular, the observed issue was: business reconciliation finds missing delivery events despite healthy pods.
F:
Designing custom business metrics addresses the root cause, but this specific three-part question asks for evidence to diagnose, accept and continuously verify the response to application metrics show 200 responses even as delivery confirmations are silently dropped, not another design proposal.
Question 458
Consider International sports league and its video storage tiers workload. The issue is that all raw broadcasts remain in premium storage though almost never retrieved; the current observation is that access report shows 94% of footage is only viewed once per year. The team must ensure that rights owners require published clips to stay fast while raw footage is protected. Which acceptance test should demonstrate both protection against the failure and continued authorized service?
- Retrieve a full legacy match and verify rights, checksum and latency expectation
- Classify object hot/cold access patterns, retention and retrieval cost
- Migrate aged objects after permission and retrieval-time validation
- Move the currently streaming clips into long-retrieval archives unconditionally
Explanation
Correct Answer
A:
Retrieve a full legacy match and verify rights, checksum and latency expectation is a direct acceptance test of the path implicated by access report shows 94% of footage is only viewed once per year. It checks that the original risk (all raw broadcasts remain in premium storage though almost never retrieved) has actually been controlled and tests that permitted operations still meet the requirement that rights owners require published clips to stay fast while raw footage is protected.
Incorrect Answers
B:
The alternative “Classify object hot/cold access patterns, retention and retrieval cost” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, access report shows 94% of footage is only viewed once per year. The option “Retrieve a full legacy match and verify rights, checksum and latency expectation” instead addresses the requested acceptance verification.
C:
The alternative “Migrate aged objects after permission and retrieval-time validation” documents change execution but not its operational acceptance result. In the reported observation, access report shows 94% of footage is only viewed once per year. The option “Retrieve a full legacy match and verify rights, checksum and latency expectation” instead addresses the requested acceptance verification.
D:
Cold retrieval economics and latency do not fit hot video playback. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that rights owners require published clips to stay fast while raw footage is protected.
Question 459
At Municipal environmental sensors, the streaming pipeline deployment workload has a documented risk: operators change sensor parsers directly in production and corrupt previously valid samples. The review found that new parser interprets temperature units differently from prior version. The architecture must also ensure that environmental alerts must preserve accurate measurements. The team must deliver the approved control safely. Which deployment sequence is most appropriate?
- Treat all sensor readings as degrees Celsius regardless of source metadata
- Define versioned schemas and stable transformation contracts
- Watch schema errors and suspicious unit-distribution changes
- Deploy new parsers in shadow mode and compare to existing pipeline
Explanation
Correct Answer
D:
Deploy new parsers in shadow mode and compare to existing pipeline is a controlled means to introduce the approved architecture while meeting the requirement that environmental alerts must preserve accurate measurements. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
Ignoring units changes physical meaning of measurements. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that environmental alerts must preserve accurate measurements.
B:
The alternative “Define versioned schemas and stable transformation contracts” describes the chosen design, but not how it is introduced safely. In the reported observation, new parser interprets temperature units differently from prior version. The option “Deploy new parsers in shadow mode and compare to existing pipeline” instead addresses the requested controlled implementation.
C:
The alternative “Watch schema errors and suspicious unit-distribution changes” addresses later monitoring rather than the actual controlled deployment. In the reported observation, new parser interprets temperature units differently from prior version. The option “Deploy new parsers in shadow mode and compare to existing pipeline” instead addresses the requested controlled implementation.
Question 460
Regional airline plans to update crew roster API. Investigators found that failure logs show read-only standby exists but application uses only one endpoint, consistent with the reported problem that a database primary restart causes regional crews to lose schedules for an entire shift. The response must satisfy the requirement that dispatch must read the last approved crew plan during recovery. The design review is over and production introduction is next. Which action is the best fit?
- Use high-availability database failover and a validated read-only contingency view
- Stage client reconnection and crew-cache refresh before database switchover
- Track replication lag, failover times and stale roster warnings
- Point every client to an unreplicated local file as the only source
Explanation
Correct Answer
B:
Stage client reconnection and crew-cache refresh before database switchover is a controlled means to introduce the approved architecture while meeting the requirement that dispatch must read the last approved crew plan during recovery. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Use high-availability database failover and a validated read-only contingency view” describes the chosen design, but not how it is introduced safely. In the reported observation, failure logs show read-only standby exists but application uses only one endpoint. The option “Stage client reconnection and crew-cache refresh before database switchover” instead addresses the requested controlled implementation.
C:
The alternative “Track replication lag, failover times and stale roster warnings” addresses later monitoring rather than the actual controlled deployment. In the reported observation, failure logs show read-only standby exists but application uses only one endpoint. The option “Stage client reconnection and crew-cache refresh before database switchover” instead addresses the requested controlled implementation.
D:
An uncontrolled copy can yield inconsistent safety-critical rosters. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that dispatch must read the last approved crew plan during recovery.