Google Professional Cloud Architect Practice Test 80
Question 790
Consider City library data portal and its accessibility acceptance workload. The issue is that a redesigned public portal uses keyboard-inaccessible chart filters; the current observation is that accessibility audit finds focus cannot reach essential search fields. The team must ensure that government content must be accessible to assistive technology users. The team has completed discovery. Which preventive or corrective architecture is most appropriate?
- Approve launch solely because automated unit tests passed
- Track accessibility regressions and user support reports
- Include accessible components and automated/manual quality criteria in release requirements
- Review key workflows, keyboard navigation and applicable accessibility criteria
Explanation
Correct Answer
C:
Include accessible components and automated/manual quality criteria in release requirements targets the underlying issue (a redesigned public portal uses keyboard-inaccessible chart filters) rather than merely reporting symptoms. It also preserves the required outcome (government content must be accessible to assistive technology users), which a target-state design must satisfy.
Incorrect Answers
A:
Unit tests do not capture all interactive accessibility barriers. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that government content must be accessible to assistive technology users.
B:
The alternative “Track accessibility regressions and user support reports” measures results without defining the preventive design now required. In the reported observation, accessibility audit finds focus cannot reach essential search fields. The option “Include accessible components and automated/manual quality criteria in release requirements” instead addresses the requested architecture selection.
D:
The alternative “Review key workflows, keyboard navigation and applicable accessibility criteria” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, accessibility audit finds focus cannot reach essential search fields. The option “Include accessible components and automated/manual quality criteria in release requirements” instead addresses the requested architecture selection.
Question 791
Case study: Medical imaging supplier: patient identifier transformation
Medical imaging supplier relies on patient identifier transformation to deliver its operational commitments. The current architectural problem is that the data warehouse stores masked fields but shared exports retain direct identifiers. The team has recorded this evidence: sampling shows patient names survive in analytical free-text notes. Any proposed response must preserve the requirement that only approved care providers may see reidentifiable data.
The patient identifier transformation environment at Medical imaging supplier faces this issue: the data warehouse stores masked fields but shared exports retain direct identifiers. Supporting evidence shows that sampling shows patient names survive in analytical free-text notes. The architect must preserve the requirement that only approved care providers may see reidentifiable data. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Stage transformations and validate clinical utility before enabling broad analytics
- Track newly identified PII patterns and masking policy exceptions
- Use Sensitive Data Protection and governed deidentification with appropriate keys
- Inspect free-text PII, transformations, ownership and access conditions
- Simply rename a column from patient_name to alias
Explanation
Correct Answers
A:
Stage transformations and validate clinical utility before enabling broad analytics is a controlled means to introduce the approved architecture while meeting the requirement that only approved care providers may see reidentifiable data. 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:
Use Sensitive Data Protection and governed deidentification with appropriate keys targets the underlying issue (the data warehouse stores masked fields but shared exports retain direct identifiers) rather than merely reporting symptoms. It also preserves the required outcome (only approved care providers may see reidentifiable data), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
Incorrect Answers
B:
Monitoring patient identifier transformation for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: the data warehouse stores masked fields but shared exports retain direct identifiers.
D:
This diagnoses the original issue (the data warehouse stores masked fields but shared exports retain direct identifiers), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
E:
Renaming does not remove personal identifiers. The shortcut does not supply the requested design and safe rollout for patient identifier transformation, where sampling shows patient names survive in analytical free-text notes.
Question 792
At Regional university consortium, the Google Cloud design for research compute funding is affected because department costs are assigned equally although GPU workloads dominate reserved capacity. A review found that billing exports show two laboratories use most training accelerator hours. The proposed response must account for the requirement that sensitive lab datasets cannot be exposed through a central chargeback dashboard. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?
- Quantify per-lab machine consumption, shared overhead and privacy restrictions
- Introduce project labeling and budgets before moving accelerator jobs
- Publish raw dataset labels and individual researcher usage to all departments
- Design labeled projects and aggregated cost allocation with workload-specific budgets
Explanation
Correct Answer
A:
Quantify per-lab machine consumption, shared overhead and privacy restrictions is the appropriate diagnostic because the observation—billing exports show two laboratories use most training accelerator hours—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (department costs are assigned equally although GPU workloads dominate reserved capacity) before the design is approved.
Incorrect Answers
B:
The alternative “Introduce project labeling and budgets before moving accelerator jobs” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, billing exports show two laboratories use most training accelerator hours. The option “Quantify per-lab machine consumption, shared overhead and privacy restrictions” instead addresses the requested root-cause evidence.
C:
Overbroad chargeback visibility can reveal sensitive research details. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that sensitive lab datasets cannot be exposed through a central chargeback dashboard.
D:
The alternative “Design labeled projects and aggregated cost allocation with workload-specific budgets” is target architecture selection; it does not establish why the observed path failed. In the reported observation, billing exports show two laboratories use most training accelerator hours. The option “Quantify per-lab machine consumption, shared overhead and privacy restrictions” instead addresses the requested root-cause evidence.
Question 793
At International renewable grid data service, the Google Cloud design for penetration-test remediation is affected because last penetration test found an IDOR flaw but the team marked it fixed after updating documentation. A review found that retest finds cross-tenant API access still possible with valid token. The proposed response must account for the requirement that commercial clients require strict account isolation. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?
- Use object-level auth enforcement with independent negative-case tests
- Close the security finding based only on a signed policy memo
- Monitor new unauthorized access attempts and API route drift
- Repeat the original cross-tenant exploit test and confirm denial
Explanation
Correct Answer
C:
Monitor new unauthorized access attempts and API route drift reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (last penetration test found an IDOR flaw but the team marked it fixed after updating documentation) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Use object-level auth enforcement with independent negative-case tests” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, retest finds cross-tenant API access still possible with valid token. The option “Monitor new unauthorized access attempts and API route drift” instead addresses the requested ongoing operational assurance.
B:
Documentation cannot replace verified access-control enforcement. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that commercial clients require strict account isolation.
D:
The alternative “Repeat the original cross-tenant exploit test and confirm denial” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, retest finds cross-tenant API access still possible with valid token. The option “Monitor new unauthorized access attempts and API route drift” instead addresses the requested ongoing operational assurance.
Question 794
Case study: National pharmacy network: central NAT egress
National pharmacy network relies on central NAT egress to deliver its operational commitments. The current architectural problem is that a vendor allowlist changes every time cloud VMs autoscale with ephemeral external IPs. The team has recorded this evidence: packet trace shows outbound API requests use different VM public addresses. Any proposed response must preserve the requirement that drug inventory partner permits only named stable source addresses.
The central NAT egress environment at National pharmacy network faces this issue: a vendor allowlist changes every time cloud VMs autoscale with ephemeral external IPs. Supporting evidence shows that packet trace shows outbound API requests use different VM public addresses. The architect must preserve the requirement that drug inventory partner permits only named stable source addresses. Which migration or rollout step best manages risk, dependencies and reversibility?
- Use Cloud NAT with reserved egress IP addresses for private-subnet instances
- Assign a new public IP to every ephemeral VM and email the vendor daily
- Monitor NAT port exhaustion and permitted destination failures
- Migrate VMs to private instances and update partner allowlists before cutover
Explanation
Correct Answer
D:
Migrate VMs to private instances and update partner allowlists before cutover is a controlled means to introduce the approved architecture while meeting the requirement that drug inventory partner permits only named stable source addresses. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Use Cloud NAT with reserved egress IP addresses for private-subnet instances” describes the chosen design, but not how it is introduced safely. In the reported observation, packet trace shows outbound API requests use different VM public addresses. The option “Migrate VMs to private instances and update partner allowlists before cutover” instead addresses the requested controlled implementation.
B:
Changing per-instance IPs cannot maintain a stable partner allowlist. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that drug inventory partner permits only named stable source addresses.
C:
The alternative “Monitor NAT port exhaustion and permitted destination failures” addresses later monitoring rather than the actual controlled deployment. In the reported observation, packet trace shows outbound API requests use different VM public addresses. The option “Migrate VMs to private instances and update partner allowlists before cutover” instead addresses the requested controlled implementation.
Question 795
At Education analytics cooperative, the Google Cloud design for data pipeline incident triage is affected because daily analytics job silently drops events with previously unseen nullable fields. A review found that Dataflow error logs show schema deserialization failures after partner update. The proposed response must account for the requirement that approved learning dashboards require source-to-target reconciliation. Which analysis will allow the architect to distinguish the reported symptom from the actual failure path?
- Discard all unrecognized events without alerting
- Compare payload schema versions, dead-letter events and parsing code
- Define versioned schemas with controlled evolution and quarantined invalid events
- Deploy tolerant parsers in staged pipelines with recovery of quarantined records
Explanation
Correct Answer
B:
Compare payload schema versions, dead-letter events and parsing code is the appropriate diagnostic because the observation—Dataflow error logs show schema deserialization failures after partner update—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (daily analytics job silently drops events with previously unseen nullable fields) before the design is approved.
Incorrect Answers
A:
Silent discards create false analytics that appear complete. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that approved learning dashboards require source-to-target reconciliation.
C:
The alternative “Define versioned schemas with controlled evolution and quarantined invalid events” is target architecture selection; it does not establish why the observed path failed. In the reported observation, Dataflow error logs show schema deserialization failures after partner update. The option “Compare payload schema versions, dead-letter events and parsing code” instead addresses the requested root-cause evidence.
D:
The alternative “Deploy tolerant parsers in staged pipelines with recovery of quarantined records” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, Dataflow error logs show schema deserialization failures after partner update. The option “Compare payload schema versions, dead-letter events and parsing code” instead addresses the requested root-cause evidence.
Question 796
National retail pharmacy plans to update support ownership between vendors. Investigators found that traces show all application calls blocked on an external vendor timeout, consistent with the reported problem that a Cloud Run API fails because a third-party payment gateway responds too slowly. The response must satisfy the requirement that pharmacy payments require a documented fallback and escalation plan. The team needs an operations signal rather than another design or one-time test. What should it track?
- Keep every request waiting indefinitely for vendor recovery
- Simulate vendor slowness and confirm approved fallback works
- Monitor vendor timeouts and unresolved escalation tickets
- Define circuit breakers, vendor escalation and timeout error handling
Explanation
Correct Answer
C:
Monitor vendor timeouts and unresolved escalation tickets reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a Cloud Run API fails because a third-party payment gateway responds too slowly) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
Unbounded waits exhaust local resources and disrupt all customers. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that pharmacy payments require a documented fallback and escalation plan.
B:
The alternative “Simulate vendor slowness and confirm approved fallback works” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, traces show all application calls blocked on an external vendor timeout. The option “Monitor vendor timeouts and unresolved escalation tickets” instead addresses the requested ongoing operational assurance.
D:
The alternative “Define circuit breakers, vendor escalation and timeout error handling” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, traces show all application calls blocked on an external vendor timeout. The option “Monitor vendor timeouts and unresolved escalation tickets” instead addresses the requested ongoing operational assurance.
Question 797
At Legal discovery cooperative, the Google Cloud design for regulated document holds is affected because a scheduled lifecycle deletion overlaps a court-ordered legal hold. A review found that records show retention rules expire before litigation review completes. The proposed response must account for the requirement that legal-hold protected files must not be removed by application writers. A deployment ticket has been closed. What direct evidence would justify solution signoff?
- Attempt test deletion with ordinary application credentials and confirm refusal
- Grant all document uploaders permission to release legal holds
- Move affected prefixes into hold-governed storage under documented owner approval
- Inspect retention settings, hold authority and lifecycle job behavior
Explanation
Correct Answer
A:
Attempt test deletion with ordinary application credentials and confirm refusal is a direct acceptance test of the path implicated by records show retention rules expire before litigation review completes. It checks that the original risk (a scheduled lifecycle deletion overlaps a court-ordered legal hold) has actually been controlled and tests that permitted operations still meet the requirement that legal-hold protected files must not be removed by application writers.
Incorrect Answers
B:
Uncontrolled release rights defeat binding preservation orders. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that legal-hold protected files must not be removed by application writers.
C:
The alternative “Move affected prefixes into hold-governed storage under documented owner approval” documents change execution but not its operational acceptance result. In the reported observation, records show retention rules expire before litigation review completes. The option “Attempt test deletion with ordinary application credentials and confirm refusal” instead addresses the requested acceptance verification.
D:
The alternative “Inspect retention settings, hold authority and lifecycle job behavior” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, records show retention rules expire before litigation review completes. The option “Attempt test deletion with ordinary application credentials and confirm refusal” instead addresses the requested acceptance verification.
Question 798
Consider Vehicle warranty analytics company and its Windows compatibility hosting workload. The issue is that a proprietary claims executable needs Windows COM objects not supported in Linux containers; the current observation is that vendor test fails on Linux libraries despite unchanged program behavior. The team must ensure that temporary hosting must keep vendor support and monthly patch controls. The team has completed discovery. Which preventive or corrective architecture is most appropriate?
- Track Windows image age, license use and support deadlines
- Repackage the unchanged Windows binary into an Alpine Linux container
- Inventory licensing, runtime dependencies and supported OS baseline
- Choose Compute Engine Windows instances for an interim supported host
Explanation
Correct Answer
D:
Choose Compute Engine Windows instances for an interim supported host targets the underlying issue (a proprietary claims executable needs Windows COM objects not supported in Linux containers) rather than merely reporting symptoms. It also preserves the required outcome (temporary hosting must keep vendor support and monthly patch controls), which a target-state design must satisfy.
Incorrect Answers
A:
The alternative “Track Windows image age, license use and support deadlines” measures results without defining the preventive design now required. In the reported observation, vendor test fails on Linux libraries despite unchanged program behavior. The option “Choose Compute Engine Windows instances for an interim supported host” instead addresses the requested architecture selection.
B:
Repackaging does not remove Windows-only executable dependencies. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that temporary hosting must keep vendor support and monthly patch controls.
C:
The alternative “Inventory licensing, runtime dependencies and supported OS baseline” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, vendor test fails on Linux libraries despite unchanged program behavior. The option “Choose Compute Engine Windows instances for an interim supported host” instead addresses the requested architecture selection.
Question 799
Consider Smart-grid aggregation provider and its remote operator privilege workload. The issue is that contractors can run privileged maintenance on all grid data collectors; the current observation is that session audit shows support requests without approved change windows. The team must ensure that critical grid safety commands must remain restricted. Which continuous monitoring approach best reveals recurrence or changing dependencies?
- Use least-privilege IAM plus centrally recorded privileged sessions and approved windows
- Give all external contractors unbounded owner privileges to speed repair
- Verify off-window operator commands fail while approved maintenance works
- Monitor exceptional elevation, unreviewed sessions and expiry
Explanation
Correct Answer
D:
Monitor exceptional elevation, unreviewed sessions and expiry reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (contractors can run privileged maintenance on all grid data collectors) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Use least-privilege IAM plus centrally recorded privileged sessions and approved windows” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, session audit shows support requests without approved change windows. The option “Monitor exceptional elevation, unreviewed sessions and expiry” instead addresses the requested ongoing operational assurance.
B:
Standing global privilege defeats accountable contractor access. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that critical grid safety commands must remain restricted.
C:
The alternative “Verify off-window operator commands fail while approved maintenance works” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, session audit shows support requests without approved change windows. The option “Monitor exceptional elevation, unreviewed sessions and expiry” instead addresses the requested ongoing operational assurance.
Question 800
Consider National weather agency and its alert dissemination workload. The issue is that the weather alert app must handle a sudden 30-fold audience jump when storms hit; the current observation is that metrics reveal static instances hit connection limits while message publication remains healthy. The team must ensure that government alerts must be delivered promptly during severe weather. The change committee needs to understand the current system rather than install a fix yet. What should it do?
- Canary autoscaling limits and emergency alert handling under load
- Profile connection saturation, geography and alert publication SLO
- Separate publish from fan-out with managed scaling and geographic caching
- Disable rate and capacity limits without testing downstream quotas
Explanation
Correct Answer
B:
Profile connection saturation, geography and alert publication SLO is the appropriate diagnostic because the observation—metrics reveal static instances hit connection limits while message publication remains healthy—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (the weather alert app must handle a sudden 30-fold audience jump when storms hit) before the design is approved.
Incorrect Answers
A:
The alternative “Canary autoscaling limits and emergency alert handling under load” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, metrics reveal static instances hit connection limits while message publication remains healthy. The option “Profile connection saturation, geography and alert publication SLO” instead addresses the requested root-cause evidence.
C:
The alternative “Separate publish from fan-out with managed scaling and geographic caching” is target architecture selection; it does not establish why the observed path failed. In the reported observation, metrics reveal static instances hit connection limits while message publication remains healthy. The option “Profile connection saturation, geography and alert publication SLO” instead addresses the requested root-cause evidence.
D:
Unbounded fanout can exhaust dependencies rather than improving availability. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that government alerts must be delivered promptly during severe weather.