Google Professional Cloud Architect Practice Test 9
Question 80
Legal case management SaaS plans to update multi-tenant object security. Investigators found that penetration test exchanges a case ID and retrieves another tenant's document, consistent with the reported problem that valid user tokens can access case files belonging to other law firms. The response must satisfy the requirement that each firm requires strict object-level isolation. Which target-state design is best justified by the evidence and required business outcome?
- Trace subject, tenant, object and data-layer authorization decisions
- Rely only on login authentication without checking case object ownership
- Apply tenant-bound object authorization enforced on every API and data query
- Monitor denied cross-tenant access and new API routes lacking ownership checks
Explanation
Correct Answer
C:
Apply tenant-bound object authorization enforced on every API and data query targets the underlying issue (valid user tokens can access case files belonging to other law firms) rather than merely reporting symptoms. It also preserves the required outcome (each firm requires strict object-level isolation), which a target-state design must satisfy.
Incorrect Answers
A:
The alternative “Trace subject, tenant, object and data-layer authorization decisions” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, penetration test exchanges a case ID and retrieves another tenant's document. The option “Apply tenant-bound object authorization enforced on every API and data query” instead addresses the requested architecture selection.
B:
Authentication cannot replace per-object authorization. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that each firm requires strict object-level isolation.
D:
The alternative “Monitor denied cross-tenant access and new API routes lacking ownership checks” measures results without defining the preventive design now required. In the reported observation, penetration test exchanges a case ID and retrieves another tenant's document. The option “Apply tenant-bound object authorization enforced on every API and data query” instead addresses the requested architecture selection.
Question 81
Case study: National airport lounge operator: managed Prometheus scraping
National airport lounge operator relies on managed Prometheus scraping to deliver its operational commitments. The current architectural problem is that several GKE services expose metrics but the monitoring system has blind spots after namespace moves. The team has recorded this evidence: scrape health shows targets disappeared when Kubernetes labels changed. Any proposed response must preserve the requirement that capacity alerts must remain tied to actual service discovery.
At National airport lounge operator, the Google Cloud design for managed Prometheus scraping is affected because several GKE services expose metrics but the monitoring system has blind spots after namespace moves. A review found that scrape health shows targets disappeared when Kubernetes labels changed. The proposed response must account for the requirement that capacity alerts must remain tied to actual service discovery. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?
- Treat all unlabeled zero metrics as healthy application inactivity
- Migrate label selectors and alert rules under observed scrape coverage
- Configure Managed Service for Prometheus collectors with stable target discovery
- Inspect Kubernetes service selectors, relabeling and scrape permissions
Explanation
Correct Answer
D:
Inspect Kubernetes service selectors, relabeling and scrape permissions is the appropriate diagnostic because the observation—scrape health shows targets disappeared when Kubernetes labels changed—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (several GKE services expose metrics but the monitoring system has blind spots after namespace moves) before the design is approved.
Incorrect Answers
A:
Missing scrape targets can look like falsely healthy zeros. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that capacity alerts must remain tied to actual service discovery.
B:
The alternative “Migrate label selectors and alert rules under observed scrape coverage” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, scrape health shows targets disappeared when Kubernetes labels changed. The option “Inspect Kubernetes service selectors, relabeling and scrape permissions” instead addresses the requested root-cause evidence.
C:
The alternative “Configure Managed Service for Prometheus collectors with stable target discovery” is target architecture selection; it does not establish why the observed path failed. In the reported observation, scrape health shows targets disappeared when Kubernetes labels changed. The option “Inspect Kubernetes service selectors, relabeling and scrape permissions” instead addresses the requested root-cause evidence.
Question 82
At Financial audit services group, the cloud organization inheritance workload has a documented risk: security administrators grant broad roles directly to each production project. The review found that audit reveals inconsistent permissions across finance subsidiaries. The architecture must also ensure that a central security team must enforce boundaries while subsidiaries run their own workloads. What follow-up metric or alert will identify emerging failures after the initial acceptance test?
- Monitor excess privileged grants, org-policy exceptions and IAM drift
- Grant Editor to every subsidiary developer on every production project
- Place business units under governed folders with group-based least privilege and org-level constraints
- Confirm a new project inherits restrictions and has only intended group access
Explanation
Correct Answer
A:
Monitor excess privileged grants, org-policy exceptions and IAM drift reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (security administrators grant broad roles directly to each production project) rather than treating the first successful test as permanent assurance.
Incorrect Answers
B:
Broad organization-wide editing violates separation and least privilege. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that a central security team must enforce boundaries while subsidiaries run their own workloads.
C:
The alternative “Place business units under governed folders with group-based least privilege and org-level constraints” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, audit reveals inconsistent permissions across finance subsidiaries. The option “Monitor excess privileged grants, org-policy exceptions and IAM drift” instead addresses the requested ongoing operational assurance.
D:
The alternative “Confirm a new project inherits restrictions and has only intended group access” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, audit reveals inconsistent permissions across finance subsidiaries. The option “Monitor excess privileged grants, org-policy exceptions and IAM drift” instead addresses the requested ongoing operational assurance.
Question 83
The speech-to-text triage environment at Medical translation nonprofit faces this issue: clinics need transcripts of spoken patient questions and multilingual summaries. Supporting evidence shows that audio samples vary in background noise and language code switching. The architect must preserve the requirement that patient data must be handled under consent and short retention. Select THREE evidence activities to cover (1) diagnosis before design, (2) direct post-change acceptance, and (3) continued operational monitoring. Which THREE fit those stages?
- Measure word error rate and translation fidelity on consented samples
- Accept the deployment ticket as proof that the control has no remaining security or availability risk
- Benchmark speech recognition error by language and noise against ground truth
- Use an image-labeling API as the only audio transcriber
- Use an appropriate speech recognition API with separate governed translation and summarization stages
- Monitor failed transcriptions, language bias and data-deletion completions
Explanation
Correct Answers
A:
Measure word error rate and translation fidelity on consented samples is a direct acceptance test of the path implicated by audio samples vary in background noise and language code switching. It checks that the original risk (clinics need transcripts of spoken patient questions and multilingual summaries) has actually been controlled and tests that permitted operations still meet the requirement that patient data must be handled under consent and short retention. It supplies the separate post-change acceptance result requested.
C:
Benchmark speech recognition error by language and noise against ground truth is the appropriate diagnostic because the observation—audio samples vary in background noise and language code switching—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (clinics need transcripts of spoken patient questions and multilingual summaries) before the design is approved. It supplies the pre-design diagnostic evidence requested.
F:
Monitor failed transcriptions, language bias and data-deletion completions reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (clinics need transcripts of spoken patient questions and multilingual summaries) rather than treating the first successful test as permanent assurance. It supplies the ongoing observation requested.
Incorrect Answers
B:
A change-record state does not measure the behavior reported by the original evidence, and cannot prove protection or availability. In particular, the observed issue was: audio samples vary in background noise and language code switching.
D:
An image classification service does not provide speech transcripts. It cannot satisfy the required evidence stages.
E:
Designing speech-to-text triage addresses the root cause, but this specific three-part question asks for evidence to diagnose, accept and continuously verify the response to clinics need transcripts of spoken patient questions and multilingual summaries, not another design proposal.
Question 84
At National tax gateway, the Google Cloud design for online filing portal is affected because project plan assumes applications can be restored faster than their external identity dependency. A review found that disaster drill finds the only token service unavailable when compute is healthy. The proposed response must account for the requirement that deadline-day filings must be accepted with accountable citizen identity. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?
- Take down identity primary and verify authorized filer recovery within SLO
- Plan independent identity recovery and replay-safe filing intake across zones
- Track token service availability, queue age and unprocessed filings
- Ignore the identity provider during resilience testing because VMs are redundant
Explanation
Correct Answer
C:
Track token service availability, queue age and unprocessed filings reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (project plan assumes applications can be restored faster than their external identity dependency) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Take down identity primary and verify authorized filer recovery within SLO” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, disaster drill finds the only token service unavailable when compute is healthy. The option “Track token service availability, queue age and unprocessed filings” instead addresses the requested ongoing operational assurance.
B:
The alternative “Plan independent identity recovery and replay-safe filing intake across zones” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, disaster drill finds the only token service unavailable when compute is healthy. The option “Track token service availability, queue age and unprocessed filings” instead addresses the requested ongoing operational assurance.
D:
Compute redundancy does not protect an unavailable authentication dependency. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that deadline-day filings must be accepted with accountable citizen identity.
Question 85
At Smart building portfolio, the Google Cloud design for telemetry collector is affected because sensor ingestion stops whenever the central analytics service is deployed. A review found that test telemetry shows HTTP sensors retry until devices run out of buffer. The proposed response must account for the requirement that devices must keep accepting samples through brief backend maintenance. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?
- Migrate sensor groups with schema validation and idempotent delivery
- Decouple device ingestion through durable messaging and independently scaling consumers
- Block sensor writes during every analytics rollout
- Quantify message rate, outage buffer and duplicate-retention behavior
Explanation
Correct Answer
D:
Quantify message rate, outage buffer and duplicate-retention behavior is the appropriate diagnostic because the observation—test telemetry shows HTTP sensors retry until devices run out of buffer—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (sensor ingestion stops whenever the central analytics service is deployed) before the design is approved.
Incorrect Answers
A:
The alternative “Migrate sensor groups with schema validation and idempotent delivery” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, test telemetry shows HTTP sensors retry until devices run out of buffer. The option “Quantify message rate, outage buffer and duplicate-retention behavior” instead addresses the requested root-cause evidence.
B:
The alternative “Decouple device ingestion through durable messaging and independently scaling consumers” is target architecture selection; it does not establish why the observed path failed. In the reported observation, test telemetry shows HTTP sensors retry until devices run out of buffer. The option “Quantify message rate, outage buffer and duplicate-retention behavior” instead addresses the requested root-cause evidence.
C:
Tight coupling discards data when a downstream service pauses. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that devices must keep accepting samples through brief backend maintenance.
Question 86
City library data portal plans to update accessibility acceptance. Investigators found that accessibility audit finds focus cannot reach essential search fields, consistent with the reported problem that a redesigned public portal uses keyboard-inaccessible chart filters. The response must satisfy the requirement that government content must be accessible to assistive technology users. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?
- Include accessible components and automated/manual quality criteria in release requirements
- Approve launch solely because automated unit tests passed
- Review key workflows, keyboard navigation and applicable accessibility criteria
- Release fixes behind user-testing feedback and rollback
Explanation
Correct Answer
C:
Review key workflows, keyboard navigation and applicable accessibility criteria is the appropriate diagnostic because the observation—accessibility audit finds focus cannot reach essential search fields—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (a redesigned public portal uses keyboard-inaccessible chart filters) before the design is approved.
Incorrect Answers
A:
The alternative “Include accessible components and automated/manual quality criteria in release requirements” is target architecture selection; it does not establish why the observed path failed. In the reported observation, accessibility audit finds focus cannot reach essential search fields. The option “Review key workflows, keyboard navigation and applicable accessibility criteria” instead addresses the requested root-cause evidence.
B:
Unit tests do not capture all interactive accessibility barriers. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that government content must be accessible to assistive technology users.
D:
The alternative “Release fixes behind user-testing feedback and rollback” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, accessibility audit finds focus cannot reach essential search fields. The option “Review key workflows, keyboard navigation and applicable accessibility criteria” instead addresses the requested root-cause evidence.
Question 87
At Urban public transport authority, the fare validation backend workload has a documented risk: rush-hour taps overwhelm the settlement database even though fraud checks are light. The review found that histogram shows 8x peak events and lock waits on identical card records. The architecture must also ensure that a transit pass must not be charged twice for one tap. What follow-up metric or alert will identify emerging failures after the initial acceptance test?
- Scale only the front-end web server while keeping the hot database lock
- Buffer taps durably and enforce idempotent settlement with per-pass consistency
- Monitor pending tap age, settlement retries and contention
- Replay duplicated rush-hour tap IDs and reconcile exactly one charge per event
Explanation
Correct Answer
C:
Monitor pending tap age, settlement retries and contention reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (rush-hour taps overwhelm the settlement database even though fraud checks are light) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
A larger front end does not remove the transactional bottleneck. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that a transit pass must not be charged twice for one tap.
B:
The alternative “Buffer taps durably and enforce idempotent settlement with per-pass consistency” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, histogram shows 8x peak events and lock waits on identical card records. The option “Monitor pending tap age, settlement retries and contention” instead addresses the requested ongoing operational assurance.
D:
The alternative “Replay duplicated rush-hour tap IDs and reconcile exactly one charge per event” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, histogram shows 8x peak events and lock waits on identical card records. The option “Monitor pending tap age, settlement retries and contention” instead addresses the requested ongoing operational assurance.
Question 88
Case study: International bank holding company: regulated data-center extension
International bank holding company relies on regulated data-center extension to deliver its operational commitments. The current architectural problem is that the proposed Dedicated Interconnect lacks a backup location and depends on a single metro facility. The team has recorded this evidence: site survey lists one colocation provider and a common power feed for both links. Any proposed response must preserve the requirement that settlement services require redundant connectivity with predictable private latency.
The regulated data-center extension environment at International bank holding company faces this issue: the proposed Dedicated Interconnect lacks a backup location and depends on a single metro facility. Supporting evidence shows that site survey lists one colocation provider and a common power feed for both links. The architect must preserve the requirement that settlement services require redundant connectivity with predictable private latency. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Design geographically separated Interconnect circuits with independent BGP sessions and failover
- Track circuit utilization, BGP flaps and SLA breaches
- Disconnect a whole metro edge and verify private settlement connectivity persists
- Install two ports in the same rack and call them regionally redundant
Explanation
Correct Answer
B:
Track circuit utilization, BGP flaps and SLA breaches reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (the proposed Dedicated Interconnect lacks a backup location and depends on a single metro facility) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Design geographically separated Interconnect circuits with independent BGP sessions and failover” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, site survey lists one colocation provider and a common power feed for both links. The option “Track circuit utilization, BGP flaps and SLA breaches” instead addresses the requested ongoing operational assurance.
C:
The alternative “Disconnect a whole metro edge and verify private settlement connectivity persists” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, site survey lists one colocation provider and a common power feed for both links. The option “Track circuit utilization, BGP flaps and SLA breaches” instead addresses the requested ongoing operational assurance.
D:
Common power and facility dependencies defeat geographic resilience. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that settlement services require redundant connectivity with predictable private latency.
Question 89
The support dependency escalation environment at Public archive network faces this issue: staff cannot resolve sporadic object read failures because the case lacks request IDs. Supporting evidence shows that support replies repeatedly ask for missing bucket and operation context. The architect must preserve the requirement that public document retrieval must be restored quickly without exposing personal data. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Define support runbooks with minimal reproducible evidence and safe redaction
- Send complete private object contents and unrestricted credentials in a support email
- Reproduce failures with sanitized requests and confirm the right support evidence is collected
- Track repeated evidence gaps and delayed support resolution
Explanation
Correct Answer
D:
Track repeated evidence gaps and delayed support resolution reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (staff cannot resolve sporadic object read failures because the case lacks request IDs) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Define support runbooks with minimal reproducible evidence and safe redaction” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, support replies repeatedly ask for missing bucket and operation context. The option “Track repeated evidence gaps and delayed support resolution” instead addresses the requested ongoing operational assurance.
B:
Support evidence should be sufficient and minimized, not a credential leak. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that public document retrieval must be restored quickly without exposing personal data.
C:
The alternative “Reproduce failures with sanitized requests and confirm the right support evidence is collected” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, support replies repeatedly ask for missing bucket and operation context. The option “Track repeated evidence gaps and delayed support resolution” instead addresses the requested ongoing operational assurance.
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.