Google Professional Cloud Architect Practice Test 45
Question 440
The production state reproducibility environment at National postal office faces this issue: manual firewall edits are missing from the Terraform plan. Supporting evidence shows that drift report shows an open SSH rule not present in source control. The architect must preserve the requirement that mail routing deployment must be repeatable and secure. Which migration or rollout step best manages risk, dependencies and reversibility?
- Import and reconcile unmanaged resources before enforcement
- Track drift events, failed plans and state-access privileges
- Delete every drifted resource before assessing mail-processing dependencies
- Move firewall resources under controlled IaC with policy-as-code checks
Explanation
Correct Answer
A:
Import and reconcile unmanaged resources before enforcement is a controlled means to introduce the approved architecture while meeting the requirement that mail routing deployment must be repeatable and secure. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
The alternative “Track drift events, failed plans and state-access privileges” addresses later monitoring rather than the actual controlled deployment. In the reported observation, drift report shows an open SSH rule not present in source control. The option “Import and reconcile unmanaged resources before enforcement” instead addresses the requested controlled implementation.
C:
Blind deletion can cause service interruptions. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that mail routing deployment must be repeatable and secure.
D:
The alternative “Move firewall resources under controlled IaC with policy-as-code checks” describes the chosen design, but not how it is introduced safely. In the reported observation, drift report shows an open SSH rule not present in source control. The option “Import and reconcile unmanaged resources before enforcement” instead addresses the requested controlled implementation.
Question 441
Regional newspaper platform plans to update automated infrastructure catalog. Investigators found that asset review shows inconsistent IAM, patch settings and logging between regions, consistent with the reported problem that each team manually creates different VM images for the same application tier. The response must satisfy the requirement that new sites must have consistent repeatable baseline controls. The approved change has been applied. Which validation provides the clearest evidence the original problem is fixed?
- Rebuild a test environment and compare deployed policy to approved baseline
- Migrate one region to versioned modules and controlled state storage
- Inventory approved resource models, drift and team ownership
- Let each engineer edit production resources manually without recording changes
Explanation
Correct Answer
A:
Rebuild a test environment and compare deployed policy to approved baseline is a direct acceptance test of the path implicated by asset review shows inconsistent IAM, patch settings and logging between regions. It checks that the original risk (each team manually creates different VM images for the same application tier) has actually been controlled and tests that permitted operations still meet the requirement that new sites must have consistent repeatable baseline controls.
Incorrect Answers
B:
The alternative “Migrate one region to versioned modules and controlled state storage” documents change execution but not its operational acceptance result. In the reported observation, asset review shows inconsistent IAM, patch settings and logging between regions. The option “Rebuild a test environment and compare deployed policy to approved baseline” instead addresses the requested acceptance verification.
C:
The alternative “Inventory approved resource models, drift and team ownership” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, asset review shows inconsistent IAM, patch settings and logging between regions. The option “Rebuild a test environment and compare deployed policy to approved baseline” instead addresses the requested acceptance verification.
D:
Manual one-off changes are hard to reproduce or audit. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that new sites must have consistent repeatable baseline controls.
Question 442
Case study: Regional transport network: low-latency dispatch API
Regional transport network relies on low-latency dispatch API to deliver its operational commitments. The current architectural problem is that dispatch requests cross the internet to an API hosted in another region. The team has recorded this evidence: flow logs show round trips go through a centralized NAT despite local backends. Any proposed response must preserve the requirement that private dispatch callers require restricted routing and prompt responses.
Regional transport network plans to update low-latency dispatch API. Investigators found that flow logs show round trips go through a centralized NAT despite local backends, consistent with the reported problem that dispatch requests cross the internet to an API hosted in another region. The response must satisfy the requirement that private dispatch callers require restricted routing and prompt responses. The design review is over and production introduction is next. Which action is the best fit?
- Put a public forwarding rule on every internal backend for simplicity
- Gradually switch dispatch clients with route validation and rollback
- Choose regional internal load balancing and private connectivity paths
- Monitor backend health, route changes and private latency
Explanation
Correct Answer
B:
Gradually switch dispatch clients with route validation and rollback is a controlled means to introduce the approved architecture while meeting the requirement that private dispatch callers require restricted routing and prompt responses. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
Public ingress violates the explicit private dispatch boundary. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that private dispatch callers require restricted routing and prompt responses.
C:
The alternative “Choose regional internal load balancing and private connectivity paths” describes the chosen design, but not how it is introduced safely. In the reported observation, flow logs show round trips go through a centralized NAT despite local backends. The option “Gradually switch dispatch clients with route validation and rollback” instead addresses the requested controlled implementation.
D:
The alternative “Monitor backend health, route changes and private latency” addresses later monitoring rather than the actual controlled deployment. In the reported observation, flow logs show round trips go through a centralized NAT despite local backends. The option “Gradually switch dispatch clients with route validation and rollback” instead addresses the requested controlled implementation.
Question 443
The database migration testing environment at Municipal tax office faces this issue: an automated migration passes row counts even though currency fields lose decimal precision. Supporting evidence shows that comparison shows several tax invoices differ by one cent after import. The architect must preserve the requirement that legal tax computations require exact financial arithmetic. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Define deterministic money-type mappings and financial invariant tests
- Track data drift, failed casts and postmigration reconciliation
- Compare cents and aggregates for individual invoices before cutover
- Accept equal row count as proof that amounts are unchanged
Explanation
Correct Answer
B:
Track data drift, failed casts and postmigration reconciliation reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (an automated migration passes row counts even though currency fields lose decimal precision) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Define deterministic money-type mappings and financial invariant tests” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, comparison shows several tax invoices differ by one cent after import. The option “Track data drift, failed casts and postmigration reconciliation” instead addresses the requested ongoing operational assurance.
C:
The alternative “Compare cents and aggregates for individual invoices before cutover” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, comparison shows several tax invoices differ by one cent after import. The option “Track data drift, failed casts and postmigration reconciliation” instead addresses the requested ongoing operational assurance.
D:
Row totals cannot detect corrupted financial values. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that legal tax computations require exact financial arithmetic.
Question 444
Consider Smart building portfolio and its telemetry collector workload. The issue is that sensor ingestion stops whenever the central analytics service is deployed; the current observation is that test telemetry shows HTTP sensors retry until devices run out of buffer. The team must ensure that devices must keep accepting samples through brief backend maintenance. Which continuous monitoring approach best reveals recurrence or changing dependencies?
- Watch oldest pending sample, dead-letter errors and quota headroom
- Stop analytics for an hour and verify ingest durability and replay
- Block sensor writes during every analytics rollout
- Decouple device ingestion through durable messaging and independently scaling consumers
Explanation
Correct Answer
A:
Watch oldest pending sample, dead-letter errors and quota headroom reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (sensor ingestion stops whenever the central analytics service is deployed) rather than treating the first successful test as permanent assurance.
Incorrect Answers
B:
The alternative “Stop analytics for an hour and verify ingest durability and replay” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, test telemetry shows HTTP sensors retry until devices run out of buffer. The option “Watch oldest pending sample, dead-letter errors and quota headroom” instead addresses the requested ongoing operational assurance.
C:
Tight coupling discards data when a downstream service pauses. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that devices must keep accepting samples through brief backend maintenance.
D:
The alternative “Decouple device ingestion through durable messaging and independently scaling consumers” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, test telemetry shows HTTP sensors retry until devices run out of buffer. The option “Watch oldest pending sample, dead-letter errors and quota headroom” instead addresses the requested ongoing operational assurance.
Question 445
The temporary sky-image processing environment at University astronomy project faces this issue: large image batch runs only one weekend a month yet reserved VMs are always on. Supporting evidence shows that cost report shows accelerator nodes idle more than ninety percent of the time. The architect must preserve the requirement that scientific jobs can checkpoint and resume after interruption. Which migration or rollout step best manages risk, dependencies and reversibility?
- Test checkpoint restoration and quota-aware job retries before scaling
- Track GPU idle hours, interruption rates and batch cost
- Use spot capacity for the only stateful database with no recovery strategy
- Use job orchestration with Spot VMs for interruptible batch computation
Explanation
Correct Answer
A:
Test checkpoint restoration and quota-aware job retries before scaling is a controlled means to introduce the approved architecture while meeting the requirement that scientific jobs can checkpoint and resume after interruption. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
The alternative “Track GPU idle hours, interruption rates and batch cost” addresses later monitoring rather than the actual controlled deployment. In the reported observation, cost report shows accelerator nodes idle more than ninety percent of the time. The option “Test checkpoint restoration and quota-aware job retries before scaling” instead addresses the requested controlled implementation.
C:
Preemptible nodes are unsuitable as unprotected authoritative state. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that scientific jobs can checkpoint and resume after interruption.
D:
The alternative “Use job orchestration with Spot VMs for interruptible batch computation” describes the chosen design, but not how it is introduced safely. In the reported observation, cost report shows accelerator nodes idle more than ninety percent of the time. The option “Test checkpoint restoration and quota-aware job retries before scaling” instead addresses the requested controlled implementation.
Question 446
At Regional newspaper platform, the Google Cloud design for automated infrastructure catalog is affected because each team manually creates different VM images for the same application tier. A review found that asset review shows inconsistent IAM, patch settings and logging between regions. The proposed response must account for the requirement that new sites must have consistent repeatable baseline controls. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?
- Inventory approved resource models, drift and team ownership
- Publish reusable Terraform modules with policy tests and documented ownership
- Migrate one region to versioned modules and controlled state storage
- Let each engineer edit production resources manually without recording changes
Explanation
Correct Answer
A:
Inventory approved resource models, drift and team ownership is the appropriate diagnostic because the observation—asset review shows inconsistent IAM, patch settings and logging between regions—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (each team manually creates different VM images for the same application tier) before the design is approved.
Incorrect Answers
B:
The alternative “Publish reusable Terraform modules with policy tests and documented ownership” is target architecture selection; it does not establish why the observed path failed. In the reported observation, asset review shows inconsistent IAM, patch settings and logging between regions. The option “Inventory approved resource models, drift and team ownership” instead addresses the requested root-cause evidence.
C:
The alternative “Migrate one region to versioned modules and controlled state storage” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, asset review shows inconsistent IAM, patch settings and logging between regions. The option “Inventory approved resource models, drift and team ownership” instead addresses the requested root-cause evidence.
D:
Manual one-off changes are hard to reproduce or audit. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that new sites must have consistent repeatable baseline controls.
Question 447
Airport luggage services plans to update service catalog onboarding. Investigators found that tickets show inconsistent machine sizing and missing application tags, consistent with the reported problem that new teams ask for databases by email and receive unrestricted project ownership. The response must satisfy the requirement that every project needs approved cost and access boundaries. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?
- Continue granting project Owner for all simple database requests
- Launch approved Terraform-backed catalog items for pilot teams
- Review common database requests, service tiers and authorized provisioning roles
- Define self-service catalog templates with IAM and budget constraints
Explanation
Correct Answer
C:
Review common database requests, service tiers and authorized provisioning roles is the appropriate diagnostic because the observation—tickets show inconsistent machine sizing and missing application tags—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (new teams ask for databases by email and receive unrestricted project ownership) before the design is approved.
Incorrect Answers
A:
Broad manual grants defeat governed repeatability. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that every project needs approved cost and access boundaries.
B:
The alternative “Launch approved Terraform-backed catalog items for pilot teams” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, tickets show inconsistent machine sizing and missing application tags. The option “Review common database requests, service tiers and authorized provisioning roles” instead addresses the requested root-cause evidence.
D:
The alternative “Define self-service catalog templates with IAM and budget constraints” is target architecture selection; it does not establish why the observed path failed. In the reported observation, tickets show inconsistent machine sizing and missing application tags. The option “Review common database requests, service tiers and authorized provisioning roles” instead addresses the requested root-cause evidence.
Question 448
Hospital imaging research unit plans to update regulated data classification. Investigators found that dataset profiler finds patient IDs inside free-text radiology comments, consistent with the reported problem that an AI training workflow ingests medical reports with accidental patient identifiers. The response must satisfy the requirement that only approved deidentified inputs may enter model training. The design review is over and production introduction is next. Which action is the best fit?
- Use Sensitive Data Protection inspection/deidentification with governance controls
- Track newly detected sensitive patterns, policy versions and false negatives
- Insert deidentification before training and quarantine unresolved findings
- Trust a generic prompt to remove every patient ID from raw input
Explanation
Correct Answer
C:
Insert deidentification before training and quarantine unresolved findings is a controlled means to introduce the approved architecture while meeting the requirement that only approved deidentified inputs may enter model training. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Use Sensitive Data Protection inspection/deidentification with governance controls” describes the chosen design, but not how it is introduced safely. In the reported observation, dataset profiler finds patient IDs inside free-text radiology comments. The option “Insert deidentification before training and quarantine unresolved findings” instead addresses the requested controlled implementation.
B:
The alternative “Track newly detected sensitive patterns, policy versions and false negatives” addresses later monitoring rather than the actual controlled deployment. In the reported observation, dataset profiler finds patient IDs inside free-text radiology comments. The option “Insert deidentification before training and quarantine unresolved findings” instead addresses the requested controlled implementation.
D:
Prompt guidance is not a deterministic privacy-control boundary. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that only approved deidentified inputs may enter model training.
Question 449
At Public grant agency, the executive decision analysis workload has a documented risk: project review scores optional chatbot convenience higher than accessibility and regulatory filing. The review found that business case omits users reliant on assistive technologies. The architecture must also ensure that benefit delivery must meet accessible filing requirements. What enduring Google Cloud design should the team choose now that the failure mode is understood?
- Prioritize accessible essential workflow before optional AI enhancements
- Monitor accessibility incidents and task completion outcomes
- Approve the chatbot solely because it uses the newest language model
- Translate user needs into measurable outcomes, compliance and risk
Explanation
Correct Answer
A:
Prioritize accessible essential workflow before optional AI enhancements targets the underlying issue (project review scores optional chatbot convenience higher than accessibility and regulatory filing) rather than merely reporting symptoms. It also preserves the required outcome (benefit delivery must meet accessible filing requirements), which a target-state design must satisfy.
Incorrect Answers
B:
The alternative “Monitor accessibility incidents and task completion outcomes” measures results without defining the preventive design now required. In the reported observation, business case omits users reliant on assistive technologies. The option “Prioritize accessible essential workflow before optional AI enhancements” instead addresses the requested architecture selection.
C:
Novelty does not meet the required filing accessibility outcome. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that benefit delivery must meet accessible filing requirements.
D:
The alternative “Translate user needs into measurable outcomes, compliance and risk” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, business case omits users reliant on assistive technologies. The option “Prioritize accessible essential workflow before optional AI enhancements” instead addresses the requested architecture selection.
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.