Google Professional Cloud Architect Practice Test 58
Question 570
Case study: Children's learning app: optional analytics consent
Children's learning app relies on optional analytics consent to deliver its operational commitments. The current architectural problem is that a single consent toggle activates necessary learning features and optional behavioral profiling. The team has recorded this evidence: privacy review shows data collected before age-appropriate consent. Any proposed response must preserve the requirement that the core learning app must work without marketing analytics.
The optional analytics consent environment at Children's learning app faces this issue: a single consent toggle activates necessary learning features and optional behavioral profiling. Supporting evidence shows that privacy review shows data collected before age-appropriate consent. The architect must preserve the requirement that the core learning app must work without marketing analytics. 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?
- Watch consent version drift, retention expiry and unapproved SDK exports
- Treat a buried general terms checkbox as unlimited future consent
- Accept the deployment ticket as proof that the control has no remaining security or availability risk
- Identify jurisdiction, age thresholds, purposes and lawful processing basis
- Separate essential learning processing from optional profiling with audited consent controls
- Verify refusal of analytics consent does not interrupt core features
Explanation
Correct Answers
A:
Watch consent version drift, retention expiry and unapproved SDK exports reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a single consent toggle activates necessary learning features and optional behavioral profiling) rather than treating the first successful test as permanent assurance. It supplies the ongoing observation requested.
D:
Identify jurisdiction, age thresholds, purposes and lawful processing basis is the appropriate diagnostic because the observation—privacy review shows data collected before age-appropriate consent—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (a single consent toggle activates necessary learning features and optional behavioral profiling) before the design is approved. It supplies the pre-design diagnostic evidence requested.
F:
Verify refusal of analytics consent does not interrupt core features is a direct acceptance test of the path implicated by privacy review shows data collected before age-appropriate consent. It checks that the original risk (a single consent toggle activates necessary learning features and optional behavioral profiling) has actually been controlled and tests that permitted operations still meet the requirement that the core learning app must work without marketing analytics. It supplies the separate post-change acceptance result requested.
Incorrect Answers
B:
Broad terms cannot replace purpose-specific protections for minors. It cannot satisfy the required evidence stages.
C:
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: privacy review shows data collected before age-appropriate consent.
E:
Designing optional analytics consent addresses the root cause, but this specific three-part question asks for evidence to diagnose, accept and continuously verify the response to a single consent toggle activates necessary learning features and optional behavioral profiling, not another design proposal.
Question 571
At Global manufacturing supplier, the Google Cloud design for product catalog service is affected because a document catalog changes shape frequently across suppliers and needs low-latency mobile reads. A review found that sample records have evolving nested attributes but no multirow transaction need. The proposed response must account for the requirement that catalog availability matters more than cross-product SQL joins. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?
- Make every supplier share an unrestricted project-wide data role
- Select Firestore document storage with explicit security rules and required indexes
- Track index growth, latency and document read costs
- Query representative evolving attributes and test unauthorized reads
Explanation
Correct Answer
C:
Track index growth, latency and document read costs reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a document catalog changes shape frequently across suppliers and needs low-latency mobile reads) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
Broad permissions negate document-level access rules. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that catalog availability matters more than cross-product SQL joins.
B:
The alternative “Select Firestore document storage with explicit security rules and required indexes” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, sample records have evolving nested attributes but no multirow transaction need. The option “Track index growth, latency and document read costs” instead addresses the requested ongoing operational assurance.
D:
The alternative “Query representative evolving attributes and test unauthorized reads” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, sample records have evolving nested attributes but no multirow transaction need. The option “Track index growth, latency and document read costs” instead addresses the requested ongoing operational assurance.
Question 572
The research compute funding environment at Regional university consortium faces this issue: department costs are assigned equally although GPU workloads dominate reserved capacity. Supporting evidence shows that billing exports show two laboratories use most training accelerator hours. The architect must preserve the requirement that sensitive lab datasets cannot be exposed through a central chargeback dashboard. Which migration or rollout step best manages risk, dependencies and reversibility?
- Design labeled projects and aggregated cost allocation with workload-specific budgets
- Monitor unlabeled accelerator spend and resource commitments by department
- Introduce project labeling and budgets before moving accelerator jobs
- Publish raw dataset labels and individual researcher usage to all departments
Explanation
Correct Answer
C:
Introduce project labeling and budgets before moving accelerator jobs is a controlled means to introduce the approved architecture while meeting the requirement that sensitive lab datasets cannot be exposed through a central chargeback dashboard. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Design labeled projects and aggregated cost allocation with workload-specific budgets” describes the chosen design, but not how it is introduced safely. In the reported observation, billing exports show two laboratories use most training accelerator hours. The option “Introduce project labeling and budgets before moving accelerator jobs” instead addresses the requested controlled implementation.
B:
The alternative “Monitor unlabeled accelerator spend and resource commitments by department” addresses later monitoring rather than the actual controlled deployment. In the reported observation, billing exports show two laboratories use most training accelerator hours. The option “Introduce project labeling and budgets before moving accelerator jobs” instead addresses the requested controlled implementation.
D:
Overbroad chargeback visibility can reveal sensitive research details. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that sensitive lab datasets cannot be exposed through a central chargeback dashboard.
Question 573
At Municipal environmental sensors, the Google Cloud design for streaming pipeline deployment is affected because operators change sensor parsers directly in production and corrupt previously valid samples. A review found that new parser interprets temperature units differently from prior version. The proposed response must account for the requirement that environmental alerts must preserve accurate measurements. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Watch schema errors and suspicious unit-distribution changes
- Deploy new parsers in shadow mode and compare to existing pipeline
- Review schema fields, unit provenance and historical interpretation
- Treat all sensor readings as degrees Celsius regardless of source metadata
- Define versioned schemas and stable transformation contracts
Explanation
Correct Answers
B:
Deploy new parsers in shadow mode and compare to existing pipeline is a controlled means to introduce the approved architecture while meeting the requirement that environmental alerts must preserve accurate measurements. 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:
Define versioned schemas and stable transformation contracts targets the underlying issue (operators change sensor parsers directly in production and corrupt previously valid samples) rather than merely reporting symptoms. It also preserves the required outcome (environmental alerts must preserve accurate measurements), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
Incorrect Answers
A:
Monitoring streaming pipeline deployment for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: operators change sensor parsers directly in production and corrupt previously valid samples.
C:
This diagnoses the original issue (operators change sensor parsers directly in production and corrupt previously valid samples), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
D:
Ignoring units changes physical meaning of measurements. The shortcut does not supply the requested design and safe rollout for streaming pipeline deployment, where new parser interprets temperature units differently from prior version.
Question 574
At Digital rehabilitation provider, the video consultation storage workload has a documented risk: the initial backup design stores both primary recordings and snapshots in one project. The review found that access review shows a project editor can delete all versions. The architecture must also ensure that clinical videos require recovery after a compromised administration account. What enduring Google Cloud design should the team choose now that the failure mode is understood?
- Use cross-project immutable retention and scoped recovery identities
- Monitor privileged retention changes, backup failures and restore timing
- Keep backups as deletable snapshots owned by the same compromised principal
- Map project trust boundaries, retention and insider-deletion threat
Explanation
Correct Answer
A:
Use cross-project immutable retention and scoped recovery identities targets the underlying issue (the initial backup design stores both primary recordings and snapshots in one project) rather than merely reporting symptoms. It also preserves the required outcome (clinical videos require recovery after a compromised administration account), which a target-state design must satisfy.
Incorrect Answers
B:
The alternative “Monitor privileged retention changes, backup failures and restore timing” measures results without defining the preventive design now required. In the reported observation, access review shows a project editor can delete all versions. The option “Use cross-project immutable retention and scoped recovery identities” instead addresses the requested architecture selection.
C:
Shared delete authority destroys recovery independence. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that clinical videos require recovery after a compromised administration account.
D:
The alternative “Map project trust boundaries, retention and insider-deletion threat” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, access review shows a project editor can delete all versions. The option “Use cross-project immutable retention and scoped recovery identities” instead addresses the requested architecture selection.
Question 575
Consider Public grant agency and its executive decision analysis workload. The issue is that project review scores optional chatbot convenience higher than accessibility and regulatory filing; the current observation is that business case omits users reliant on assistive technologies. The team must ensure that benefit delivery must meet accessible filing requirements. Which continuous monitoring approach best reveals recurrence or changing dependencies?
- Validate assisted-technology filing success against user acceptance criteria
- Approve the chatbot solely because it uses the newest language model
- Monitor accessibility incidents and task completion outcomes
- Prioritize accessible essential workflow before optional AI enhancements
Explanation
Correct Answer
C:
Monitor accessibility incidents and task completion outcomes reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (project review scores optional chatbot convenience higher than accessibility and regulatory filing) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Validate assisted-technology filing success against user acceptance criteria” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, business case omits users reliant on assistive technologies. The option “Monitor accessibility incidents and task completion outcomes” instead addresses the requested ongoing operational assurance.
B:
Novelty does not meet the required filing accessibility outcome. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that benefit delivery must meet accessible filing requirements.
D:
The alternative “Prioritize accessible essential workflow before optional AI enhancements” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, business case omits users reliant on assistive technologies. The option “Monitor accessibility incidents and task completion outcomes” instead addresses the requested ongoing operational assurance.
Question 576
At International hotel chain, the central incident notification API workload has a documented risk: operations migrates a notification service before updating caller authentication and message retry rules. The review found that test customers see duplicate room-change notifications. The architecture must also ensure that customer booking updates must remain unique and attributable. Which post-change test most reliably distinguishes a functioning control from a merely successful installation?
- Disable all retries and discard messages when the first send fails
- Inject duplicate delivery attempts and verify one customer-visible notification
- Review retry, authentication and idempotency semantics across partners
- Move partners through versioned API deployment with replayable messages
Explanation
Correct Answer
B:
Inject duplicate delivery attempts and verify one customer-visible notification is a direct acceptance test of the path implicated by test customers see duplicate room-change notifications. It checks that the original risk (operations migrates a notification service before updating caller authentication and message retry rules) has actually been controlled and tests that permitted operations still meet the requirement that customer booking updates must remain unique and attributable.
Incorrect Answers
A:
At-most-once loss does not meet delivery commitments. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that customer booking updates must remain unique and attributable.
C:
The alternative “Review retry, authentication and idempotency semantics across partners” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, test customers see duplicate room-change notifications. The option “Inject duplicate delivery attempts and verify one customer-visible notification” instead addresses the requested acceptance verification.
D:
The alternative “Move partners through versioned API deployment with replayable messages” documents change execution but not its operational acceptance result. In the reported observation, test customers see duplicate room-change notifications. The option “Inject duplicate delivery attempts and verify one customer-visible notification” instead addresses the requested acceptance verification.
Question 577
Case study: Industrial distributor: interwarehouse shipment events
Industrial distributor relies on interwarehouse shipment events to deliver its operational commitments. The current architectural problem is that orders must trigger independent finance and warehouse actions without a central polling table. The team has recorded this evidence: architecture diagram shows tight synchronous calls to five downstream services. Any proposed response must preserve the requirement that an outage in accounting must not block physical pick requests.
Industrial distributor plans to update interwarehouse shipment events. Investigators found that architecture diagram shows tight synchronous calls to five downstream services, consistent with the reported problem that orders must trigger independent finance and warehouse actions without a central polling table. The response must satisfy the requirement that an outage in accounting must not block physical pick requests. The team needs an operations signal rather than another design or one-time test. What should it track?
- Disconnect accounting and verify warehouse consumers continue and replay later
- Have warehouse service synchronously call every downstream system before confirming an order
- Publish durable order events to Pub/Sub subscriptions for decoupled consumers
- Monitor backlog, dead letters and per-consumer delivery lag
Explanation
Correct Answer
D:
Monitor backlog, dead letters and per-consumer delivery lag reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (orders must trigger independent finance and warehouse actions without a central polling table) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Disconnect accounting and verify warehouse consumers continue and replay later” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, architecture diagram shows tight synchronous calls to five downstream services. The option “Monitor backlog, dead letters and per-consumer delivery lag” instead addresses the requested ongoing operational assurance.
B:
Synchronous fanout propagates a slow consumer into order failures. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that an outage in accounting must not block physical pick requests.
C:
The alternative “Publish durable order events to Pub/Sub subscriptions for decoupled consumers” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, architecture diagram shows tight synchronous calls to five downstream services. The option “Monitor backlog, dead letters and per-consumer delivery lag” instead addresses the requested ongoing operational assurance.
Question 578
Consider Automotive safety modeling startup and its reinforcement model evaluation workload. The issue is that engineering wants to deploy a new model before proving corner-case behavior; the current observation is that evaluation report covers average accuracy but no rare safety-critical maneuvers. The team must ensure that safety review requires rigorous offline evaluation and rollback. Which acceptance test should demonstrate both protection against the failure and continued authorized service?
- Define rare-event evaluation cases, adversarial tests and traceability
- Replay corner-case simulation corpus and verify failure thresholds before release
- Approve the model solely because aggregate accuracy rose one percent
- Introduce shadow inference before any controlled production promotion
Explanation
Correct Answer
B:
Replay corner-case simulation corpus and verify failure thresholds before release is a direct acceptance test of the path implicated by evaluation report covers average accuracy but no rare safety-critical maneuvers. It checks that the original risk (engineering wants to deploy a new model before proving corner-case behavior) has actually been controlled and tests that permitted operations still meet the requirement that safety review requires rigorous offline evaluation and rollback.
Incorrect Answers
A:
The alternative “Define rare-event evaluation cases, adversarial tests and traceability” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, evaluation report covers average accuracy but no rare safety-critical maneuvers. The option “Replay corner-case simulation corpus and verify failure thresholds before release” instead addresses the requested acceptance verification.
C:
Mean accuracy can hide unacceptable safety-regression tails. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that safety review requires rigorous offline evaluation and rollback.
D:
The alternative “Introduce shadow inference before any controlled production promotion” documents change execution but not its operational acceptance result. In the reported observation, evaluation report covers average accuracy but no rare safety-critical maneuvers. The option “Replay corner-case simulation corpus and verify failure thresholds before release” instead addresses the requested acceptance verification.
Question 579
Case study: Healthcare billing analytics: log-based incident metrics
Healthcare billing analytics relies on log-based incident metrics to deliver its operational commitments. The current architectural problem is that an API error log is present but there is no alert on rising failed invoice reconciliation. The team has recorded this evidence: log query shows 15% payment finalization errors during partner outage. Any proposed response must preserve the requirement that financial integrity requires detection before end-of-day settlement.
At Healthcare billing analytics, the Google Cloud design for log-based incident metrics is affected because an API error log is present but there is no alert on rising failed invoice reconciliation. A review found that log query shows 15% payment finalization errors during partner outage. The proposed response must account for the requirement that financial integrity requires detection before end-of-day settlement. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?
- Emit representative failure logs and verify actionable alert delivery
- Define a log-based metric and threshold tied to reconciliation impact
- Only send a weekly email digest for critical reconciliation failures
- Track metric ingestion gaps and false positives
Explanation
Correct Answer
D:
Track metric ingestion gaps and false positives reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (an API error log is present but there is no alert on rising failed invoice reconciliation) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Emit representative failure logs and verify actionable alert delivery” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, log query shows 15% payment finalization errors during partner outage. The option “Track metric ingestion gaps and false positives” instead addresses the requested ongoing operational assurance.
B:
The alternative “Define a log-based metric and threshold tied to reconciliation impact” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, log query shows 15% payment finalization errors during partner outage. The option “Track metric ingestion gaps and false positives” instead addresses the requested ongoing operational assurance.
C:
A weekly summary misses urgent financial incidents. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that financial integrity requires detection before end-of-day settlement.
Question 580
Case study: Cross-border payment provider: regulated retention policy
Cross-border payment provider relies on regulated retention policy to deliver its operational commitments. The current architectural problem is that cloud backups are replicated globally without legal review of data-residency restrictions. The team has recorded this evidence: compliance assessment finds a bucket's secondary location is outside allowed jurisdiction. Any proposed response must preserve the requirement that cardholder data must remain only in approved processing geography.
At Cross-border payment provider, the regulated retention policy workload has a documented risk: cloud backups are replicated globally without legal review of data-residency restrictions. The review found that compliance assessment finds a bucket's secondary location is outside allowed jurisdiction. The architecture must also ensure that cardholder data must remain only in approved processing geography. What follow-up metric or alert will identify emerging failures after the initial acceptance test?
- Store the most sensitive copies in any multi-region regardless of its constituent locations
- Use region-restricted storage, key policies and authenticated retention records
- Prove primary and recovery copies remain in allowed geography after failover
- Review location-policy changes, recovery tests and retention deviations
Explanation
Correct Answer
D:
Review location-policy changes, recovery tests and retention deviations reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (cloud backups are replicated globally without legal review of data-residency restrictions) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
A global location can violate specific geographic transfer restrictions. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that cardholder data must remain only in approved processing geography.
B:
The alternative “Use region-restricted storage, key policies and authenticated retention records” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, compliance assessment finds a bucket's secondary location is outside allowed jurisdiction. The option “Review location-policy changes, recovery tests and retention deviations” instead addresses the requested ongoing operational assurance.
C:
The alternative “Prove primary and recovery copies remain in allowed geography after failover” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, compliance assessment finds a bucket's secondary location is outside allowed jurisdiction. The option “Review location-policy changes, recovery tests and retention deviations” instead addresses the requested ongoing operational assurance.