Google Professional Cloud Architect Practice Test 64
Question 630
At Public pension administrator, the Google Cloud design for database engine transition is affected because an old relational engine uses vendor-specific stored procedures that block a simple migration. A review found that assessment finds financial calculation logic embedded in triggers. The proposed response must account for the requirement that pension payouts require exact money arithmetic across historical backfills. Which controlled implementation should be used to preserve operational continuity during the change?
- Treat stored procedures as portable SQL without regression tests
- Plan staged conversion with verified query/procedure compatibility
- Track procedure error rates and unauthorized schema changes
- Use migration dry runs with immutable ledger snapshots and rollback
Explanation
Correct Answer
D:
Use migration dry runs with immutable ledger snapshots and rollback is a controlled means to introduce the approved architecture while meeting the requirement that pension payouts require exact money arithmetic across historical backfills. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
Vendor dialect and arithmetic differences can corrupt financial calculations. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that pension payouts require exact money arithmetic across historical backfills.
B:
The alternative “Plan staged conversion with verified query/procedure compatibility” describes the chosen design, but not how it is introduced safely. In the reported observation, assessment finds financial calculation logic embedded in triggers. The option “Use migration dry runs with immutable ledger snapshots and rollback” instead addresses the requested controlled implementation.
C:
The alternative “Track procedure error rates and unauthorized schema changes” addresses later monitoring rather than the actual controlled deployment. In the reported observation, assessment finds financial calculation logic embedded in triggers. The option “Use migration dry runs with immutable ledger snapshots and rollback” instead addresses the requested controlled implementation.
Question 631
AI satellite imagery group plans to update short-lived GPU inference. Investigators found that billing shows high GPU idle cost with short bursts of queued requests, consistent with the reported problem that the product team leaves GPU instances running overnight for occasional image classification. The response must satisfy the requirement that inference can tolerate several seconds of cold-start delay. The team needs an operations signal rather than another design or one-time test. What should it track?
- Reserve the largest GPU fleet permanently for infrequent requests
- Verify output equivalence through GPU scale-down and restart events
- Choose a scale-aware inference platform with workload-appropriate GPUs and queueing
- Monitor idle GPU spend, request latency and quota exhaustion
Explanation
Correct Answer
D:
Monitor idle GPU spend, request latency and quota exhaustion reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (the product team leaves GPU instances running overnight for occasional image classification) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
Always-on capacity wastes cost when demand is highly intermittent. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that inference can tolerate several seconds of cold-start delay.
B:
The alternative “Verify output equivalence through GPU scale-down and restart events” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, billing shows high GPU idle cost with short bursts of queued requests. The option “Monitor idle GPU spend, request latency and quota exhaustion” instead addresses the requested ongoing operational assurance.
C:
The alternative “Choose a scale-aware inference platform with workload-appropriate GPUs and queueing” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, billing shows high GPU idle cost with short bursts of queued requests. The option “Monitor idle GPU spend, request latency and quota exhaustion” instead addresses the requested ongoing operational assurance.
Question 632
At Urban public transport authority, the Google Cloud design for fare validation backend is affected because rush-hour taps overwhelm the settlement database even though fraud checks are light. A review found that histogram shows 8x peak events and lock waits on identical card records. The proposed response must account for the requirement that a transit pass must not be charged twice for one tap. A deployment ticket has been closed. What direct evidence would justify solution signoff?
- Introduce tap ingestion in station cohorts with controlled retry semantics
- Replay duplicated rush-hour tap IDs and reconcile exactly one charge per event
- Scale only the front-end web server while keeping the hot database lock
- Measure tap interarrival, hot-key contention and duplicate IDs
Explanation
Correct Answer
B:
Replay duplicated rush-hour tap IDs and reconcile exactly one charge per event is a direct acceptance test of the path implicated by histogram shows 8x peak events and lock waits on identical card records. It checks that the original risk (rush-hour taps overwhelm the settlement database even though fraud checks are light) has actually been controlled and tests that permitted operations still meet the requirement that a transit pass must not be charged twice for one tap.
Incorrect Answers
A:
The alternative “Introduce tap ingestion in station cohorts with controlled retry semantics” documents change execution but not its operational acceptance result. In the reported observation, histogram shows 8x peak events and lock waits on identical card records. The option “Replay duplicated rush-hour tap IDs and reconcile exactly one charge per event” instead addresses the requested acceptance verification.
C:
A larger front end does not remove the transactional bottleneck. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that a transit pass must not be charged twice for one tap.
D:
The alternative “Measure tap interarrival, hot-key contention and duplicate IDs” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, histogram shows 8x peak events and lock waits on identical card records. The option “Replay duplicated rush-hour tap IDs and reconcile exactly one charge per event” instead addresses the requested acceptance verification.
Question 633
The finops reserved capacity environment at National small-business bank faces this issue: leadership commits all compute to three-year reservations despite demand reduction plans. Supporting evidence shows that forecasts show the main batch system will retire within six months. The architect must preserve the requirement that reserved spend must not exceed expected future compute usage. Which migration or rollout step best manages risk, dependencies and reversibility?
- Choose commitments only for stable baseline needs and leave uncertain capacity flexible
- Apply bounded commitments after finance and engineering review
- Buy maximal three-year reservations for workloads scheduled for decommission
- Monitor commitment utilization and forecast changes
Explanation
Correct Answer
B:
Apply bounded commitments after finance and engineering review is a controlled means to introduce the approved architecture while meeting the requirement that reserved spend must not exceed expected future compute usage. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Choose commitments only for stable baseline needs and leave uncertain capacity flexible” describes the chosen design, but not how it is introduced safely. In the reported observation, forecasts show the main batch system will retire within six months. The option “Apply bounded commitments after finance and engineering review” instead addresses the requested controlled implementation.
C:
Long obligations can outlast the resource demand. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that reserved spend must not exceed expected future compute usage.
D:
The alternative “Monitor commitment utilization and forecast changes” addresses later monitoring rather than the actual controlled deployment. In the reported observation, forecasts show the main batch system will retire within six months. The option “Apply bounded commitments after finance and engineering review” instead addresses the requested controlled implementation.
Question 634
The energy-aware workload economics environment at Sustainable packaging manufacturer faces this issue: nightly noncritical reports run during peak electricity pricing even though deadline is the next afternoon. Supporting evidence shows that billing data shows batch energy and instance costs spike in fixed early hours. The architect must preserve the requirement that reports must be complete by 14:00, not in real time. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Terminate all reports to maximize energy savings
- Confirm reports complete by deadline and measure per-report spend
- Schedule nonurgent batch jobs in lower-cost windows subject to completion SLO
- Monitor deadline misses, cost and unexpected runtime expansion
Explanation
Correct Answer
D:
Monitor deadline misses, cost and unexpected runtime expansion reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (nightly noncritical reports run during peak electricity pricing even though deadline is the next afternoon) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
Zero processing fails the defined reporting objective. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that reports must be complete by 14:00, not in real time.
B:
The alternative “Confirm reports complete by deadline and measure per-report spend” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, billing data shows batch energy and instance costs spike in fixed early hours. The option “Monitor deadline misses, cost and unexpected runtime expansion” instead addresses the requested ongoing operational assurance.
C:
The alternative “Schedule nonurgent batch jobs in lower-cost windows subject to completion SLO” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, billing data shows batch energy and instance costs spike in fixed early hours. The option “Monitor deadline misses, cost and unexpected runtime expansion” instead addresses the requested ongoing operational assurance.
Question 635
At International hotel chain, the Google Cloud design for central incident notification API is affected because operations migrates a notification service before updating caller authentication and message retry rules. A review found that test customers see duplicate room-change notifications. The proposed response must account for the requirement that customer booking updates must remain unique and attributable. Which controlled implementation should be used to preserve operational continuity during the change?
- Monitor retry storms and unexpected duplicate IDs
- Design idempotent notification delivery with scoped API identities
- Disable all retries and discard messages when the first send fails
- Move partners through versioned API deployment with replayable messages
Explanation
Correct Answer
D:
Move partners through versioned API deployment with replayable messages is a controlled means to introduce the approved architecture while meeting the requirement that customer booking updates must remain unique and attributable. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Monitor retry storms and unexpected duplicate IDs” addresses later monitoring rather than the actual controlled deployment. In the reported observation, test customers see duplicate room-change notifications. The option “Move partners through versioned API deployment with replayable messages” instead addresses the requested controlled implementation.
B:
The alternative “Design idempotent notification delivery with scoped API identities” describes the chosen design, but not how it is introduced safely. In the reported observation, test customers see duplicate room-change notifications. The option “Move partners through versioned API deployment with replayable messages” instead addresses the requested controlled implementation.
C:
At-most-once loss does not meet delivery commitments. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that customer booking updates must remain unique and attributable.
Question 636
The incident root-cause analysis environment at Global logistics company faces this issue: operators replaced pods repeatedly after timeouts without inspecting a shared cache bottleneck. Supporting evidence shows that distributed traces show requests stall on a single Redis connection pool. The architect must preserve the requirement that orders must remain available while the root cause is established. What test must pass before the business accepts the remediated architecture?
- Correlate traces, dependency saturation, application revisions and failure start time
- Keep restarting every failing pod while ignoring the saturated shared service
- Deploy bounded pool change and fallback in a canary service
- Run load through the cache failure condition and validate error reduction
Explanation
Correct Answer
D:
Run load through the cache failure condition and validate error reduction is a direct acceptance test of the path implicated by distributed traces show requests stall on a single Redis connection pool. It checks that the original risk (operators replaced pods repeatedly after timeouts without inspecting a shared cache bottleneck) has actually been controlled and tests that permitted operations still meet the requirement that orders must remain available while the root cause is established.
Incorrect Answers
A:
The alternative “Correlate traces, dependency saturation, application revisions and failure start time” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, distributed traces show requests stall on a single Redis connection pool. The option “Run load through the cache failure condition and validate error reduction” instead addresses the requested acceptance verification.
B:
Restarting consumers cannot remove the persistent shared dependency bottleneck. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that orders must remain available while the root cause is established.
C:
The alternative “Deploy bounded pool change and fallback in a canary service” documents change execution but not its operational acceptance result. In the reported observation, distributed traces show requests stall on a single Redis connection pool. The option “Run load through the cache failure condition and validate error reduction” instead addresses the requested acceptance verification.
Question 637
At City parking payment app, the payment token audit workload has a documented risk: service records full PAN in debug logs while application database is tokenized. The review found that log sample includes unmasked card numbers in error traces. The architecture must also ensure that payment operations require minimized log retention and incident-ready evidence. What enduring Google Cloud design should the team choose now that the failure mode is understood?
- Trace cardholder paths through logging, traces and batch exports
- Remove PAN from telemetry and apply scoped tokenization and log redaction
- Use TLS on log transport and keep full card numbers indefinitely
- Monitor new PAN detections and changes in logging pipeline
Explanation
Correct Answer
B:
Remove PAN from telemetry and apply scoped tokenization and log redaction targets the underlying issue (service records full PAN in debug logs while application database is tokenized) rather than merely reporting symptoms. It also preserves the required outcome (payment operations require minimized log retention and incident-ready evidence), which a target-state design must satisfy.
Incorrect Answers
A:
The alternative “Trace cardholder paths through logging, traces and batch exports” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, log sample includes unmasked card numbers in error traces. The option “Remove PAN from telemetry and apply scoped tokenization and log redaction” instead addresses the requested architecture selection.
C:
Transport encryption alone does not minimize sensitive logged content. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that payment operations require minimized log retention and incident-ready evidence.
D:
The alternative “Monitor new PAN detections and changes in logging pipeline” measures results without defining the preventive design now required. In the reported observation, log sample includes unmasked card numbers in error traces. The option “Remove PAN from telemetry and apply scoped tokenization and log redaction” instead addresses the requested architecture selection.
Question 638
Consider Hospital payments administrator and its database point-in-time recovery workload. The issue is that an operator accidentally ran a broad UPDATE against the claims settlement database; the current observation is that audit shows thousands of records changed before detection. The team must ensure that finance requires restoration to immediately before the erroneous transaction. The change committee needs to understand the current system rather than install a fix yet. What should it do?
- Set continuous backup/PITR where supported and segregated recovery permissions
- Enable recovery policy and rehearse isolated restore before relying on it
- Restore from a week-old cold snapshot and overwrite new valid payments blindly
- Identify commit timestamps, backup settings and business replay obligations
Explanation
Correct Answer
D:
Identify commit timestamps, backup settings and business replay obligations is the appropriate diagnostic because the observation—audit shows thousands of records changed before detection—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (an operator accidentally ran a broad UPDATE against the claims settlement database) before the design is approved.
Incorrect Answers
A:
The alternative “Set continuous backup/PITR where supported and segregated recovery permissions” is target architecture selection; it does not establish why the observed path failed. In the reported observation, audit shows thousands of records changed before detection. The option “Identify commit timestamps, backup settings and business replay obligations” instead addresses the requested root-cause evidence.
B:
The alternative “Enable recovery policy and rehearse isolated restore before relying on it” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, audit shows thousands of records changed before detection. The option “Identify commit timestamps, backup settings and business replay obligations” instead addresses the requested root-cause evidence.
C:
An old snapshot without transaction reconciliation can discard legitimate payments. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that finance requires restoration to immediately before the erroneous transaction.
Question 639
At Vehicle warranty analytics company, the Windows compatibility hosting workload has a documented risk: a proprietary claims executable needs Windows COM objects not supported in Linux containers. The review found that vendor test fails on Linux libraries despite unchanged program behavior. The architecture must also ensure that temporary hosting must keep vendor support and monthly patch controls. Which post-change test most reliably distinguishes a functioning control from a merely successful installation?
- Create controlled images, migrate service identities and test rollback
- Inventory licensing, runtime dependencies and supported OS baseline
- Repackage the unchanged Windows binary into an Alpine Linux container
- Run the COM-dependent workflow and verify monthly patch recovery
Explanation
Correct Answer
D:
Run the COM-dependent workflow and verify monthly patch recovery is a direct acceptance test of the path implicated by vendor test fails on Linux libraries despite unchanged program behavior. It checks that the original risk (a proprietary claims executable needs Windows COM objects not supported in Linux containers) has actually been controlled and tests that permitted operations still meet the requirement that temporary hosting must keep vendor support and monthly patch controls.
Incorrect Answers
A:
The alternative “Create controlled images, migrate service identities and test rollback” documents change execution but not its operational acceptance result. In the reported observation, vendor test fails on Linux libraries despite unchanged program behavior. The option “Run the COM-dependent workflow and verify monthly patch recovery” instead addresses the requested acceptance verification.
B:
The alternative “Inventory licensing, runtime dependencies and supported OS baseline” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, vendor test fails on Linux libraries despite unchanged program behavior. The option “Run the COM-dependent workflow and verify monthly patch recovery” instead addresses the requested acceptance verification.
C:
Repackaging does not remove Windows-only executable dependencies. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that temporary hosting must keep vendor support and monthly patch controls.
Question 640
The multi-tenant object security environment at Legal case management SaaS faces this issue: valid user tokens can access case files belonging to other law firms. Supporting evidence shows that penetration test exchanges a case ID and retrieves another tenant's document. The architect must preserve the requirement that each firm requires strict object-level isolation. Before approving a solution, which analysis most directly clarifies the underlying dependency or control gap?
- Trace subject, tenant, object and data-layer authorization decisions
- Rely only on login authentication without checking case object ownership
- Introduce safe policy fixes with a dual-tenant regression suite
- Apply tenant-bound object authorization enforced on every API and data query
Explanation
Correct Answer
A:
Trace subject, tenant, object and data-layer authorization decisions is the appropriate diagnostic because the observation—penetration test exchanges a case ID and retrieves another tenant's document—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (valid user tokens can access case files belonging to other law firms) before the design is approved.
Incorrect Answers
B:
Authentication cannot replace per-object authorization. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that each firm requires strict object-level isolation.
C:
The alternative “Introduce safe policy fixes with a dual-tenant regression suite” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, penetration test exchanges a case ID and retrieves another tenant's document. The option “Trace subject, tenant, object and data-layer authorization decisions” instead addresses the requested root-cause evidence.
D:
The alternative “Apply tenant-bound object authorization enforced on every API and data query” is target architecture selection; it does not establish why the observed path failed. In the reported observation, penetration test exchanges a case ID and retrieves another tenant's document. The option “Trace subject, tenant, object and data-layer authorization decisions” instead addresses the requested root-cause evidence.