Google Professional Cloud Architect Practice Test 20
Question 190
At Retail healthcare supplier, the Cloud Run canary release workload has a documented risk: a monolithic new API revision receives 100% of traffic and breaks patient orders. The review found that release journal shows no canary or rollback criterion. The architecture must also ensure that approved orders must continue during application upgrades. Which post-change test most reliably distinguishes a functioning control from a merely successful installation?
- Replace the production revision all at once and delete the prior image
- Shift a small traffic percentage and widen only when health gates pass
- Analyze failure budget, revision behavior and traffic splitting needs
- Inject a regression into a canary and confirm automatic/manual rollback meets SLO
Explanation
Correct Answer
D:
Inject a regression into a canary and confirm automatic/manual rollback meets SLO is a direct acceptance test of the path implicated by release journal shows no canary or rollback criterion. It checks that the original risk (a monolithic new API revision receives 100% of traffic and breaks patient orders) has actually been controlled and tests that permitted operations still meet the requirement that approved orders must continue during application upgrades.
Incorrect Answers
A:
An irreversible full cutover magnifies deployment failure. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that approved orders must continue during application upgrades.
B:
The alternative “Shift a small traffic percentage and widen only when health gates pass” documents change execution but not its operational acceptance result. In the reported observation, release journal shows no canary or rollback criterion. The option “Inject a regression into a canary and confirm automatic/manual rollback meets SLO” instead addresses the requested acceptance verification.
C:
The alternative “Analyze failure budget, revision behavior and traffic splitting needs” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, release journal shows no canary or rollback criterion. The option “Inject a regression into a canary and confirm automatic/manual rollback meets SLO” instead addresses the requested acceptance verification.
Question 191
At Regional healthcare network, the cross-team incident communication workload has a documented risk: operations and security teams issue conflicting statements during a cloud authentication incident. The review found that timeline shows two status pages disagreed on user impact. The architecture must also ensure that patient portals require one accountable incident communication path. What follow-up metric or alert will identify emerging failures after the initial acceptance test?
- Let every engineer publish its own unverified outage explanation
- Create a single incident command and evidence-qualified status communication plan
- Run a tabletop and verify correct internal and external messages
- Watch approval delays, contradictory updates and stakeholder confusion
Explanation
Correct Answer
D:
Watch approval delays, contradictory updates and stakeholder confusion reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (operations and security teams issue conflicting statements during a cloud authentication incident) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
Uncoordinated messaging can misstate patient impact. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that patient portals require one accountable incident communication path.
B:
The alternative “Create a single incident command and evidence-qualified status communication plan” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, timeline shows two status pages disagreed on user impact. The option “Watch approval delays, contradictory updates and stakeholder confusion” instead addresses the requested ongoing operational assurance.
C:
The alternative “Run a tabletop and verify correct internal and external messages” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, timeline shows two status pages disagreed on user impact. The option “Watch approval delays, contradictory updates and stakeholder confusion” instead addresses the requested ongoing operational assurance.
Question 192
The service account impersonation environment at Large airline revenue group faces this issue: automation assumes project Editor role is required to invoke one reporting job. Supporting evidence shows that permission audit shows callers can create keys and change unrelated resources. The architect must preserve the requirement that billing reads must use auditable least privilege. What test must pass before the business accepts the remediated architecture?
- Prove the job runs but cannot modify unrelated billing data
- Migrate callers to short-lived access tokens and disable downloaded keys
- Map exact permissions and impersonation token flows
- Use a downloaded project Owner key for every reporting job
Explanation
Correct Answer
A:
Prove the job runs but cannot modify unrelated billing data is a direct acceptance test of the path implicated by permission audit shows callers can create keys and change unrelated resources. It checks that the original risk (automation assumes project Editor role is required to invoke one reporting job) has actually been controlled and tests that permitted operations still meet the requirement that billing reads must use auditable least privilege.
Incorrect Answers
B:
The alternative “Migrate callers to short-lived access tokens and disable downloaded keys” documents change execution but not its operational acceptance result. In the reported observation, permission audit shows callers can create keys and change unrelated resources. The option “Prove the job runs but cannot modify unrelated billing data” instead addresses the requested acceptance verification.
C:
The alternative “Map exact permissions and impersonation token flows” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, permission audit shows callers can create keys and change unrelated resources. The option “Prove the job runs but cannot modify unrelated billing data” instead addresses the requested acceptance verification.
D:
Overprivileged permanent keys greatly increase compromise impact. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that billing reads must use auditable least privilege.
Question 193
European media distributor plans to update content recommendation evolution. Investigators found that product roadmap adds five languages and stricter content ranking rules next year, consistent with the reported problem that recommendation service is tied to one proprietary model endpoint and cannot adapt to new languages. The response must satisfy the requirement that existing subscribers must keep playback uninterrupted. The design review is over and production introduction is next. Which action is the best fit?
- Track deprecation notices, bias drift and API costs
- Introduce compatibility tests for new language models with staged cohort activation
- Hardcode one unversioned provider response into the user profile schema
- Adopt versioned model contracts and independent feature pipelines that can evolve
Explanation
Correct Answer
B:
Introduce compatibility tests for new language models with staged cohort activation is a controlled means to introduce the approved architecture while meeting the requirement that existing subscribers must keep playback uninterrupted. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Track deprecation notices, bias drift and API costs” addresses later monitoring rather than the actual controlled deployment. In the reported observation, product roadmap adds five languages and stricter content ranking rules next year. The option “Introduce compatibility tests for new language models with staged cohort activation” instead addresses the requested controlled implementation.
C:
A brittle API contract blocks planned language expansion. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that existing subscribers must keep playback uninterrupted.
D:
The alternative “Adopt versioned model contracts and independent feature pipelines that can evolve” describes the chosen design, but not how it is introduced safely. In the reported observation, product roadmap adds five languages and stricter content ranking rules next year. The option “Introduce compatibility tests for new language models with staged cohort activation” instead addresses the requested controlled implementation.
Question 194
The large immutable scans environment at Clinical imaging archive faces this issue: imaging staff need object retention but architects chose a file share for infrequently accessed studies. Supporting evidence shows that inventory shows petabytes of immutable DICOM objects with annual reads. The architect must preserve the requirement that specific clinical records have mandatory retention and legal hold. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Monitor lifecycle transitions, retention exceptions and retrieval charges
- Use Cloud Storage with appropriate storage classes and retention policies for immutable objects
- Use only an ephemeral instance boot disk for the master archive
- Restore random samples and confirm legal hold denies unauthorized deletions
Explanation
Correct Answer
A:
Monitor lifecycle transitions, retention exceptions and retrieval charges reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (imaging staff need object retention but architects chose a file share for infrequently accessed studies) rather than treating the first successful test as permanent assurance.
Incorrect Answers
B:
The alternative “Use Cloud Storage with appropriate storage classes and retention policies for immutable objects” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, inventory shows petabytes of immutable DICOM objects with annual reads. The option “Monitor lifecycle transitions, retention exceptions and retrieval charges” instead addresses the requested ongoing operational assurance.
C:
Boot disks lack appropriate durable retention and lifecycle governance. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that specific clinical records have mandatory retention and legal hold.
D:
The alternative “Restore random samples and confirm legal hold denies unauthorized deletions” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, inventory shows petabytes of immutable DICOM objects with annual reads. The option “Monitor lifecycle transitions, retention exceptions and retrieval charges” instead addresses the requested ongoing operational assurance.
Question 195
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.
The low-latency dispatch API environment at Regional transport network faces this issue: dispatch requests cross the internet to an API hosted in another region. Supporting evidence shows that flow logs show round trips go through a centralized NAT despite local backends. The architect must preserve the requirement that private dispatch callers require restricted routing and prompt responses. Choose the architecture that resolves the documented weakness without breaching the operational constraint.
- Monitor backend health, route changes and private latency
- Put a public forwarding rule on every internal backend for simplicity
- Inspect hybrid route tables, peering limitations and service DNS
- Choose regional internal load balancing and private connectivity paths
Explanation
Correct Answer
D:
Choose regional internal load balancing and private connectivity paths targets the underlying issue (dispatch requests cross the internet to an API hosted in another region) rather than merely reporting symptoms. It also preserves the required outcome (private dispatch callers require restricted routing and prompt responses), which a target-state design must satisfy.
Incorrect Answers
A:
The alternative “Monitor backend health, route changes and private latency” measures results without defining the preventive design now required. In the reported observation, flow logs show round trips go through a centralized NAT despite local backends. The option “Choose regional internal load balancing and private connectivity paths” instead addresses the requested architecture selection.
B:
Public ingress violates the explicit private dispatch boundary. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that private dispatch callers require restricted routing and prompt responses.
C:
The alternative “Inspect hybrid route tables, peering limitations and service DNS” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, flow logs show round trips go through a centralized NAT despite local backends. The option “Choose regional internal load balancing and private connectivity paths” instead addresses the requested architecture selection.
Question 196
The GKE node-upgrade safety environment at Healthcare AI supplier faces this issue: a node upgrade evicts all inference replicas because they share one failure domain. Supporting evidence shows that cluster events show two replicas pinned to the same maintenance pool. The architect must preserve the requirement that inference must remain available during security patching. Before approving a solution, which analysis most directly clarifies the underlying dependency or control gap?
- Set replica count to one and disable disruption checks
- Design multi-zone GKE scheduling with PodDisruptionBudget and appropriate replicas
- Inspect pod affinity, disruption budgets and node-pool placement
- Move one replica and drain one node per upgrade wave
Explanation
Correct Answer
C:
Inspect pod affinity, disruption budgets and node-pool placement is the appropriate diagnostic because the observation—cluster events show two replicas pinned to the same maintenance pool—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (a node upgrade evicts all inference replicas because they share one failure domain) before the design is approved.
Incorrect Answers
A:
A single replica cannot tolerate a node drain. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that inference must remain available during security patching.
B:
The alternative “Design multi-zone GKE scheduling with PodDisruptionBudget and appropriate replicas” is target architecture selection; it does not establish why the observed path failed. In the reported observation, cluster events show two replicas pinned to the same maintenance pool. The option “Inspect pod affinity, disruption budgets and node-pool placement” instead addresses the requested root-cause evidence.
D:
The alternative “Move one replica and drain one node per upgrade wave” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, cluster events show two replicas pinned to the same maintenance pool. The option “Inspect pod affinity, disruption budgets and node-pool placement” instead addresses the requested root-cause evidence.
Question 197
Case study: Regional public broadcaster: license-compliant migration planning
Regional public broadcaster relies on license-compliant migration planning to deliver its operational commitments. The current architectural problem is that cloud project budget ignores legacy transcoding license entitlements. The team has recorded this evidence: vendor contract requires designated cores and annual renewal. Any proposed response must preserve the requirement that broadcast licensing must remain valid across hybrid operation.
Regional public broadcaster plans to update license-compliant migration planning. Investigators found that vendor contract requires designated cores and annual renewal, consistent with the reported problem that cloud project budget ignores legacy transcoding license entitlements. The response must satisfy the requirement that broadcast licensing must remain valid across hybrid operation. The team needs an operations signal rather than another design or one-time test. What should it track?
- Assume cloud pay-as-you-go billing automatically grants third-party software licenses
- Choose a hosting disposition reflecting license and future refactor cost
- Track unlicensed deployments and upcoming support changes
- Compare total budget and deployed licensed cores after cutover
Explanation
Correct Answer
C:
Track unlicensed deployments and upcoming support changes reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (cloud project budget ignores legacy transcoding license entitlements) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
Infrastructure payment does not confer separate application rights. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that broadcast licensing must remain valid across hybrid operation.
B:
The alternative “Choose a hosting disposition reflecting license and future refactor cost” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, vendor contract requires designated cores and annual renewal. The option “Track unlicensed deployments and upcoming support changes” instead addresses the requested ongoing operational assurance.
D:
The alternative “Compare total budget and deployed licensed cores after cutover” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, vendor contract requires designated cores and annual renewal. The option “Track unlicensed deployments and upcoming support changes” instead addresses the requested ongoing operational assurance.
Question 198
At Municipal permit office, the Google Cloud design for digital permit filing is affected because stakeholders propose a simple document store without cross-department approval traceability. A review found that a discovery workshop finds six approval signatures and statutory retention deadlines. The proposed response must account for the requirement that citizens must see accurate permit status across agencies. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?
- Track unsigned workflow exceptions and retention-policy drift
- Use an auditable workflow with durable state transitions and immutable original attachments
- Verify every signed approval is linked to one permit version and visible to authorized users
- Replace all human approvals with a single anonymous automated approval
Explanation
Correct Answer
A:
Track unsigned workflow exceptions and retention-policy drift reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (stakeholders propose a simple document store without cross-department approval traceability) rather than treating the first successful test as permanent assurance.
Incorrect Answers
B:
The alternative “Use an auditable workflow with durable state transitions and immutable original attachments” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, a discovery workshop finds six approval signatures and statutory retention deadlines. The option “Track unsigned workflow exceptions and retention-policy drift” instead addresses the requested ongoing operational assurance.
C:
The alternative “Verify every signed approval is linked to one permit version and visible to authorized users” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, a discovery workshop finds six approval signatures and statutory retention deadlines. The option “Track unsigned workflow exceptions and retention-policy drift” instead addresses the requested ongoing operational assurance.
D:
An unaccountable shortcut cannot satisfy multi-agency statutory approval. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that citizens must see accurate permit status across agencies.
Question 199
Consider National land registry and its admin console access workload. The issue is that staff directly expose internal admin dashboards through public VM IPs; the current observation is that network scan discovers admin endpoints reachable without identity-aware gateway. The team must ensure that authorized clerks must access remotely without public administrative ingress. Which acceptance test should demonstrate both protection against the failure and continued authorized service?
- Add a public allow-all firewall rule with obscured URL paths
- Verify unauthorized principal denied and authorized clerk session logged
- Cut over clerks through IAP and remove public admin access safely
- Inspect admin application authentication, network paths and role needs
Explanation
Correct Answer
B:
Verify unauthorized principal denied and authorized clerk session logged is a direct acceptance test of the path implicated by network scan discovers admin endpoints reachable without identity-aware gateway. It checks that the original risk (staff directly expose internal admin dashboards through public VM IPs) has actually been controlled and tests that permitted operations still meet the requirement that authorized clerks must access remotely without public administrative ingress.
Incorrect Answers
A:
Obscure paths do not restrict authenticated administrative access. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that authorized clerks must access remotely without public administrative ingress.
C:
The alternative “Cut over clerks through IAP and remove public admin access safely” documents change execution but not its operational acceptance result. In the reported observation, network scan discovers admin endpoints reachable without identity-aware gateway. The option “Verify unauthorized principal denied and authorized clerk session logged” instead addresses the requested acceptance verification.
D:
The alternative “Inspect admin application authentication, network paths and role needs” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, network scan discovers admin endpoints reachable without identity-aware gateway. The option “Verify unauthorized principal denied and authorized clerk session logged” instead addresses the requested acceptance verification.
Question 200
At Financial remittance company, the Google Cloud design for card token ledger is affected because a transactional SQL database runs out of horizontal write capacity across continents. A review found that design review finds one region primary is a regulatory single point of failure. The proposed response must account for the requirement that ledger updates require strongly consistent multi-region transactions. A deployment ticket has been closed. What direct evidence would justify solution signoff?
- Stage dual-run ledger comparison and migrate one currency corridor
- Reconcile unique transfer IDs and fail a region during concurrent writes
- Create independent writable ledgers and reconcile disputed balances weekly
- Test geographic commit latency and exact data-sovereignty requirements
Explanation
Correct Answer
B:
Reconcile unique transfer IDs and fail a region during concurrent writes is a direct acceptance test of the path implicated by design review finds one region primary is a regulatory single point of failure. It checks that the original risk (a transactional SQL database runs out of horizontal write capacity across continents) has actually been controlled and tests that permitted operations still meet the requirement that ledger updates require strongly consistent multi-region transactions.
Incorrect Answers
A:
The alternative “Stage dual-run ledger comparison and migrate one currency corridor” documents change execution but not its operational acceptance result. In the reported observation, design review finds one region primary is a regulatory single point of failure. The option “Reconcile unique transfer IDs and fail a region during concurrent writes” instead addresses the requested acceptance verification.
C:
Deferred conflict reconciliation is unacceptable for money movement. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that ledger updates require strongly consistent multi-region transactions.
D:
The alternative “Test geographic commit latency and exact data-sovereignty requirements” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, design review finds one region primary is a regulatory single point of failure. The option “Reconcile unique transfer IDs and fail a region during concurrent writes” instead addresses the requested acceptance verification.