Google Professional Cloud Architect Practice Test 88
Question 870
At International insurance portal, the automated rollback thresholds workload has a documented risk: new revision doubles checkout error rate but rollout continues because logs are not tied to release gates. The review found that service dashboard shows 6% failure during a 20% canary. The architecture must also ensure that customer billing changes must be reversible without inconsistent transactions. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Deploy gradual traffic with automated abort thresholds
- Treat release success as the number of pods that became Ready
- Track failed rollback events and release-specific SLO deltas
- Establish baseline error budgets, canary signals and rollback authority
- Define canary gates for error, latency and transaction integrity
Explanation
Correct Answers
A:
Deploy gradual traffic with automated abort thresholds is a controlled means to introduce the approved architecture while meeting the requirement that customer billing changes must be reversible without inconsistent transactions. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption. This supplies the controlled-introduction half of the two-action package.
E:
Define canary gates for error, latency and transaction integrity targets the underlying issue (new revision doubles checkout error rate but rollout continues because logs are not tied to release gates) rather than merely reporting symptoms. It also preserves the required outcome (customer billing changes must be reversible without inconsistent transactions), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
Incorrect Answers
B:
Readiness alone does not demonstrate correct customer transactions. The shortcut does not supply the requested design and safe rollout for automated rollback thresholds, where service dashboard shows 6% failure during a 20% canary.
C:
Monitoring automated rollback thresholds for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: new revision doubles checkout error rate but rollout continues because logs are not tied to release gates.
D:
This diagnoses the original issue (new revision doubles checkout error rate but rollout continues because logs are not tied to release gates), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
Question 871
Consider Regional tax administration and its separation of duties workload. The issue is that one engineer both edits production code and approves its own security policy exceptions; the current observation is that access review shows the same principal has release and audit-admin permissions. The team must ensure that regulated changes require an independent approval trail. The team has completed discovery. Which preventive or corrective architecture is most appropriate?
- Give all developers Owner and rely on an informal promise to avoid self-approval
- Map change roles, privileged groups and audit responsibilities
- Monitor break-glass sessions and privilege role conflicts
- Separate release, approval and audit roles with enforceable IAM constraints
Explanation
Correct Answer
D:
Separate release, approval and audit roles with enforceable IAM constraints targets the underlying issue (one engineer both edits production code and approves its own security policy exceptions) rather than merely reporting symptoms. It also preserves the required outcome (regulated changes require an independent approval trail), which a target-state design must satisfy.
Incorrect Answers
A:
An informal promise cannot enforce role separation. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that regulated changes require an independent approval trail.
B:
The alternative “Map change roles, privileged groups and audit responsibilities” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, access review shows the same principal has release and audit-admin permissions. The option “Separate release, approval and audit roles with enforceable IAM constraints” instead addresses the requested architecture selection.
C:
The alternative “Monitor break-glass sessions and privilege role conflicts” measures results without defining the preventive design now required. In the reported observation, access review shows the same principal has release and audit-admin permissions. The option “Separate release, approval and audit roles with enforceable IAM constraints” instead addresses the requested architecture selection.
Question 872
At University research network, the GKE deployment safety workload has a documented risk: a new GPU workload is rolled onto the only node while existing experiment pods have no disruption budget. The review found that pilot update evicts every running inference pod. The architecture must also ensure that research service must remain available during cluster upgrades. The team must deliver the approved control safely. Which deployment sequence is most appropriate?
- Design safe rollout using health probes and PodDisruptionBudget where appropriate
- Roll out node-pool updates incrementally with fallback capacity
- Watch pod evictions, deployment stalls and degraded GPU availability
- Set replicas to one and skip readiness probes to accelerate upgrades
Explanation
Correct Answer
B:
Roll out node-pool updates incrementally with fallback capacity is a controlled means to introduce the approved architecture while meeting the requirement that research service must remain available during cluster upgrades. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Design safe rollout using health probes and PodDisruptionBudget where appropriate” describes the chosen design, but not how it is introduced safely. In the reported observation, pilot update evicts every running inference pod. The option “Roll out node-pool updates incrementally with fallback capacity” instead addresses the requested controlled implementation.
C:
The alternative “Watch pod evictions, deployment stalls and degraded GPU availability” addresses later monitoring rather than the actual controlled deployment. In the reported observation, pilot update evicts every running inference pod. The option “Roll out node-pool updates incrementally with fallback capacity” instead addresses the requested controlled implementation.
D:
Unprotected singleton workloads are unavailable on node drain. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that research service must remain available during cluster upgrades.
Question 873
Case study: Community telehealth provider: clinical deployment training
Community telehealth provider relies on clinical deployment training to deliver its operational commitments. The current architectural problem is that a platform modernization plan assigns unfamiliar GKE on-call duties without staff enablement. The team has recorded this evidence: postmortems show alerts ignored because responders lack cluster permissions. Any proposed response must preserve the requirement that patient scheduling must be supported around the clock.
Community telehealth provider plans to update clinical deployment training. Investigators found that postmortems show alerts ignored because responders lack cluster permissions, consistent with the reported problem that a platform modernization plan assigns unfamiliar GKE on-call duties without staff enablement. The response must satisfy the requirement that patient scheduling must be supported around the clock. Which target-state design is best justified by the evidence and required business outcome?
- Plan role-specific training, escalation and supported operational runbooks
- Give production Owner to everyone as an alternative to training
- Assess team skills, access gaps and incident handoff requirements
- Track runbook usage, responder readiness and escalation failures
Explanation
Correct Answer
A:
Plan role-specific training, escalation and supported operational runbooks targets the underlying issue (a platform modernization plan assigns unfamiliar GKE on-call duties without staff enablement) rather than merely reporting symptoms. It also preserves the required outcome (patient scheduling must be supported around the clock), which a target-state design must satisfy.
Incorrect Answers
B:
Broad privilege does not create operational competence. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that patient scheduling must be supported around the clock.
C:
The alternative “Assess team skills, access gaps and incident handoff requirements” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, postmortems show alerts ignored because responders lack cluster permissions. The option “Plan role-specific training, escalation and supported operational runbooks” instead addresses the requested architecture selection.
D:
The alternative “Track runbook usage, responder readiness and escalation failures” measures results without defining the preventive design now required. In the reported observation, postmortems show alerts ignored because responders lack cluster permissions. The option “Plan role-specific training, escalation and supported operational runbooks” instead addresses the requested architecture selection.
Question 874
Case study: Coastal logistics firm: Storage API pagination
Coastal logistics firm relies on Storage API pagination to deliver its operational commitments. The current architectural problem is that inventory script processes only the first page of Cloud Storage objects. The team has recorded this evidence: logs show listing stops at 1,000 objects despite millions in bucket. Any proposed response must preserve the requirement that compliance inventory must enumerate all object generations.
The Storage API pagination environment at Coastal logistics firm faces this issue: inventory script processes only the first page of Cloud Storage objects. Supporting evidence shows that logs show listing stops at 1,000 objects despite millions in bucket. The architect must preserve the requirement that compliance inventory must enumerate all object generations. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Assume one list call always returns an entire bucket
- Compare script count and generations to independent bucket inventory
- Watch page-token errors and missed generations
- Use the supported client-library iterator with explicit generation handling
Explanation
Correct Answer
C:
Watch page-token errors and missed generations reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (inventory script processes only the first page of Cloud Storage objects) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
Paginated APIs can omit most objects unless continued. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that compliance inventory must enumerate all object generations.
B:
The alternative “Compare script count and generations to independent bucket inventory” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, logs show listing stops at 1,000 objects despite millions in bucket. The option “Watch page-token errors and missed generations” instead addresses the requested ongoing operational assurance.
D:
The alternative “Use the supported client-library iterator with explicit generation handling” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, logs show listing stops at 1,000 objects despite millions in bucket. The option “Watch page-token errors and missed generations” instead addresses the requested ongoing operational assurance.
Question 875
At Green energy trading service, the runbook resilience workload has a documented risk: a repeated Cloud SQL failover is handled differently by each on-call engineer. The review found that incident notes show conflicting restart commands and missing escalation steps. The architecture must also ensure that financial settlement recovery must be repeatable and auditable. The team must deliver the approved control safely. Which deployment sequence is most appropriate?
- Train the response team using a shadow exercise and signed change review
- Create versioned runbooks and automated safe diagnostics with approval points
- Allow responders to improvise privileged database deletion during every outage
- Track runbook deviation, recovery duration and incomplete action items
Explanation
Correct Answer
A:
Train the response team using a shadow exercise and signed change review is a controlled means to introduce the approved architecture while meeting the requirement that financial settlement recovery must be repeatable and auditable. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
The alternative “Create versioned runbooks and automated safe diagnostics with approval points” describes the chosen design, but not how it is introduced safely. In the reported observation, incident notes show conflicting restart commands and missing escalation steps. The option “Train the response team using a shadow exercise and signed change review” instead addresses the requested controlled implementation.
C:
Uncontrolled destructive actions increase recovery risk. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that financial settlement recovery must be repeatable and auditable.
D:
The alternative “Track runbook deviation, recovery duration and incomplete action items” addresses later monitoring rather than the actual controlled deployment. In the reported observation, incident notes show conflicting restart commands and missing escalation steps. The option “Train the response team using a shadow exercise and signed change review” instead addresses the requested controlled implementation.
Question 876
Consider Neighborhood banking cooperative and its loan-origination approval service workload. The issue is that the planned monolith migration promises lower costs but omits the regulatory audit and branch-outage requirements; the current observation is that business interviews reveal a four-hour branch outage limit and an immutable decision-history obligation. The team must ensure that branches need approvals even when a regional WAN circuit fails. The target architecture is approved; execution without disruption is the remaining decision. Which rollout action is best?
- Track queue age, replay conflicts and branch recovery objectives
- Choose the cheapest single-zone VM and discard decision events once the API responds
- Design a regional approval API with durable event logging and a tested local queue for temporary disconnection
- Migrate one branch at a time with reconciled event replay and rollback
Explanation
Correct Answer
D:
Migrate one branch at a time with reconciled event replay and rollback is a controlled means to introduce the approved architecture while meeting the requirement that branches need approvals even when a regional WAN circuit fails. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Track queue age, replay conflicts and branch recovery objectives” addresses later monitoring rather than the actual controlled deployment. In the reported observation, business interviews reveal a four-hour branch outage limit and an immutable decision-history obligation. The option “Migrate one branch at a time with reconciled event replay and rollback” instead addresses the requested controlled implementation.
B:
Lower initial infrastructure cost does not satisfy auditable decisions or disconnected operation. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that branches need approvals even when a regional WAN circuit fails.
C:
The alternative “Design a regional approval API with durable event logging and a tested local queue for temporary disconnection” describes the chosen design, but not how it is introduced safely. In the reported observation, business interviews reveal a four-hour branch outage limit and an immutable decision-history obligation. The option “Migrate one branch at a time with reconciled event replay and rollback” instead addresses the requested controlled implementation.
Question 877
At National health data exchange, the Google Cloud design for service risk prioritization is affected because engineering spends most reliability effort on cosmetic dashboard errors while core clinical imports fail. A review found that error-budget report shows clinical file import has the worst user impact. The proposed response must account for the requirement that clinical data delivery requires a time-bound recovery process. Which controlled implementation should be used to preserve operational continuity during the change?
- Watch error-budget consumption and service-health priority drift
- Reallocate the next reliability work period with cross-team approval
- Prioritize operational improvements based on SLOs and measurable error budgets
- Choose the task with the largest number of low-impact tickets only
Explanation
Correct Answer
B:
Reallocate the next reliability work period with cross-team approval is a controlled means to introduce the approved architecture while meeting the requirement that clinical data delivery requires a time-bound recovery process. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Watch error-budget consumption and service-health priority drift” addresses later monitoring rather than the actual controlled deployment. In the reported observation, error-budget report shows clinical file import has the worst user impact. The option “Reallocate the next reliability work period with cross-team approval” instead addresses the requested controlled implementation.
C:
The alternative “Prioritize operational improvements based on SLOs and measurable error budgets” describes the chosen design, but not how it is introduced safely. In the reported observation, error-budget report shows clinical file import has the worst user impact. The option “Reallocate the next reliability work period with cross-team approval” instead addresses the requested controlled implementation.
D:
Ticket volume is a poor substitute for consequence and SLO impact. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that clinical data delivery requires a time-bound recovery process.
Question 878
Consider Public safety communications service and its Secret Manager credential lifecycle workload. The issue is that a service passes a database password through the deployment YAML; the current observation is that pipeline logs contain plaintext passwords used in production. The team must ensure that credentials must rotate without emergency downtime. The change committee needs to understand the current system rather than install a fix yet. What should it do?
- Use Secret Manager with per-workload access and controlled secret versioning
- Deploy consumers that read approved versions before retiring the old secret
- Locate credential copies, readers and rotation/dependency relationships
- Put the same plaintext password into a Kubernetes ConfigMap
Explanation
Correct Answer
C:
Locate credential copies, readers and rotation/dependency relationships is the appropriate diagnostic because the observation—pipeline logs contain plaintext passwords used in production—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (a service passes a database password through the deployment YAML) before the design is approved.
Incorrect Answers
A:
The alternative “Use Secret Manager with per-workload access and controlled secret versioning” is target architecture selection; it does not establish why the observed path failed. In the reported observation, pipeline logs contain plaintext passwords used in production. The option “Locate credential copies, readers and rotation/dependency relationships” instead addresses the requested root-cause evidence.
B:
The alternative “Deploy consumers that read approved versions before retiring the old secret” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, pipeline logs contain plaintext passwords used in production. The option “Locate credential copies, readers and rotation/dependency relationships” instead addresses the requested root-cause evidence.
D:
A ConfigMap alone does not secure the original secret. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that credentials must rotate without emergency downtime.
Question 879
The data pipeline incident triage environment at Education analytics cooperative faces this issue: daily analytics job silently drops events with previously unseen nullable fields. Supporting evidence shows that Dataflow error logs show schema deserialization failures after partner update. The architect must preserve the requirement that approved learning dashboards require source-to-target reconciliation. Which migration or rollout step best manages risk, dependencies and reversibility?
- Discard all unrecognized events without alerting
- Define versioned schemas with controlled evolution and quarantined invalid events
- Deploy tolerant parsers in staged pipelines with recovery of quarantined records
- Monitor schema rejection and lag by producer
Explanation
Correct Answer
C:
Deploy tolerant parsers in staged pipelines with recovery of quarantined records is a controlled means to introduce the approved architecture while meeting the requirement that approved learning dashboards require source-to-target reconciliation. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
Silent discards create false analytics that appear complete. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that approved learning dashboards require source-to-target reconciliation.
B:
The alternative “Define versioned schemas with controlled evolution and quarantined invalid events” describes the chosen design, but not how it is introduced safely. In the reported observation, Dataflow error logs show schema deserialization failures after partner update. The option “Deploy tolerant parsers in staged pipelines with recovery of quarantined records” instead addresses the requested controlled implementation.
D:
The alternative “Monitor schema rejection and lag by producer” addresses later monitoring rather than the actual controlled deployment. In the reported observation, Dataflow error logs show schema deserialization failures after partner update. The option “Deploy tolerant parsers in staged pipelines with recovery of quarantined records” instead addresses the requested controlled implementation.
Question 880
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 Google Cloud design for organizational change management is affected because field employees reject a new cloud harvest portal because offline workflows were removed. A review found that usability survey shows farmers cannot record deliveries during cellular loss. The proposed response must account for the requirement that offline data capture is required for the harvest season. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?
- Verify actual delivery capture and reconciliation in a no-signal exercise
- Declare change successful because the web portal was deployed
- Track adoption, support calls and sync conflicts
- Design product adoption with offline capture and clear sync accountability
Explanation
Correct Answer
C:
Track adoption, support calls and sync conflicts reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (field employees reject a new cloud harvest portal because offline workflows were removed) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Verify actual delivery capture and reconciliation in a no-signal exercise” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, usability survey shows farmers cannot record deliveries during cellular loss. The option “Track adoption, support calls and sync conflicts” instead addresses the requested ongoing operational assurance.
B:
Deployment alone does not establish that users can complete business work. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that offline data capture is required for the harvest season.
D:
The alternative “Design product adoption with offline capture and clear sync accountability” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, usability survey shows farmers cannot record deliveries during cellular loss. The option “Track adoption, support calls and sync conflicts” instead addresses the requested ongoing operational assurance.