Google Professional Cloud Architect Practice Test 11
Question 100
At Regional mapping institute, the Google Cloud design for Cloud Shell access hygiene is affected because analysts share one long-lived service account key inside a notebook for gcloud access. A review found that repository audit finds the key in notebook history. The proposed response must account for the requirement that interactive analysts need attributable access without downloaded secrets. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?
- Use individual user authentication and short-lived impersonation for scoped tasks
- Move the service account JSON into a hidden notebook cell
- Map user identities, command permissions and persistent key copies
- Remove compromised keys and update training notebooks with safe CLI setup
Explanation
Correct Answer
C:
Map user identities, command permissions and persistent key copies is the appropriate diagnostic because the observation—repository audit finds the key in notebook history—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (analysts share one long-lived service account key inside a notebook for gcloud access) before the design is approved.
Incorrect Answers
A:
The alternative “Use individual user authentication and short-lived impersonation for scoped tasks” is target architecture selection; it does not establish why the observed path failed. In the reported observation, repository audit finds the key in notebook history. The option “Map user identities, command permissions and persistent key copies” instead addresses the requested root-cause evidence.
B:
A hidden cell does not revoke or protect embedded credentials. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that interactive analysts need attributable access without downloaded secrets.
D:
The alternative “Remove compromised keys and update training notebooks with safe CLI setup” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, repository audit finds the key in notebook history. The option “Map user identities, command permissions and persistent key copies” instead addresses the requested root-cause evidence.
Question 101
Case study: Telehealth teleconsultation: regulated regional failover
Telehealth teleconsultation relies on regulated regional failover to deliver its operational commitments. The current architectural problem is that the recovery design sends patient consultations to a region forbidden by local processing rules. The team has recorded this evidence: failover plan lists a default backup service on another continent. Any proposed response must preserve the requirement that clinical service must be recoverable inside approved national boundaries.
The regulated regional failover environment at Telehealth teleconsultation faces this issue: the recovery design sends patient consultations to a region forbidden by local processing rules. Supporting evidence shows that failover plan lists a default backup service on another continent. The architect must preserve the requirement that clinical service must be recoverable inside approved national boundaries. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Assume a foreign backup region is always allowed during emergencies
- Design in-country redundant service and storage with compliant backup
- Monitor regional replication, legal changes and failover access logs
- Disconnect the primary and verify sessions never cross prohibited geography
Explanation
Correct Answer
C:
Monitor regional replication, legal changes and failover access logs reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (the recovery design sends patient consultations to a region forbidden by local processing rules) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
Emergency operations do not automatically waive data residency laws. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that clinical service must be recoverable inside approved national boundaries.
B:
The alternative “Design in-country redundant service and storage with compliant backup” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, failover plan lists a default backup service on another continent. The option “Monitor regional replication, legal changes and failover access logs” instead addresses the requested ongoing operational assurance.
D:
The alternative “Disconnect the primary and verify sessions never cross prohibited geography” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, failover plan lists a default backup service on another continent. The option “Monitor regional replication, legal changes and failover access logs” instead addresses the requested ongoing operational assurance.
Question 102
At National retail pharmacy, the Google Cloud design for support ownership between vendors is affected because a Cloud Run API fails because a third-party payment gateway responds too slowly. A review found that traces show all application calls blocked on an external vendor timeout. The proposed response must account for the requirement that pharmacy payments require a documented fallback and escalation plan. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Isolate vendor-specific latency from internal service failures
- Roll out timeouts and safe manual settlement fallback with partner coordination
- Define circuit breakers, vendor escalation and timeout error handling
- Keep every request waiting indefinitely for vendor recovery
- Monitor vendor timeouts and unresolved escalation tickets
Explanation
Correct Answers
B:
Roll out timeouts and safe manual settlement fallback with partner coordination is a controlled means to introduce the approved architecture while meeting the requirement that pharmacy payments require a documented fallback and escalation plan. 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.
C:
Define circuit breakers, vendor escalation and timeout error handling targets the underlying issue (a Cloud Run API fails because a third-party payment gateway responds too slowly) rather than merely reporting symptoms. It also preserves the required outcome (pharmacy payments require a documented fallback and escalation plan), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
Incorrect Answers
A:
This diagnoses the original issue (a Cloud Run API fails because a third-party payment gateway responds too slowly), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
D:
Unbounded waits exhaust local resources and disrupt all customers. The shortcut does not supply the requested design and safe rollout for support ownership between vendors, where traces show all application calls blocked on an external vendor timeout.
E:
Monitoring support ownership between vendors for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: a Cloud Run API fails because a third-party payment gateway responds too slowly.
Question 103
At Public transportation authority, the Google Cloud design for organization location constraint is affected because test projects in an overseas region unexpectedly receive personal commuter data. A review found that resource inventory shows unrestricted region creation in folder projects. The proposed response must account for the requirement that all raw rider IDs must remain in the designated country. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?
- Stage policy constraints for new projects then move existing assets safely
- Apply supported organization location restrictions and approved regional storage architecture
- Identify data-flow locations and policy inheritance across projects
- Document a preferred region but leave cloud APIs unrestricted
Explanation
Correct Answer
C:
Identify data-flow locations and policy inheritance across projects is the appropriate diagnostic because the observation—resource inventory shows unrestricted region creation in folder projects—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (test projects in an overseas region unexpectedly receive personal commuter data) before the design is approved.
Incorrect Answers
A:
The alternative “Stage policy constraints for new projects then move existing assets safely” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, resource inventory shows unrestricted region creation in folder projects. The option “Identify data-flow locations and policy inheritance across projects” instead addresses the requested root-cause evidence.
B:
The alternative “Apply supported organization location restrictions and approved regional storage architecture” is target architecture selection; it does not establish why the observed path failed. In the reported observation, resource inventory shows unrestricted region creation in folder projects. The option “Identify data-flow locations and policy inheritance across projects” instead addresses the requested root-cause evidence.
D:
A recommendation alone does not prevent prohibited region deployments. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that all raw rider IDs must remain in the designated country.
Question 104
At Regional newspaper platform, the automated infrastructure catalog workload has a documented risk: each team manually creates different VM images for the same application tier. The review found that asset review shows inconsistent IAM, patch settings and logging between regions. The architecture must also ensure that new sites must have consistent repeatable baseline controls. What enduring Google Cloud design should the team choose now that the failure mode is understood?
- Let each engineer edit production resources manually without recording changes
- Monitor module drift, change approvals and obsolete versions
- Inventory approved resource models, drift and team ownership
- Publish reusable Terraform modules with policy tests and documented ownership
Explanation
Correct Answer
D:
Publish reusable Terraform modules with policy tests and documented ownership targets the underlying issue (each team manually creates different VM images for the same application tier) rather than merely reporting symptoms. It also preserves the required outcome (new sites must have consistent repeatable baseline controls), which a target-state design must satisfy.
Incorrect Answers
A:
Manual one-off changes are hard to reproduce or audit. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that new sites must have consistent repeatable baseline controls.
B:
The alternative “Monitor module drift, change approvals and obsolete versions” measures results without defining the preventive design now required. In the reported observation, asset review shows inconsistent IAM, patch settings and logging between regions. The option “Publish reusable Terraform modules with policy tests and documented ownership” instead addresses the requested architecture selection.
C:
The alternative “Inventory approved resource models, drift and team ownership” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, asset review shows inconsistent IAM, patch settings and logging between regions. The option “Publish reusable Terraform modules with policy tests and documented ownership” instead addresses the requested architecture selection.
Question 105
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.
The organizational change management environment at International agriculture co-op faces this issue: field employees reject a new cloud harvest portal because offline workflows were removed. Supporting evidence shows that usability survey shows farmers cannot record deliveries during cellular loss. The architect must preserve the requirement that offline data capture is required for the harvest season. Choose the architecture that resolves the documented weakness without breaching the operational constraint.
- Design product adoption with offline capture and clear sync accountability
- Interview field users and prioritize their required offline workflows
- Track adoption, support calls and sync conflicts
- Declare change successful because the web portal was deployed
Explanation
Correct Answer
A:
Design product adoption with offline capture and clear sync accountability targets the underlying issue (field employees reject a new cloud harvest portal because offline workflows were removed) rather than merely reporting symptoms. It also preserves the required outcome (offline data capture is required for the harvest season), which a target-state design must satisfy.
Incorrect Answers
B:
The alternative “Interview field users and prioritize their required offline workflows” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, usability survey shows farmers cannot record deliveries during cellular loss. The option “Design product adoption with offline capture and clear sync accountability” instead addresses the requested architecture selection.
C:
The alternative “Track adoption, support calls and sync conflicts” measures results without defining the preventive design now required. In the reported observation, usability survey shows farmers cannot record deliveries during cellular loss. The option “Design product adoption with offline capture and clear sync accountability” instead addresses the requested architecture selection.
D:
Deployment alone does not establish that users can complete business work. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that offline data capture is required for the harvest season.
Question 106
Consider University astronomy project and its temporary sky-image processing workload. The issue is that large image batch runs only one weekend a month yet reserved VMs are always on; the current observation is that cost report shows accelerator nodes idle more than ninety percent of the time. The team must ensure that scientific jobs can checkpoint and resume after interruption. Which continuous monitoring approach best reveals recurrence or changing dependencies?
- Interrupt workers deliberately and verify reproducible processed outputs
- Use spot capacity for the only stateful database with no recovery strategy
- Use job orchestration with Spot VMs for interruptible batch computation
- Track GPU idle hours, interruption rates and batch cost
Explanation
Correct Answer
D:
Track GPU idle hours, interruption rates and batch cost reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (large image batch runs only one weekend a month yet reserved VMs are always on) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Interrupt workers deliberately and verify reproducible processed outputs” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, cost report shows accelerator nodes idle more than ninety percent of the time. The option “Track GPU idle hours, interruption rates and batch cost” instead addresses the requested ongoing operational assurance.
B:
Preemptible nodes are unsuitable as unprotected authoritative state. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that scientific jobs can checkpoint and resume after interruption.
C:
The alternative “Use job orchestration with Spot VMs for interruptible batch computation” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, cost report shows accelerator nodes idle more than ninety percent of the time. The option “Track GPU idle hours, interruption rates and batch cost” instead addresses the requested ongoing operational assurance.
Question 107
At Education research foundation, the multi-project packet filtering workload has a documented risk: research projects inherit inconsistent firewall rules and centralized policy has no owner. The review found that network review finds SSH open to the internet from three experiment subnets. The architecture must also ensure that a limited set of approved remote researchers still needs audited access. The team must deliver the approved control safely. Which deployment sequence is most appropriate?
- Set hierarchy-level firewall controls with least-privilege project overrides
- Apply deny policies in monitored phases with approved access exceptions
- Monitor firewall-rule drift and exception expiry by project
- Let every project administrator create a public any-any ingress rule
Explanation
Correct Answer
B:
Apply deny policies in monitored phases with approved access exceptions is a controlled means to introduce the approved architecture while meeting the requirement that a limited set of approved remote researchers still needs audited access. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Set hierarchy-level firewall controls with least-privilege project overrides” describes the chosen design, but not how it is introduced safely. In the reported observation, network review finds SSH open to the internet from three experiment subnets. The option “Apply deny policies in monitored phases with approved access exceptions” instead addresses the requested controlled implementation.
C:
The alternative “Monitor firewall-rule drift and exception expiry by project” addresses later monitoring rather than the actual controlled deployment. In the reported observation, network review finds SSH open to the internet from three experiment subnets. The option “Apply deny policies in monitored phases with approved access exceptions” instead addresses the requested controlled implementation.
D:
Unrestricted local firewalls defeat centralized protection. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that a limited set of approved remote researchers still needs audited access.
Question 108
Consider European media distributor and its content recommendation evolution workload. The issue is that recommendation service is tied to one proprietary model endpoint and cannot adapt to new languages; the current observation is that product roadmap adds five languages and stricter content ranking rules next year. The team must ensure that existing subscribers must keep playback uninterrupted. Which acceptance test should demonstrate both protection against the failure and continued authorized service?
- Forecast model and language demand against content-governance obligations
- Measure ranking quality and contract compatibility across model upgrades
- Hardcode one unversioned provider response into the user profile schema
- Introduce compatibility tests for new language models with staged cohort activation
Explanation
Correct Answer
B:
Measure ranking quality and contract compatibility across model upgrades is a direct acceptance test of the path implicated by product roadmap adds five languages and stricter content ranking rules next year. It checks that the original risk (recommendation service is tied to one proprietary model endpoint and cannot adapt to new languages) has actually been controlled and tests that permitted operations still meet the requirement that existing subscribers must keep playback uninterrupted.
Incorrect Answers
A:
The alternative “Forecast model and language demand against content-governance obligations” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, product roadmap adds five languages and stricter content ranking rules next year. The option “Measure ranking quality and contract compatibility across model upgrades” instead addresses the requested acceptance verification.
C:
A brittle API contract blocks planned language expansion. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that existing subscribers must keep playback uninterrupted.
D:
The alternative “Introduce compatibility tests for new language models with staged cohort activation” documents change execution but not its operational acceptance result. In the reported observation, product roadmap adds five languages and stricter content ranking rules next year. The option “Measure ranking quality and contract compatibility across model upgrades” instead addresses the requested acceptance verification.
Question 109
The cost governance of abandoned environments environment at International renewable energy fund faces this issue: unused development clusters persist after quarter-end project closures. Supporting evidence shows that billing export shows idle infrastructure without current cost owner. The architect must preserve the requirement that audit requirements retain records but not unused compute. Choose the architecture that resolves the documented weakness without breaching the operational constraint.
- Watch stale projects, budget alerts and reactivated resources
- Set lifecycle policies and project budgets with approved archival before deletion
- Delete every project including protected regulatory evidence without review
- Map workloads, cleanup ownership and retention dependencies
Explanation
Correct Answer
B:
Set lifecycle policies and project budgets with approved archival before deletion targets the underlying issue (unused development clusters persist after quarter-end project closures) rather than merely reporting symptoms. It also preserves the required outcome (audit requirements retain records but not unused compute), which a target-state design must satisfy.
Incorrect Answers
A:
The alternative “Watch stale projects, budget alerts and reactivated resources” measures results without defining the preventive design now required. In the reported observation, billing export shows idle infrastructure without current cost owner. The option “Set lifecycle policies and project budgets with approved archival before deletion” instead addresses the requested architecture selection.
C:
Unreviewed cleanup can destroy necessary retained records. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that audit requirements retain records but not unused compute.
D:
The alternative “Map workloads, cleanup ownership and retention dependencies” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, billing export shows idle infrastructure without current cost owner. The option “Set lifecycle policies and project budgets with approved archival before deletion” instead addresses the requested architecture selection.
Question 110
The multilingual customer request assistant environment at Multinational travel support service faces this issue: an architecture team confuses basic FAQ retrieval with an agent allowed to change reservations. Supporting evidence shows that requirements show ticket search and refund actions have different authorization obligations. The architect must preserve the requirement that refunds require authenticated approval and audit. Before approving a solution, which analysis most directly clarifies the underlying dependency or control gap?
- Separate information retrieval, conversational reasoning and privileged transactions
- Give every search result direct permission to execute refund APIs
- Use a grounded search-based assistant and keep refund execution behind an authenticated tool policy
- Deploy read-only answers first and then gated action flows
Explanation
Correct Answer
A:
Separate information retrieval, conversational reasoning and privileged transactions is the appropriate diagnostic because the observation—requirements show ticket search and refund actions have different authorization obligations—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (an architecture team confuses basic FAQ retrieval with an agent allowed to change reservations) before the design is approved.
Incorrect Answers
B:
Retrieved text is untrusted input, not authorization. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that refunds require authenticated approval and audit.
C:
The alternative “Use a grounded search-based assistant and keep refund execution behind an authenticated tool policy” is target architecture selection; it does not establish why the observed path failed. In the reported observation, requirements show ticket search and refund actions have different authorization obligations. The option “Separate information retrieval, conversational reasoning and privileged transactions” instead addresses the requested root-cause evidence.
D:
The alternative “Deploy read-only answers first and then gated action flows” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, requirements show ticket search and refund actions have different authorization obligations. The option “Separate information retrieval, conversational reasoning and privileged transactions” instead addresses the requested root-cause evidence.