Google Professional Cloud Architect Practice Test 76
Question 750
At National digital identification office, the Google Cloud design for external identity service onboarding is affected because a public API rollout lacks per-agency token audience enforcement. A review found that test shows an agency credential can call unrelated record endpoints. The proposed response must account for the requirement that agency access must be least privilege and auditable. Which controlled implementation should be used to preserve operational continuity during the change?
- Allow any signed token from any agency to read all records
- Track token audience drift and unauthorized API attempts
- Use audience-scoped tokens and appropriate API authorization checks
- Onboard agencies incrementally with policy tests and request logs
Explanation
Correct Answer
D:
Onboard agencies incrementally with policy tests and request logs is a controlled means to introduce the approved architecture while meeting the requirement that agency access must be least privilege and auditable. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
Signature validity does not grant access to unrelated applications. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that agency access must be least privilege and auditable.
B:
The alternative “Track token audience drift and unauthorized API attempts” addresses later monitoring rather than the actual controlled deployment. In the reported observation, test shows an agency credential can call unrelated record endpoints. The option “Onboard agencies incrementally with policy tests and request logs” instead addresses the requested controlled implementation.
C:
The alternative “Use audience-scoped tokens and appropriate API authorization checks” describes the chosen design, but not how it is introduced safely. In the reported observation, test shows an agency credential can call unrelated record endpoints. The option “Onboard agencies incrementally with policy tests and request logs” instead addresses the requested controlled implementation.
Question 751
The edge-device digital twin environment at Industrial robotics startup faces this issue: architects assume GPU inference remains constant even though future robots gain local accelerators. Supporting evidence shows that hardware roadmap shows some plants will run most inference at the edge. The architect must preserve the requirement that plant safety systems must not depend on public network availability. Choose the architecture that resolves the documented weakness without breaching the operational constraint.
- Design split edge/cloud inference with versioned model contracts and offline safety path
- Force all safety-critical inference through a distant cloud endpoint
- Track unsupported hardware, model rollout lag and cloud inference spend
- Forecast edge capability, model footprints and remote update channels
Explanation
Correct Answer
A:
Design split edge/cloud inference with versioned model contracts and offline safety path targets the underlying issue (architects assume GPU inference remains constant even though future robots gain local accelerators) rather than merely reporting symptoms. It also preserves the required outcome (plant safety systems must not depend on public network availability), which a target-state design must satisfy.
Incorrect Answers
B:
WAN outages would compromise real-time plant operation. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that plant safety systems must not depend on public network availability.
C:
The alternative “Track unsupported hardware, model rollout lag and cloud inference spend” measures results without defining the preventive design now required. In the reported observation, hardware roadmap shows some plants will run most inference at the edge. The option “Design split edge/cloud inference with versioned model contracts and offline safety path” instead addresses the requested architecture selection.
D:
The alternative “Forecast edge capability, model footprints and remote update channels” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, hardware roadmap shows some plants will run most inference at the edge. The option “Design split edge/cloud inference with versioned model contracts and offline safety path” instead addresses the requested architecture selection.
Question 752
At Biopharma laboratory, the internal research dashboards workload has a documented risk: analysts need petabyte SQL aggregation but a transactional app database is overloaded. The review found that workload trace shows long scans that lock operational assay tables. The architecture must also ensure that regulated sample updates cannot be blocked by ad hoc reporting. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Differentiate OLTP writes, query concurrency and analytics freshness
- Point every BI user at the operational database with unrestricted full-table scans
- Watch slots, partition pruning and data-freshness SLO
- Schedule partitioned incremental extraction and dataset-level controls
- Load analytical datasets into BigQuery while preserving transactional source
Explanation
Correct Answers
D:
Schedule partitioned incremental extraction and dataset-level controls is a controlled means to introduce the approved architecture while meeting the requirement that regulated sample updates cannot be blocked by ad hoc reporting. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption. This supplies the controlled-introduction half of the two-action package.
E:
Load analytical datasets into BigQuery while preserving transactional source targets the underlying issue (analysts need petabyte SQL aggregation but a transactional app database is overloaded) rather than merely reporting symptoms. It also preserves the required outcome (regulated sample updates cannot be blocked by ad hoc reporting), 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 (analysts need petabyte SQL aggregation but a transactional app database is overloaded), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
B:
Unbounded analytics queries undermine transactional service. The shortcut does not supply the requested design and safe rollout for internal research dashboards, where workload trace shows long scans that lock operational assay tables.
C:
Monitoring internal research dashboards for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: analysts need petabyte SQL aggregation but a transactional app database is overloaded.
Question 753
The automated rollback thresholds environment at International insurance portal faces this issue: new revision doubles checkout error rate but rollout continues because logs are not tied to release gates. Supporting evidence shows that service dashboard shows 6% failure during a 20% canary. The architect must preserve the requirement that customer billing changes must be reversible without inconsistent transactions. Which migration or rollout step best manages risk, dependencies and reversibility?
- Track failed rollback events and release-specific SLO deltas
- Treat release success as the number of pods that became Ready
- Deploy gradual traffic with automated abort thresholds
- Define canary gates for error, latency and transaction integrity
Explanation
Correct Answer
C:
Deploy gradual traffic with automated abort thresholds is a controlled means to introduce the approved architecture while meeting the requirement that customer billing changes must be reversible without inconsistent transactions. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Track failed rollback events and release-specific SLO deltas” addresses later monitoring rather than the actual controlled deployment. In the reported observation, service dashboard shows 6% failure during a 20% canary. The option “Deploy gradual traffic with automated abort thresholds” instead addresses the requested controlled implementation.
B:
Readiness alone does not demonstrate correct customer transactions. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that customer billing changes must be reversible without inconsistent transactions.
D:
The alternative “Define canary gates for error, latency and transaction integrity” describes the chosen design, but not how it is introduced safely. In the reported observation, service dashboard shows 6% failure during a 20% canary. The option “Deploy gradual traffic with automated abort thresholds” instead addresses the requested controlled implementation.
Question 754
National tax gateway plans to update online filing portal. Investigators found that disaster drill finds the only token service unavailable when compute is healthy, consistent with the reported problem that project plan assumes applications can be restored faster than their external identity dependency. The response must satisfy the requirement that deadline-day filings must be accepted with accountable citizen identity. The design review is over and production introduction is next. Which action is the best fit?
- Track token service availability, queue age and unprocessed filings
- Stage identity failover with signed-session revocation and audit retention
- Plan independent identity recovery and replay-safe filing intake across zones
- Ignore the identity provider during resilience testing because VMs are redundant
Explanation
Correct Answer
B:
Stage identity failover with signed-session revocation and audit retention is a controlled means to introduce the approved architecture while meeting the requirement that deadline-day filings must be accepted with accountable citizen identity. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Track token service availability, queue age and unprocessed filings” addresses later monitoring rather than the actual controlled deployment. In the reported observation, disaster drill finds the only token service unavailable when compute is healthy. The option “Stage identity failover with signed-session revocation and audit retention” instead addresses the requested controlled implementation.
C:
The alternative “Plan independent identity recovery and replay-safe filing intake across zones” describes the chosen design, but not how it is introduced safely. In the reported observation, disaster drill finds the only token service unavailable when compute is healthy. The option “Stage identity failover with signed-session revocation and audit retention” instead addresses the requested controlled implementation.
D:
Compute redundancy does not protect an unavailable authentication dependency. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that deadline-day filings must be accepted with accountable citizen identity.
Question 755
Case study: National airport regulator: programmatic audit exports
National airport regulator relies on programmatic audit exports to deliver its operational commitments. The current architectural problem is that a Python client uses user ADC with project Owner and downloads more logs than needed. The team has recorded this evidence: code review finds broad filterless audit queries. Any proposed response must preserve the requirement that regulator requires a bounded report for one certified airport.
Consider National airport regulator and its programmatic audit exports workload. The issue is that a Python client uses user ADC with project Owner and downloads more logs than needed; the current observation is that code review finds broad filterless audit queries. The team must ensure that regulator requires a bounded report for one certified airport. Which continuous monitoring approach best reveals recurrence or changing dependencies?
- Reconcile exported timestamps and counts against source query
- Use scoped service identity and paginated filtered API requests
- Run unfiltered organization-wide log downloads with superadmin credentials
- Monitor access scope changes and missing export windows
Explanation
Correct Answer
D:
Monitor access scope changes and missing export windows reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a Python client uses user ADC with project Owner and downloads more logs than needed) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Reconcile exported timestamps and counts against source query” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, code review finds broad filterless audit queries. The option “Monitor access scope changes and missing export windows” instead addresses the requested ongoing operational assurance.
B:
The alternative “Use scoped service identity and paginated filtered API requests” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, code review finds broad filterless audit queries. The option “Monitor access scope changes and missing export windows” instead addresses the requested ongoing operational assurance.
C:
Overbroad access and exports exceed the audit's authorized scope. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that regulator requires a bounded report for one certified airport.
Question 756
The admin console access environment at National land registry faces this issue: staff directly expose internal admin dashboards through public VM IPs. Supporting evidence shows that network scan discovers admin endpoints reachable without identity-aware gateway. The architect must preserve the requirement that authorized clerks must access remotely without public administrative ingress. Choose the architecture that resolves the documented weakness without breaching the operational constraint.
- Monitor IAP access failures and unexpected direct ingress rules
- Add a public allow-all firewall rule with obscured URL paths
- Inspect admin application authentication, network paths and role needs
- Put supported admin applications behind Identity-Aware Proxy with appropriate IAM
Explanation
Correct Answer
D:
Put supported admin applications behind Identity-Aware Proxy with appropriate IAM targets the underlying issue (staff directly expose internal admin dashboards through public VM IPs) rather than merely reporting symptoms. It also preserves the required outcome (authorized clerks must access remotely without public administrative ingress), which a target-state design must satisfy.
Incorrect Answers
A:
The alternative “Monitor IAP access failures and unexpected direct ingress rules” measures results without defining the preventive design now required. In the reported observation, network scan discovers admin endpoints reachable without identity-aware gateway. The option “Put supported admin applications behind Identity-Aware Proxy with appropriate IAM” instead addresses the requested architecture selection.
B:
Obscure paths do not restrict authenticated administrative access. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that authorized clerks must access remotely without public administrative ingress.
C:
The alternative “Inspect admin application authentication, network paths and role needs” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, network scan discovers admin endpoints reachable without identity-aware gateway. The option “Put supported admin applications behind Identity-Aware Proxy with appropriate IAM” instead addresses the requested architecture selection.
Question 757
Case study: Insurance document platform: external customer authentication
Insurance document platform relies on external customer authentication to deliver its operational commitments. The current architectural problem is that a business partner requests privileged access using only a static shared API key. The team has recorded this evidence: request log shows the same key used from several external offices. Any proposed response must preserve the requirement that partner access must identify the calling workload and enforce scopes.
Consider Insurance document platform and its external customer authentication workload. The issue is that a business partner requests privileged access using only a static shared API key; the current observation is that request log shows the same key used from several external offices. The team must ensure that partner access must identify the calling workload and enforce scopes. The target architecture is approved; execution without disruption is the remaining decision. Which rollout action is best?
- Expand the shared API key to every document endpoint for convenience
- Adopt federated workload identity and scoped authorization with token expiry
- Onboard partner issuers with trust conditions and retire the static key
- Monitor issuer trust changes and anomalous token audience values
Explanation
Correct Answer
C:
Onboard partner issuers with trust conditions and retire the static key is a controlled means to introduce the approved architecture while meeting the requirement that partner access must identify the calling workload and enforce scopes. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
Shared keys cannot represent least-privilege workload identity. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that partner access must identify the calling workload and enforce scopes.
B:
The alternative “Adopt federated workload identity and scoped authorization with token expiry” describes the chosen design, but not how it is introduced safely. In the reported observation, request log shows the same key used from several external offices. The option “Onboard partner issuers with trust conditions and retire the static key” instead addresses the requested controlled implementation.
D:
The alternative “Monitor issuer trust changes and anomalous token audience values” addresses later monitoring rather than the actual controlled deployment. In the reported observation, request log shows the same key used from several external offices. The option “Onboard partner issuers with trust conditions and retire the static key” instead addresses the requested controlled implementation.
Question 758
International health insurer plans to update Cloud Build release flow. Investigators found that release logs show no artifact promotion or security scan before a production deploy, consistent with the reported problem that a deployment pipeline places unreviewed images into production after every commit. The response must satisfy the requirement that production releases require signed approval and a reversible rollout. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Stage signed artifact promotion with progressive traffic rollout
- Map build triggers, artifact hashes, approval owners and deployment paths
- Allow every developer to deploy from a mutable local image tag
- Monitor skipped gates, broken builds and rollout error budgets
- Design gated CI/CD with immutable artifacts, tests, policy checks and deploy approvals
Explanation
Correct Answers
A:
Stage signed artifact promotion with progressive traffic rollout is a controlled means to introduce the approved architecture while meeting the requirement that production releases require signed approval and a reversible rollout. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption. This supplies the controlled-introduction half of the two-action package.
E:
Design gated CI/CD with immutable artifacts, tests, policy checks and deploy approvals targets the underlying issue (a deployment pipeline places unreviewed images into production after every commit) rather than merely reporting symptoms. It also preserves the required outcome (production releases require signed approval and a reversible rollout), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
Incorrect Answers
B:
This diagnoses the original issue (a deployment pipeline places unreviewed images into production after every commit), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
C:
Mutable unreviewed releases cannot provide attributable production control. The shortcut does not supply the requested design and safe rollout for Cloud Build release flow, where release logs show no artifact promotion or security scan before a production deploy.
D:
Monitoring Cloud Build release flow for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: a deployment pipeline places unreviewed images into production after every commit.
Question 759
At International game publisher, the multiplayer leaderboard workload has a documented risk: the team needs globally consistent top-rank writes but each region has independent SQL databases. The review found that traces show duplicate rank commits during cross-region failover. The architecture must also ensure that player rewards require globally serialized authoritative outcomes. The team must deliver the approved control safely. Which deployment sequence is most appropriate?
- Use independent last-writer-wins Redis counters as the financial reward ledger
- Track commit latency, aborted transaction retries and region failover
- Choose globally consistent Spanner transactions for authoritative ranking records
- Migrate selected leaderboard partitions with dual reconciliation
Explanation
Correct Answer
D:
Migrate selected leaderboard partitions with dual reconciliation is a controlled means to introduce the approved architecture while meeting the requirement that player rewards require globally serialized authoritative outcomes. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
Conflict resolution by overwrite can duplicate or lose reward decisions. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that player rewards require globally serialized authoritative outcomes.
B:
The alternative “Track commit latency, aborted transaction retries and region failover” addresses later monitoring rather than the actual controlled deployment. In the reported observation, traces show duplicate rank commits during cross-region failover. The option “Migrate selected leaderboard partitions with dual reconciliation” instead addresses the requested controlled implementation.
C:
The alternative “Choose globally consistent Spanner transactions for authoritative ranking records” describes the chosen design, but not how it is introduced safely. In the reported observation, traces show duplicate rank commits during cross-region failover. The option “Migrate selected leaderboard partitions with dual reconciliation” instead addresses the requested controlled implementation.
Question 760
At Metropolitan power utility, the SCADA historian migration workload has a documented risk: historian collectors send proprietary UDP and engineers propose direct internet exposure. The review found that packet survey shows embedded devices without TLS or authentication. The architecture must also ensure that plant control networks must remain isolated from public ingress. What enduring Google Cloud design should the team choose now that the failure mode is understood?
- Track DMZ policy deviations and telemetry gaps
- Identify collectors, untrusted protocols, firewall dependencies and vendor constraints
- Give cloud VMs public routes into the SCADA control VLAN
- Design a controlled telemetry bridge through an industrial DMZ to cloud storage
Explanation
Correct Answer
D:
Design a controlled telemetry bridge through an industrial DMZ to cloud storage targets the underlying issue (historian collectors send proprietary UDP and engineers propose direct internet exposure) rather than merely reporting symptoms. It also preserves the required outcome (plant control networks must remain isolated from public ingress), which a target-state design must satisfy.
Incorrect Answers
A:
The alternative “Track DMZ policy deviations and telemetry gaps” measures results without defining the preventive design now required. In the reported observation, packet survey shows embedded devices without TLS or authentication. The option “Design a controlled telemetry bridge through an industrial DMZ to cloud storage” instead addresses the requested architecture selection.
B:
The alternative “Identify collectors, untrusted protocols, firewall dependencies and vendor constraints” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, packet survey shows embedded devices without TLS or authentication. The option “Design a controlled telemetry bridge through an industrial DMZ to cloud storage” instead addresses the requested architecture selection.
C:
Direct internet access violates industrial segmentation. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that plant control networks must remain isolated from public ingress.