Google Professional Cloud Architect Practice Test 56
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.
Question 551
Case study: Financial audit platform: service emulator tests
Financial audit platform relies on service emulator tests to deliver its operational commitments. The current architectural problem is that developers run payment integration tests against live transaction services. The team has recorded this evidence: test logs show real transfer identifiers generated by a local developer build. Any proposed response must preserve the requirement that testing must not create external settlement transfers.
Consider Financial audit platform and its service emulator tests workload. The issue is that developers run payment integration tests against live transaction services; the current observation is that test logs show real transfer identifiers generated by a local developer build. The team must ensure that testing must not create external settlement transfers. Which acceptance test should demonstrate both protection against the failure and continued authorized service?
- Identify external API calls, test credentials and shared environment settings
- Run full test suite and confirm no live financial side effects
- Run all tests using the production billing administrator identity
- Switch CI jobs to gated test endpoints and secret-scoped identities
Explanation
Correct Answer
B:
Run full test suite and confirm no live financial side effects is a direct acceptance test of the path implicated by test logs show real transfer identifiers generated by a local developer build. It checks that the original risk (developers run payment integration tests against live transaction services) has actually been controlled and tests that permitted operations still meet the requirement that testing must not create external settlement transfers.
Incorrect Answers
A:
The alternative “Identify external API calls, test credentials and shared environment settings” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, test logs show real transfer identifiers generated by a local developer build. The option “Run full test suite and confirm no live financial side effects” instead addresses the requested acceptance verification.
C:
Production credentials make test runs capable of unintended transfers. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that testing must not create external settlement transfers.
D:
The alternative “Switch CI jobs to gated test endpoints and secret-scoped identities” documents change execution but not its operational acceptance result. In the reported observation, test logs show real transfer identifiers generated by a local developer build. The option “Run full test suite and confirm no live financial side effects” instead addresses the requested acceptance verification.
Question 552
At Legal case management SaaS, the Google Cloud design for multi-tenant object security is affected because valid user tokens can access case files belonging to other law firms. A review found that penetration test exchanges a case ID and retrieves another tenant's document. The proposed response must account for the requirement that each firm requires strict object-level isolation. 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?
- Verify cross-tenant IDs always return authorization failure
- Trace subject, tenant, object and data-layer authorization decisions
- Accept the deployment ticket as proof that the control has no remaining security or availability risk
- Rely only on login authentication without checking case object ownership
- Monitor denied cross-tenant access and new API routes lacking ownership checks
- Apply tenant-bound object authorization enforced on every API and data query
Explanation
Correct Answers
A:
Verify cross-tenant IDs always return authorization failure is a direct acceptance test of the path implicated by penetration test exchanges a case ID and retrieves another tenant's document. It checks that the original risk (valid user tokens can access case files belonging to other law firms) has actually been controlled and tests that permitted operations still meet the requirement that each firm requires strict object-level isolation. It supplies the separate post-change acceptance result requested.
B:
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. It supplies the pre-design diagnostic evidence requested.
E:
Monitor denied cross-tenant access and new API routes lacking ownership checks reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (valid user tokens can access case files belonging to other law firms) rather than treating the first successful test as permanent assurance. It supplies the ongoing observation requested.
Incorrect Answers
C:
A change-record state does not measure the behavior reported by the original evidence, and cannot prove protection or availability. In particular, the observed issue was: penetration test exchanges a case ID and retrieves another tenant's document.
D:
Authentication cannot replace per-object authorization. It cannot satisfy the required evidence stages.
F:
Designing multi-tenant object security addresses the root cause, but this specific three-part question asks for evidence to diagnose, accept and continuously verify the response to valid user tokens can access case files belonging to other law firms, not another design proposal.
Question 553
At Public school administration, the Google Cloud design for student records database is affected because developers chose key-value storage but school reports need relational joins and ACID updates. A review found that schema analysis shows normalized enrollment, grades and billing tables. The proposed response must account for the requirement that data must stay region-bound and consistent across student updates. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?
- Choose managed Cloud SQL PostgreSQL for compatible relational transactions and backups
- Inventory relational queries, concurrency, transaction volume and region rules
- Migrate with Database Migration Service and compare transactional checksums
- Use unstructured object storage as a drop-in SQL transaction engine
Explanation
Correct Answer
B:
Inventory relational queries, concurrency, transaction volume and region rules is the appropriate diagnostic because the observation—schema analysis shows normalized enrollment, grades and billing tables—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (developers chose key-value storage but school reports need relational joins and ACID updates) before the design is approved.
Incorrect Answers
A:
The alternative “Choose managed Cloud SQL PostgreSQL for compatible relational transactions and backups” is target architecture selection; it does not establish why the observed path failed. In the reported observation, schema analysis shows normalized enrollment, grades and billing tables. The option “Inventory relational queries, concurrency, transaction volume and region rules” instead addresses the requested root-cause evidence.
C:
The alternative “Migrate with Database Migration Service and compare transactional checksums” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, schema analysis shows normalized enrollment, grades and billing tables. The option “Inventory relational queries, concurrency, transaction volume and region rules” instead addresses the requested root-cause evidence.
D:
Object storage cannot replace a relational transaction and query layer. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that data must stay region-bound and consistent across student updates.
Question 554
Case study: International agriculture co-op: organizational change management
International agriculture co-op relies on organizational change management to deliver its operational commitments. The current architectural problem is that field employees reject a new cloud harvest portal because offline workflows were removed. The team has recorded this evidence: usability survey shows farmers cannot record deliveries during cellular loss. Any proposed response must preserve the requirement that offline data capture is required for the harvest season.
At International agriculture co-op, the organizational change management workload has a documented risk: field employees reject a new cloud harvest portal because offline workflows were removed. The review found that usability survey shows farmers cannot record deliveries during cellular loss. The architecture must also ensure that offline data capture is required for the harvest season. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Interview field users and prioritize their required offline workflows
- Design product adoption with offline capture and clear sync accountability
- Pilot with field representatives and adapt training before full rollout
- Declare change successful because the web portal was deployed
Explanation
Correct Answer
A:
Interview field users and prioritize their required offline workflows is the appropriate diagnostic because the observation—usability survey shows farmers cannot record deliveries during cellular loss—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (field employees reject a new cloud harvest portal because offline workflows were removed) before the design is approved.
Incorrect Answers
B:
The alternative “Design product adoption with offline capture and clear sync accountability” is target architecture selection; it does not establish why the observed path failed. In the reported observation, usability survey shows farmers cannot record deliveries during cellular loss. The option “Interview field users and prioritize their required offline workflows” instead addresses the requested root-cause evidence.
C:
The alternative “Pilot with field representatives and adapt training before full rollout” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, usability survey shows farmers cannot record deliveries during cellular loss. The option “Interview field users and prioritize their required offline workflows” instead addresses the requested root-cause evidence.
D:
Deployment alone does not establish that users can complete business work. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that offline data capture is required for the harvest season.
Question 555
Public university registrar plans to update student-data migration. Investigators found that comparison shows primary-key collisions between initial exports and ongoing edits, consistent with the reported problem that bulk import from an aging database overwrites later updates during the cutover. The response must satisfy the requirement that graduation records must be correct at the moment of cutover. The design review is over and production introduction is next. Which action is the best fit?
- Plan full-load plus change-data capture with deterministic conflict handling
- Execute synchronized cutover after low-lag catch-up and final write-freeze
- Track CDC lag, failed writes and migration data quality
- Import the original snapshot only and ignore writes after its extraction
Explanation
Correct Answer
B:
Execute synchronized cutover after low-lag catch-up and final write-freeze is a controlled means to introduce the approved architecture while meeting the requirement that graduation records must be correct at the moment of cutover. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Plan full-load plus change-data capture with deterministic conflict handling” describes the chosen design, but not how it is introduced safely. In the reported observation, comparison shows primary-key collisions between initial exports and ongoing edits. The option “Execute synchronized cutover after low-lag catch-up and final write-freeze” instead addresses the requested controlled implementation.
C:
The alternative “Track CDC lag, failed writes and migration data quality” addresses later monitoring rather than the actual controlled deployment. In the reported observation, comparison shows primary-key collisions between initial exports and ongoing edits. The option “Execute synchronized cutover after low-lag catch-up and final write-freeze” instead addresses the requested controlled implementation.
D:
A stale snapshot loses legitimate updates made during the move. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that graduation records must be correct at the moment of cutover.
Question 556
Education research foundation plans to update multi-project packet filtering. Investigators found that network review finds SSH open to the internet from three experiment subnets, consistent with the reported problem that research projects inherit inconsistent firewall rules and centralized policy has no owner. The response must satisfy the requirement that a limited set of approved remote researchers still needs audited access. The team needs an operations signal rather than another design or one-time test. What should it track?
- Verify unapproved SSH is rejected while authenticated researcher routes remain
- Monitor firewall-rule drift and exception expiry by project
- Let every project administrator create a public any-any ingress rule
- Set hierarchy-level firewall controls with least-privilege project overrides
Explanation
Correct Answer
B:
Monitor firewall-rule drift and exception expiry by project reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (research projects inherit inconsistent firewall rules and centralized policy has no owner) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Verify unapproved SSH is rejected while authenticated researcher routes remain” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, network review finds SSH open to the internet from three experiment subnets. The option “Monitor firewall-rule drift and exception expiry by project” instead addresses the requested ongoing operational assurance.
C:
Unrestricted local firewalls defeat centralized protection. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that a limited set of approved remote researchers still needs audited access.
D:
The alternative “Set hierarchy-level firewall controls with least-privilege project overrides” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, network review finds SSH open to the internet from three experiment subnets. The option “Monitor firewall-rule drift and exception expiry by project” instead addresses the requested ongoing operational assurance.
Question 557
At University student services, the Google Cloud design for support cost decision is affected because finance wants to optimize Cloud Run spending by terminating instances during exam registration. A review found that cost report shows request demand peaks 20x within minutes. The proposed response must account for the requirement that students must be able to submit registration before hard deadlines. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?
- Trial concurrency and min-instance changes outside peak periods
- Set spending guardrails compatible with required minimum capacity and scaling
- Set min and max instances to zero during the announced registration peak
- Model workload demand, latency cost of cold starts and peak business value
Explanation
Correct Answer
D:
Model workload demand, latency cost of cold starts and peak business value is the appropriate diagnostic because the observation—cost report shows request demand peaks 20x within minutes—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (finance wants to optimize Cloud Run spending by terminating instances during exam registration) before the design is approved.
Incorrect Answers
A:
The alternative “Trial concurrency and min-instance changes outside peak periods” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, cost report shows request demand peaks 20x within minutes. The option “Model workload demand, latency cost of cold starts and peak business value” instead addresses the requested root-cause evidence.
B:
The alternative “Set spending guardrails compatible with required minimum capacity and scaling” is target architecture selection; it does not establish why the observed path failed. In the reported observation, cost report shows request demand peaks 20x within minutes. The option “Model workload demand, latency cost of cold starts and peak business value” instead addresses the requested root-cause evidence.
C:
A blanket shutdown destroys the core business outcome. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that students must be able to submit registration before hard deadlines.
Question 558
Consider Community public library and its Terraform landing zone rollout workload. The issue is that new projects require approved security settings but Terraform changes are applied directly from laptops; the current observation is that audit finds mutable local state and unreviewed IAM grants. The team must ensure that public catalog availability must not be interrupted by infrastructure drift. Which continuous monitoring approach best reveals recurrence or changing dependencies?
- Give all engineers full project Owner for local Terraform apply
- Use remote protected Terraform state and policy-controlled plans
- Verify identical approved plan outcomes and no unreviewed IAM escalation
- Monitor manual drift and denied policy changes
Explanation
Correct Answer
D:
Monitor manual drift and denied policy changes reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (new projects require approved security settings but Terraform changes are applied directly from laptops) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
Unreviewed broad changes negate controlled infrastructure rollout. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that public catalog availability must not be interrupted by infrastructure drift.
B:
The alternative “Use remote protected Terraform state and policy-controlled plans” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, audit finds mutable local state and unreviewed IAM grants. The option “Monitor manual drift and denied policy changes” instead addresses the requested ongoing operational assurance.
C:
The alternative “Verify identical approved plan outcomes and no unreviewed IAM escalation” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, audit finds mutable local state and unreviewed IAM grants. The option “Monitor manual drift and denied policy changes” instead addresses the requested ongoing operational assurance.
Question 559
Consider Multinational retailer and its checkout cost modernization workload. The issue is that a newly acquired brand will double country coverage and tax interfaces after migration; the current observation is that requirements show separate national tax authorities and holiday peak profiles. The team must ensure that checkout must preserve local residency and transparent tax audit. Which continuous monitoring approach best reveals recurrence or changing dependencies?
- Use modular regional tax integration boundaries with portable checkout contracts
- Encode every country's tax rules in a single hard-coded pricing function
- Track change requests, country-level latency and tax-policy drift
- Check per-country tax totals and rollback for partial integration failures
Explanation
Correct Answer
C:
Track change requests, country-level latency and tax-policy drift reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a newly acquired brand will double country coverage and tax interfaces after migration) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Use modular regional tax integration boundaries with portable checkout contracts” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, requirements show separate national tax authorities and holiday peak profiles. The option “Track change requests, country-level latency and tax-policy drift” instead addresses the requested ongoing operational assurance.
B:
Hardcoded global tax logic becomes fragile and difficult to audit. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that checkout must preserve local residency and transparent tax audit.
D:
The alternative “Check per-country tax totals and rollback for partial integration failures” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, requirements show separate national tax authorities and holiday peak profiles. The option “Track change requests, country-level latency and tax-policy drift” instead addresses the requested ongoing operational assurance.
Question 560
Case study: Payments risk laboratory: encryption key governance
Payments risk laboratory relies on encryption key governance to deliver its operational commitments. The current architectural problem is that payment data uses default encryption but contract requires customer control over key rotation. The team has recorded this evidence: key inventory shows provider-managed keys with no customer-managed lifecycle. Any proposed response must preserve the requirement that regulated card records require tracked access and planned key retirement.
Payments risk laboratory plans to update encryption key governance. Investigators found that key inventory shows provider-managed keys with no customer-managed lifecycle, consistent with the reported problem that payment data uses default encryption but contract requires customer control over key rotation. The response must satisfy the requirement that regulated card records require tracked access and planned key retirement. The approved change has been applied. Which validation provides the clearest evidence the original problem is fixed?
- Migrate eligible resources to approved keys with tested grant/rollback
- Clarify contract control requirements, key users and outage recovery implications
- Place plaintext encryption keys in shared project metadata
- Deny unauthorized decrypt, rotate a key version and verify service continuity
Explanation
Correct Answer
D:
Deny unauthorized decrypt, rotate a key version and verify service continuity is a direct acceptance test of the path implicated by key inventory shows provider-managed keys with no customer-managed lifecycle. It checks that the original risk (payment data uses default encryption but contract requires customer control over key rotation) has actually been controlled and tests that permitted operations still meet the requirement that regulated card records require tracked access and planned key retirement.
Incorrect Answers
A:
The alternative “Migrate eligible resources to approved keys with tested grant/rollback” documents change execution but not its operational acceptance result. In the reported observation, key inventory shows provider-managed keys with no customer-managed lifecycle. The option “Deny unauthorized decrypt, rotate a key version and verify service continuity” instead addresses the requested acceptance verification.
B:
The alternative “Clarify contract control requirements, key users and outage recovery implications” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, key inventory shows provider-managed keys with no customer-managed lifecycle. The option “Deny unauthorized decrypt, rotate a key version and verify service continuity” instead addresses the requested acceptance verification.
C:
Shared metadata does not provide protected KMS custody. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that regulated card records require tracked access and planned key retirement.