Google Professional Cloud Architect Practice Test 47
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.
Question 461
Smart-grid aggregation provider plans to update remote operator privilege. Investigators found that session audit shows support requests without approved change windows, consistent with the reported problem that contractors can run privileged maintenance on all grid data collectors. The response must satisfy the requirement that critical grid safety commands must remain restricted. The approved change has been applied. Which validation provides the clearest evidence the original problem is fixed?
- Revoke standing access and introduce scoped time-limited grants
- Give all external contractors unbounded owner privileges to speed repair
- Inventory operator identities, authorized sites and time-bound access needs
- Verify off-window operator commands fail while approved maintenance works
Explanation
Correct Answer
D:
Verify off-window operator commands fail while approved maintenance works is a direct acceptance test of the path implicated by session audit shows support requests without approved change windows. It checks that the original risk (contractors can run privileged maintenance on all grid data collectors) has actually been controlled and tests that permitted operations still meet the requirement that critical grid safety commands must remain restricted.
Incorrect Answers
A:
The alternative “Revoke standing access and introduce scoped time-limited grants” documents change execution but not its operational acceptance result. In the reported observation, session audit shows support requests without approved change windows. The option “Verify off-window operator commands fail while approved maintenance works” instead addresses the requested acceptance verification.
B:
Standing global privilege defeats accountable contractor access. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that critical grid safety commands must remain restricted.
C:
The alternative “Inventory operator identities, authorized sites and time-bound access needs” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, session audit shows support requests without approved change windows. The option “Verify off-window operator commands fail while approved maintenance works” instead addresses the requested acceptance verification.
Question 462
The alert dissemination environment at National weather agency faces this issue: the weather alert app must handle a sudden 30-fold audience jump when storms hit. Supporting evidence shows that metrics reveal static instances hit connection limits while message publication remains healthy. The architect must preserve the requirement that government alerts must be delivered promptly during severe weather. What test must pass before the business accepts the remediated architecture?
- Disable rate and capacity limits without testing downstream quotas
- Generate synthetic 30x fanout and confirm alert freshness and error budgets
- Canary autoscaling limits and emergency alert handling under load
- Profile connection saturation, geography and alert publication SLO
Explanation
Correct Answer
B:
Generate synthetic 30x fanout and confirm alert freshness and error budgets is a direct acceptance test of the path implicated by metrics reveal static instances hit connection limits while message publication remains healthy. It checks that the original risk (the weather alert app must handle a sudden 30-fold audience jump when storms hit) has actually been controlled and tests that permitted operations still meet the requirement that government alerts must be delivered promptly during severe weather.
Incorrect Answers
A:
Unbounded fanout can exhaust dependencies rather than improving availability. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that government alerts must be delivered promptly during severe weather.
C:
The alternative “Canary autoscaling limits and emergency alert handling under load” documents change execution but not its operational acceptance result. In the reported observation, metrics reveal static instances hit connection limits while message publication remains healthy. The option “Generate synthetic 30x fanout and confirm alert freshness and error budgets” instead addresses the requested acceptance verification.
D:
The alternative “Profile connection saturation, geography and alert publication SLO” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, metrics reveal static instances hit connection limits while message publication remains healthy. The option “Generate synthetic 30x fanout and confirm alert freshness and error budgets” instead addresses the requested acceptance verification.
Question 463
Case study: International automotive retailer: API gateway migration
International automotive retailer relies on API gateway migration to deliver its operational commitments. The current architectural problem is that third-party dealerships expect old JSON fields while a new service removes one required property. The team has recorded this evidence: contract tests show older clients fail when the new revision is published. Any proposed response must preserve the requirement that dealer ordering cannot require simultaneous client upgrades.
At International automotive retailer, the API gateway migration workload has a documented risk: third-party dealerships expect old JSON fields while a new service removes one required property. The review found that contract tests show older clients fail when the new revision is published. The architecture must also ensure that dealer ordering cannot require simultaneous client upgrades. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Deploy compatibility adapter with parallel metrics and announced migration window
- Design backward-compatible API versioning and deprecation policy
- Remove legacy fields immediately because the provider source code is updated
- Identify required fields, version agreements and client deployment windows
Explanation
Correct Answer
D:
Identify required fields, version agreements and client deployment windows is the appropriate diagnostic because the observation—contract tests show older clients fail when the new revision is published—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (third-party dealerships expect old JSON fields while a new service removes one required property) before the design is approved.
Incorrect Answers
A:
The alternative “Deploy compatibility adapter with parallel metrics and announced migration window” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, contract tests show older clients fail when the new revision is published. The option “Identify required fields, version agreements and client deployment windows” instead addresses the requested root-cause evidence.
B:
The alternative “Design backward-compatible API versioning and deprecation policy” is target architecture selection; it does not establish why the observed path failed. In the reported observation, contract tests show older clients fail when the new revision is published. The option “Identify required fields, version agreements and client deployment windows” instead addresses the requested root-cause evidence.
C:
Client contracts are not automatically updated with server code. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that dealer ordering cannot require simultaneous client upgrades.
Question 464
Case study: Subscription video startup: BigQuery warehouse scan cost
Subscription video startup relies on BigQuery warehouse scan cost to deliver its operational commitments. The current architectural problem is that queries scan every historical event for simple daily subscriber counts. The team has recorded this evidence: query plan shows 5TB scanned despite filtering for yesterday. Any proposed response must preserve the requirement that marketing results must arrive within its daily budget.
Subscription video startup plans to update BigQuery warehouse scan cost. Investigators found that query plan shows 5TB scanned despite filtering for yesterday, consistent with the reported problem that queries scan every historical event for simple daily subscriber counts. The response must satisfy the requirement that marketing results must arrive within its daily budget. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?
- Rewrite incremental pipelines and test a representative partitioned query
- Use date-partitioned tables and suitable clustering with governed query patterns
- Replace predicates with full-table SELECT star on each dashboard load
- Inspect SQL filters, partition pruning and required clustering keys
Explanation
Correct Answer
D:
Inspect SQL filters, partition pruning and required clustering keys is the appropriate diagnostic because the observation—query plan shows 5TB scanned despite filtering for yesterday—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (queries scan every historical event for simple daily subscriber counts) before the design is approved.
Incorrect Answers
A:
The alternative “Rewrite incremental pipelines and test a representative partitioned query” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, query plan shows 5TB scanned despite filtering for yesterday. The option “Inspect SQL filters, partition pruning and required clustering keys” instead addresses the requested root-cause evidence.
B:
The alternative “Use date-partitioned tables and suitable clustering with governed query patterns” is target architecture selection; it does not establish why the observed path failed. In the reported observation, query plan shows 5TB scanned despite filtering for yesterday. The option “Inspect SQL filters, partition pruning and required clustering keys” instead addresses the requested root-cause evidence.
C:
Full scans multiply spend without improving daily freshness. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that marketing results must arrive within its daily budget.
Question 465
At National energy balancing platform, the regional failure rehearsal workload has a documented risk: a multi-zone app still relies on a single regional message broker. The review found that chaos rehearsal shows all dispatch messages stop when broker restarts. The architecture must also ensure that grid dispatch must recover within a documented time objective. The team must deliver the approved control safely. Which deployment sequence is most appropriate?
- Add more web replicas while retaining the unreplicated broker
- Stage broker migration with message replay and cutover safeguards
- Monitor lag, broker health and RTO breaches
- Design redundant durable messaging with proper consumer reconciliation
Explanation
Correct Answer
B:
Stage broker migration with message replay and cutover safeguards is a controlled means to introduce the approved architecture while meeting the requirement that grid dispatch must recover within a documented time objective. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
Web redundancy cannot compensate for a single broker dependency. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that grid dispatch must recover within a documented time objective.
C:
The alternative “Monitor lag, broker health and RTO breaches” addresses later monitoring rather than the actual controlled deployment. In the reported observation, chaos rehearsal shows all dispatch messages stop when broker restarts. The option “Stage broker migration with message replay and cutover safeguards” instead addresses the requested controlled implementation.
D:
The alternative “Design redundant durable messaging with proper consumer reconciliation” describes the chosen design, but not how it is introduced safely. In the reported observation, chaos rehearsal shows all dispatch messages stop when broker restarts. The option “Stage broker migration with message replay and cutover safeguards” instead addresses the requested controlled implementation.
Question 466
Case study: Regional sports venue: deploy-time traffic splitting
Regional sports venue relies on deploy-time traffic splitting to deliver its operational commitments. The current architectural problem is that teams replace a full production service revision in one step before stadium events. The team has recorded this evidence: last release caused 15 minutes of checkout errors during a full swap. Any proposed response must preserve the requirement that ticket scanning must stay available throughout peak admission.
At Regional sports venue, the deploy-time traffic splitting workload has a documented risk: teams replace a full production service revision in one step before stadium events. The review found that last release caused 15 minutes of checkout errors during a full swap. The architecture must also ensure that ticket scanning must stay available throughout peak admission. The team must deliver the approved control safely. Which deployment sequence is most appropriate?
- Introduce weighted traffic shifting and automatic rollback thresholds
- Watch conversion errors, latency and rollback triggers
- Design progressive canary or blue-green release with measurable safety gates
- Use a full instantaneous replace for every release and observe failures afterward
Explanation
Correct Answer
A:
Introduce weighted traffic shifting and automatic rollback thresholds is a controlled means to introduce the approved architecture while meeting the requirement that ticket scanning must stay available throughout peak admission. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
The alternative “Watch conversion errors, latency and rollback triggers” addresses later monitoring rather than the actual controlled deployment. In the reported observation, last release caused 15 minutes of checkout errors during a full swap. The option “Introduce weighted traffic shifting and automatic rollback thresholds” instead addresses the requested controlled implementation.
C:
The alternative “Design progressive canary or blue-green release with measurable safety gates” describes the chosen design, but not how it is introduced safely. In the reported observation, last release caused 15 minutes of checkout errors during a full swap. The option “Introduce weighted traffic shifting and automatic rollback thresholds” instead addresses the requested controlled implementation.
D:
A big-bang change concentrates customer impact. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that ticket scanning must stay available throughout peak admission.
Question 467
National retailer plans to update SOC 2 assurance evidence. Investigators found that internal audit finds no linkage between IAM grants and access requests, consistent with the reported problem that cloud service roles change without retaining approval artifacts for audit. The response must satisfy the requirement that auditor must reconstruct who authorized production privileges. Which target-state design is best justified by the evidence and required business outcome?
- Design traceable access approval, just-in-time privileges and immutable change records
- Treat an informal verbal confirmation as complete access audit evidence
- Map evidence sources, authorization workflow and retained approvals
- Track orphan grants, missing approvals and retained evidence coverage
Explanation
Correct Answer
A:
Design traceable access approval, just-in-time privileges and immutable change records targets the underlying issue (cloud service roles change without retaining approval artifacts for audit) rather than merely reporting symptoms. It also preserves the required outcome (auditor must reconstruct who authorized production privileges), which a target-state design must satisfy.
Incorrect Answers
B:
Unrecorded approvals cannot support reproducible assurance. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that auditor must reconstruct who authorized production privileges.
C:
The alternative “Map evidence sources, authorization workflow and retained approvals” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, internal audit finds no linkage between IAM grants and access requests. The option “Design traceable access approval, just-in-time privileges and immutable change records” instead addresses the requested architecture selection.
D:
The alternative “Track orphan grants, missing approvals and retained evidence coverage” measures results without defining the preventive design now required. In the reported observation, internal audit finds no linkage between IAM grants and access requests. The option “Design traceable access approval, just-in-time privileges and immutable change records” instead addresses the requested architecture selection.
Question 468
At International hotel operator, the reservation mainframe bridge workload has a documented risk: reservation jobs on a mainframe call undocumented nightly batch services. The review found that discovery captures eleven downstream dependencies absent from design diagrams. The architecture must also ensure that bookings may not be lost during peak holiday weeks. Which post-change test most reliably distinguishes a functioning control from a merely successful installation?
- Cut all mainframe links on the first deployment without inventory reconciliation
- Build a verified dependency map and define safe migration waves
- Compare room inventory and customer booking consistency across both systems
- Pilot low-risk read features and dual-write reconciliation before reservation cutover
Explanation
Correct Answer
C:
Compare room inventory and customer booking consistency across both systems is a direct acceptance test of the path implicated by discovery captures eleven downstream dependencies absent from design diagrams. It checks that the original risk (reservation jobs on a mainframe call undocumented nightly batch services) has actually been controlled and tests that permitted operations still meet the requirement that bookings may not be lost during peak holiday weeks.
Incorrect Answers
A:
A big-bang cutover risks invisible dependencies and lost bookings. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that bookings may not be lost during peak holiday weeks.
B:
The alternative “Build a verified dependency map and define safe migration waves” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, discovery captures eleven downstream dependencies absent from design diagrams. The option “Compare room inventory and customer booking consistency across both systems” instead addresses the requested acceptance verification.
D:
The alternative “Pilot low-risk read features and dual-write reconciliation before reservation cutover” documents change execution but not its operational acceptance result. In the reported observation, discovery captures eleven downstream dependencies absent from design diagrams. The option “Compare room inventory and customer booking consistency across both systems” instead addresses the requested acceptance verification.
Question 469
Case study: Online language tutoring platform: GKE API worker capacity
Online language tutoring platform relies on GKE API worker capacity to deliver its operational commitments. The current architectural problem is that CPU-based scaling alone misses a backlog of asynchronous translation requests. The team has recorded this evidence: pod telemetry shows low CPU but growing Pub/Sub outstanding messages. Any proposed response must preserve the requirement that tutoring sessions require backlogs to clear in under two minutes.
The GKE API worker capacity environment at Online language tutoring platform faces this issue: CPU-based scaling alone misses a backlog of asynchronous translation requests. Supporting evidence shows that pod telemetry shows low CPU but growing Pub/Sub outstanding messages. The architect must preserve the requirement that tutoring sessions require backlogs to clear in under two minutes. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Load queue bursts and observe backlog clearance within the two-minute SLO
- Track autoscaler saturation, pending pods and oldest task age
- Use workload autoscaling based on meaningful request or queue metrics
- Increase CPU limits but keep one replica regardless of queue depth
Explanation
Correct Answer
B:
Track autoscaler saturation, pending pods and oldest task age reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (CPU-based scaling alone misses a backlog of asynchronous translation requests) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Load queue bursts and observe backlog clearance within the two-minute SLO” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, pod telemetry shows low CPU but growing Pub/Sub outstanding messages. The option “Track autoscaler saturation, pending pods and oldest task age” instead addresses the requested ongoing operational assurance.
C:
The alternative “Use workload autoscaling based on meaningful request or queue metrics” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, pod telemetry shows low CPU but growing Pub/Sub outstanding messages. The option “Track autoscaler saturation, pending pods and oldest task age” instead addresses the requested ongoing operational assurance.
D:
A fixed replica count cannot scale with independent queue pressure. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that tutoring sessions require backlogs to clear in under two minutes.
Question 470
Regional postal delivery firm plans to update support escalation maturity. Investigators found that ticket history shows repeated bounced ownership assignments, consistent with the reported problem that a production outage remains open because no team owns the supporting vendor service. The response must satisfy the requirement that delivery confirmations must have a clear customer-facing support path. The approved change has been applied. Which validation provides the clearest evidence the original problem is fixed?
- Open synthetic vendor dependency outage and verify correct escalation
- Map vendor dependencies, RACI boundaries and critical support escalation
- Close incidents whenever they cross an organizational boundary
- Introduce unified incident routing with current on-call contact tests
Explanation
Correct Answer
A:
Open synthetic vendor dependency outage and verify correct escalation is a direct acceptance test of the path implicated by ticket history shows repeated bounced ownership assignments. It checks that the original risk (a production outage remains open because no team owns the supporting vendor service) has actually been controlled and tests that permitted operations still meet the requirement that delivery confirmations must have a clear customer-facing support path.
Incorrect Answers
B:
The alternative “Map vendor dependencies, RACI boundaries and critical support escalation” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, ticket history shows repeated bounced ownership assignments. The option “Open synthetic vendor dependency outage and verify correct escalation” instead addresses the requested acceptance verification.
C:
No owner does not imply the service problem is resolved. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that delivery confirmations must have a clear customer-facing support path.
D:
The alternative “Introduce unified incident routing with current on-call contact tests” documents change execution but not its operational acceptance result. In the reported observation, ticket history shows repeated bounced ownership assignments. The option “Open synthetic vendor dependency outage and verify correct escalation” instead addresses the requested acceptance verification.