Google Professional Cloud Architect Practice Test 10
Question 90
The shared IAM inheritance environment at Multinational consulting alliance faces this issue: a merger added interns to a group that has editor permission on financial-production resources. Supporting evidence shows that IAM policy audit shows project roles inherited from the organization root. The architect must preserve the requirement that production access must be limited to verified operational duties. Which migration or rollout step best manages risk, dependencies and reversibility?
- Stage grant changes with access simulation and validated rollback
- Create a new group but keep the old wildcard organization binding
- Move broad grants to scoped groups and use conditional role bindings where appropriate
- Watch group membership changes and inherited privilege escalation
Explanation
Correct Answer
A:
Stage grant changes with access simulation and validated rollback is a controlled means to introduce the approved architecture while meeting the requirement that production access must be limited to verified operational duties. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
A new group does not negate an existing broad inherited permission. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that production access must be limited to verified operational duties.
C:
The alternative “Move broad grants to scoped groups and use conditional role bindings where appropriate” describes the chosen design, but not how it is introduced safely. In the reported observation, IAM policy audit shows project roles inherited from the organization root. The option “Stage grant changes with access simulation and validated rollback” instead addresses the requested controlled implementation.
D:
The alternative “Watch group membership changes and inherited privilege escalation” addresses later monitoring rather than the actual controlled deployment. In the reported observation, IAM policy audit shows project roles inherited from the organization root. The option “Stage grant changes with access simulation and validated rollback” instead addresses the requested controlled implementation.
Question 91
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.
Online language tutoring platform plans to update GKE API worker capacity. Investigators found that pod telemetry shows low CPU but growing Pub/Sub outstanding messages, consistent with the reported problem that CPU-based scaling alone misses a backlog of asynchronous translation requests. The response must satisfy the requirement that tutoring sessions require backlogs to clear in under two minutes. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?
- Use workload autoscaling based on meaningful request or queue metrics
- Measure backlog age, per-request time and pod resource bounds
- Stage HPA/KEDA equivalent scaling configuration with quota safeguards
- Increase CPU limits but keep one replica regardless of queue depth
Explanation
Correct Answer
B:
Measure backlog age, per-request time and pod resource bounds is the appropriate diagnostic because the observation—pod telemetry shows low CPU but growing Pub/Sub outstanding messages—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (CPU-based scaling alone misses a backlog of asynchronous translation requests) before the design is approved.
Incorrect Answers
A:
The alternative “Use workload autoscaling based on meaningful request or queue metrics” is target architecture selection; it does not establish why the observed path failed. In the reported observation, pod telemetry shows low CPU but growing Pub/Sub outstanding messages. The option “Measure backlog age, per-request time and pod resource bounds” instead addresses the requested root-cause evidence.
C:
The alternative “Stage HPA/KEDA equivalent scaling configuration with quota safeguards” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, pod telemetry shows low CPU but growing Pub/Sub outstanding messages. The option “Measure backlog age, per-request time and pod resource bounds” instead addresses the requested root-cause evidence.
D:
A fixed replica count cannot scale with independent queue pressure. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that tutoring sessions require backlogs to clear in under two minutes.
Question 92
University student services plans to update support cost decision. Investigators found that cost report shows request demand peaks 20x within minutes, consistent with the reported problem that finance wants to optimize Cloud Run spending by terminating instances during exam registration. The response must satisfy the requirement that students must be able to submit registration before hard deadlines. The approved change has been applied. Which validation provides the clearest evidence the original problem is fixed?
- Measure peak registration completion and cost per successful submission
- Trial concurrency and min-instance changes outside peak periods
- Model workload demand, latency cost of cold starts and peak business value
- Set min and max instances to zero during the announced registration peak
Explanation
Correct Answer
A:
Measure peak registration completion and cost per successful submission is a direct acceptance test of the path implicated by cost report shows request demand peaks 20x within minutes. It checks that the original risk (finance wants to optimize Cloud Run spending by terminating instances during exam registration) has actually been controlled and tests that permitted operations still meet the requirement that students must be able to submit registration before hard deadlines.
Incorrect Answers
B:
The alternative “Trial concurrency and min-instance changes outside peak periods” documents change execution but not its operational acceptance result. In the reported observation, cost report shows request demand peaks 20x within minutes. The option “Measure peak registration completion and cost per successful submission” instead addresses the requested acceptance verification.
C:
The alternative “Model workload demand, latency cost of cold starts and peak business value” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, cost report shows request demand peaks 20x within minutes. The option “Measure peak registration completion and cost per successful submission” instead addresses the requested acceptance verification.
D:
A blanket shutdown destroys the core business outcome. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that students must be able to submit registration before hard deadlines.
Question 93
At Public sports streaming provider, the Google Cloud design for Cloud Monitoring latency alert is affected because the team alerts on average latency while p99 playback start delays exceed 20 seconds. A review found that histogram shows rare severe stalls hidden by low median. The proposed response must account for the requirement that users need a low tail-latency start experience. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?
- Define percentile-based latency SLO and burn-rate alert policy
- Inject tail-latency stalls and confirm alert triggers without page floods
- Track p95/p99 trends, burn rate and false positives
- Alert only when average latency crosses a broad threshold
Explanation
Correct Answer
C:
Track p95/p99 trends, burn rate and false positives reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (the team alerts on average latency while p99 playback start delays exceed 20 seconds) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Define percentile-based latency SLO and burn-rate alert policy” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, histogram shows rare severe stalls hidden by low median. The option “Track p95/p99 trends, burn rate and false positives” instead addresses the requested ongoing operational assurance.
B:
The alternative “Inject tail-latency stalls and confirm alert triggers without page floods” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, histogram shows rare severe stalls hidden by low median. The option “Track p95/p99 trends, burn rate and false positives” instead addresses the requested ongoing operational assurance.
D:
An average hides a small but severely affected user cohort. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that users need a low tail-latency start experience.
Question 94
Case study: Regional farmers market network: mobile checkout modernization
Regional farmers market network relies on mobile checkout modernization to deliver its operational commitments. The current architectural problem is that the business case assumes continuous cellular service across remote event sites. The team has recorded this evidence: store surveys show multi-hour connectivity gaps at harvest festivals. Any proposed response must preserve the requirement that offline payments must reconcile without accepting unlimited duplicate orders.
The mobile checkout modernization environment at Regional farmers market network faces this issue: the business case assumes continuous cellular service across remote event sites. Supporting evidence shows that store surveys show multi-hour connectivity gaps at harvest festivals. The architect must preserve the requirement that offline payments must reconcile without accepting unlimited duplicate orders. What test must pass before the business accepts the remediated architecture?
- Run an offline purchase and reconnect cycle while checking uniqueness and ledger totals
- Enumerate offline duration, refund operations, device trust and reconciliation owners
- Pilot one market with controlled offline ledgers and an explicit failback process
- Let every device approve unlimited offline charges without identity checks
Explanation
Correct Answer
A:
Run an offline purchase and reconnect cycle while checking uniqueness and ledger totals is a direct acceptance test of the path implicated by store surveys show multi-hour connectivity gaps at harvest festivals. It checks that the original risk (the business case assumes continuous cellular service across remote event sites) has actually been controlled and tests that permitted operations still meet the requirement that offline payments must reconcile without accepting unlimited duplicate orders.
Incorrect Answers
B:
The alternative “Enumerate offline duration, refund operations, device trust and reconciliation owners” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, store surveys show multi-hour connectivity gaps at harvest festivals. The option “Run an offline purchase and reconnect cycle while checking uniqueness and ledger totals” instead addresses the requested acceptance verification.
C:
The alternative “Pilot one market with controlled offline ledgers and an explicit failback process” documents change execution but not its operational acceptance result. In the reported observation, store surveys show multi-hour connectivity gaps at harvest festivals. The option “Run an offline purchase and reconnect cycle while checking uniqueness and ledger totals” instead addresses the requested acceptance verification.
D:
Unlimited offline approvals create unbounded fraud and reconciliation exposure. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that offline payments must reconcile without accepting unlimited duplicate orders.
Question 95
Case study: Public broadcaster: live event thumbnail pipeline
Public broadcaster relies on live event thumbnail pipeline to deliver its operational commitments. The current architectural problem is that image conversion jobs scale unpredictably and operators provision fixed VMs manually. The team has recorded this evidence: daily charts show 60x spikes lasting ten minutes with idle nights. Any proposed response must preserve the requirement that uploads require isolated execution and no long-lived server state.
The live event thumbnail pipeline environment at Public broadcaster faces this issue: image conversion jobs scale unpredictably and operators provision fixed VMs manually. Supporting evidence shows that daily charts show 60x spikes lasting ten minutes with idle nights. The architect must preserve the requirement that uploads require isolated execution and no long-lived server state. Before approving a solution, which analysis most directly clarifies the underlying dependency or control gap?
- Operate a fixed single VM with no scaling or restart policy
- Select Cloud Run for stateless event-driven conversion with managed scaling
- Classify request duration, concurrency, output size and idle baseline
- Publish container revisions with gradual traffic splitting and bounded concurrency
Explanation
Correct Answer
C:
Classify request duration, concurrency, output size and idle baseline is the appropriate diagnostic because the observation—daily charts show 60x spikes lasting ten minutes with idle nights—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (image conversion jobs scale unpredictably and operators provision fixed VMs manually) before the design is approved.
Incorrect Answers
A:
A fixed VM creates capacity bottlenecks and idle cost. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that uploads require isolated execution and no long-lived server state.
B:
The alternative “Select Cloud Run for stateless event-driven conversion with managed scaling” is target architecture selection; it does not establish why the observed path failed. In the reported observation, daily charts show 60x spikes lasting ten minutes with idle nights. The option “Classify request duration, concurrency, output size and idle baseline” instead addresses the requested root-cause evidence.
D:
The alternative “Publish container revisions with gradual traffic splitting and bounded concurrency” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, daily charts show 60x spikes lasting ten minutes with idle nights. The option “Classify request duration, concurrency, output size and idle baseline” instead addresses the requested root-cause evidence.
Question 96
Consider Large airline revenue group and its service account impersonation workload. The issue is that automation assumes project Editor role is required to invoke one reporting job; the current observation is that permission audit shows callers can create keys and change unrelated resources. The team must ensure that billing reads must use auditable least privilege. The change committee needs to understand the current system rather than install a fix yet. What should it do?
- Map exact permissions and impersonation token flows
- Migrate callers to short-lived access tokens and disable downloaded keys
- Use a downloaded project Owner key for every reporting job
- Grant narrowly scoped service-account impersonation and resource-specific reader roles
Explanation
Correct Answer
A:
Map exact permissions and impersonation token flows is the appropriate diagnostic because the observation—permission audit shows callers can create keys and change unrelated resources—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (automation assumes project Editor role is required to invoke one reporting job) before the design is approved.
Incorrect Answers
B:
The alternative “Migrate callers to short-lived access tokens and disable downloaded keys” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, permission audit shows callers can create keys and change unrelated resources. The option “Map exact permissions and impersonation token flows” instead addresses the requested root-cause evidence.
C:
Overprivileged permanent keys greatly increase compromise impact. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that billing reads must use auditable least privilege.
D:
The alternative “Grant narrowly scoped service-account impersonation and resource-specific reader roles” is target architecture selection; it does not establish why the observed path failed. In the reported observation, permission audit shows callers can create keys and change unrelated resources. The option “Map exact permissions and impersonation token flows” instead addresses the requested root-cause evidence.
Question 97
The organization location constraint environment at Public transportation authority faces this issue: test projects in an overseas region unexpectedly receive personal commuter data. Supporting evidence shows that resource inventory shows unrestricted region creation in folder projects. The architect must preserve the requirement that all raw rider IDs must remain in the designated country. Which migration or rollout step best manages risk, dependencies and reversibility?
- Monitor location constraint exceptions and cross-region transfers
- Stage policy constraints for new projects then move existing assets safely
- Apply supported organization location restrictions and approved regional storage architecture
- Document a preferred region but leave cloud APIs unrestricted
Explanation
Correct Answer
B:
Stage policy constraints for new projects then move existing assets safely is a controlled means to introduce the approved architecture while meeting the requirement that all raw rider IDs must remain in the designated country. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Monitor location constraint exceptions and cross-region transfers” addresses later monitoring rather than the actual controlled deployment. In the reported observation, resource inventory shows unrestricted region creation in folder projects. The option “Stage policy constraints for new projects then move existing assets safely” instead addresses the requested controlled implementation.
C:
The alternative “Apply supported organization location restrictions and approved regional storage architecture” describes the chosen design, but not how it is introduced safely. In the reported observation, resource inventory shows unrestricted region creation in folder projects. The option “Stage policy constraints for new projects then move existing assets safely” instead addresses the requested controlled implementation.
D:
A recommendation alone does not prevent prohibited region deployments. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that all raw rider IDs must remain in the designated country.
Question 98
Neighborhood banking cooperative plans to update loan-origination approval service. Investigators found that business interviews reveal a four-hour branch outage limit and an immutable decision-history obligation, consistent with the reported problem that the planned monolith migration promises lower costs but omits the regulatory audit and branch-outage requirements. The response must satisfy the requirement that branches need approvals even when a regional WAN circuit fails. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Map branch dependencies, decision-record retention and acceptable outage duration with risk owners
- Choose the cheapest single-zone VM and discard decision events once the API responds
- Migrate one branch at a time with reconciled event replay and rollback
- Design a regional approval API with durable event logging and a tested local queue for temporary disconnection
- Track queue age, replay conflicts and branch recovery objectives
Explanation
Correct Answers
C:
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. This supplies the controlled-introduction half of the two-action package.
D:
Design a regional approval API with durable event logging and a tested local queue for temporary disconnection targets the underlying issue (the planned monolith migration promises lower costs but omits the regulatory audit and branch-outage requirements) rather than merely reporting symptoms. It also preserves the required outcome (branches need approvals even when a regional WAN circuit fails), 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 (the planned monolith migration promises lower costs but omits the regulatory audit and branch-outage requirements), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
B:
Lower initial infrastructure cost does not satisfy auditable decisions or disconnected operation. The shortcut does not supply the requested design and safe rollout for loan-origination approval service, where business interviews reveal a four-hour branch outage limit and an immutable decision-history obligation.
E:
Monitoring loan-origination approval service for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: the planned monolith migration promises lower costs but omits the regulatory audit and branch-outage requirements.
Question 99
Consider International fashion retailer and its customer loyalty relaunch workload. The issue is that a vendor proposal minimizes compute cost while ignoring peak checkout conversion; the current observation is that transaction dashboards show flash-sale load rises twelvefold for fifteen minutes. The team must ensure that checkout must keep the payment processor independent of loyalty analytics. The target architecture is approved; execution without disruption is the remaining decision. Which rollout action is best?
- Monitor checkout latency, dropped loyalty events and scaling cost per order
- Synchronous-call the loyalty model before charging every order
- Separate checkout from asynchronous loyalty scoring with elastic stateless APIs
- Stage canary traffic with queue buffering and a payment-path rollback switch
Explanation
Correct Answer
D:
Stage canary traffic with queue buffering and a payment-path rollback switch is a controlled means to introduce the approved architecture while meeting the requirement that checkout must keep the payment processor independent of loyalty analytics. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Monitor checkout latency, dropped loyalty events and scaling cost per order” addresses later monitoring rather than the actual controlled deployment. In the reported observation, transaction dashboards show flash-sale load rises twelvefold for fifteen minutes. The option “Stage canary traffic with queue buffering and a payment-path rollback switch” instead addresses the requested controlled implementation.
B:
Making payment dependent on optional scoring magnifies latency and outages. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that checkout must keep the payment processor independent of loyalty analytics.
C:
The alternative “Separate checkout from asynchronous loyalty scoring with elastic stateless APIs” describes the chosen design, but not how it is introduced safely. In the reported observation, transaction dashboards show flash-sale load rises twelvefold for fifteen minutes. The option “Stage canary traffic with queue buffering and a payment-path rollback switch” instead addresses the requested controlled implementation.
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.