Google Professional Cloud Architect Practice Test 29
Question 280
Case study: Regional museum: global artifact web gallery
Regional museum relies on global artifact web gallery to deliver its operational commitments. The current architectural problem is that public image delivery overloads the origin service on exhibit announcement days. The team has recorded this evidence: traces show the same static media repeatedly retrieved by remote browsers. Any proposed response must preserve the requirement that private curator uploads must remain restricted while published assets are cacheable.
Regional museum plans to update global artifact web gallery. Investigators found that traces show the same static media repeatedly retrieved by remote browsers, consistent with the reported problem that public image delivery overloads the origin service on exhibit announcement days. The response must satisfy the requirement that private curator uploads must remain restricted while published assets are cacheable. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?
- Cache authenticated curator endpoints for every visitor under a shared key
- Launch edge caching for signed-public asset paths with invalidation procedure
- Measure static/dynamic request mix, cache control and publication boundaries
- Serve public assets through Cloud CDN while keeping private edit APIs uncached
Explanation
Correct Answer
C:
Measure static/dynamic request mix, cache control and publication boundaries is the appropriate diagnostic because the observation—traces show the same static media repeatedly retrieved by remote browsers—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (public image delivery overloads the origin service on exhibit announcement days) before the design is approved.
Incorrect Answers
A:
Shared caching of private responses can leak unreleased content. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that private curator uploads must remain restricted while published assets are cacheable.
B:
The alternative “Launch edge caching for signed-public asset paths with invalidation procedure” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, traces show the same static media repeatedly retrieved by remote browsers. The option “Measure static/dynamic request mix, cache control and publication boundaries” instead addresses the requested root-cause evidence.
D:
The alternative “Serve public assets through Cloud CDN while keeping private edit APIs uncached” is target architecture selection; it does not establish why the observed path failed. In the reported observation, traces show the same static media repeatedly retrieved by remote browsers. The option “Measure static/dynamic request mix, cache control and publication boundaries” instead addresses the requested root-cause evidence.
Question 281
The student records database environment at Public school administration faces this issue: developers chose key-value storage but school reports need relational joins and ACID updates. Supporting evidence shows that schema analysis shows normalized enrollment, grades and billing tables. The architect must preserve the requirement that data must stay region-bound and consistent across student updates. Which migration or rollout step best manages risk, dependencies and reversibility?
- Monitor connection pressure, replica lag and backup recoverability
- Migrate with Database Migration Service and compare transactional checksums
- Use unstructured object storage as a drop-in SQL transaction engine
- Choose managed Cloud SQL PostgreSQL for compatible relational transactions and backups
Explanation
Correct Answer
B:
Migrate with Database Migration Service and compare transactional checksums is a controlled means to introduce the approved architecture while meeting the requirement that data must stay region-bound and consistent across student updates. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Monitor connection pressure, replica lag and backup recoverability” addresses later monitoring rather than the actual controlled deployment. In the reported observation, schema analysis shows normalized enrollment, grades and billing tables. The option “Migrate with Database Migration Service and compare transactional checksums” instead addresses the requested controlled implementation.
C:
Object storage cannot replace a relational transaction and query layer. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that data must stay region-bound and consistent across student updates.
D:
The alternative “Choose managed Cloud SQL PostgreSQL for compatible relational transactions and backups” describes the chosen design, but not how it is introduced safely. In the reported observation, schema analysis shows normalized enrollment, grades and billing tables. The option “Migrate with Database Migration Service and compare transactional checksums” instead addresses the requested controlled implementation.
Question 282
At Green energy trading service, the Google Cloud design for runbook resilience is affected because a repeated Cloud SQL failover is handled differently by each on-call engineer. A review found that incident notes show conflicting restart commands and missing escalation steps. The proposed response must account for the requirement that financial settlement recovery must be repeatable and auditable. The cause has been established and a lasting architecture is being selected. Which design best meets the constraint?
- Reconstruct failures, decision points and runbook gaps
- Allow responders to improvise privileged database deletion during every outage
- Track runbook deviation, recovery duration and incomplete action items
- Create versioned runbooks and automated safe diagnostics with approval points
Explanation
Correct Answer
D:
Create versioned runbooks and automated safe diagnostics with approval points targets the underlying issue (a repeated Cloud SQL failover is handled differently by each on-call engineer) rather than merely reporting symptoms. It also preserves the required outcome (financial settlement recovery must be repeatable and auditable), which a target-state design must satisfy.
Incorrect Answers
A:
The alternative “Reconstruct failures, decision points and runbook gaps” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, incident notes show conflicting restart commands and missing escalation steps. The option “Create versioned runbooks and automated safe diagnostics with approval points” instead addresses the requested architecture selection.
B:
Uncontrolled destructive actions increase recovery risk. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that financial settlement recovery must be repeatable and auditable.
C:
The alternative “Track runbook deviation, recovery duration and incomplete action items” measures results without defining the preventive design now required. In the reported observation, incident notes show conflicting restart commands and missing escalation steps. The option “Create versioned runbooks and automated safe diagnostics with approval points” instead addresses the requested architecture selection.
Question 283
Case study: Metropolitan bus operator: customer API throttling
Metropolitan bus operator relies on customer API throttling to deliver its operational commitments. The current architectural problem is that one external client causes an overloaded trip-planning API while most users are normal. The team has recorded this evidence: gateway logs show one tenant produces 80% of requests. Any proposed response must preserve the requirement that emergency schedule lookups must remain available to all operators.
Metropolitan bus operator plans to update customer API throttling. Investigators found that gateway logs show one tenant produces 80% of requests, consistent with the reported problem that one external client causes an overloaded trip-planning API while most users are normal. The response must satisfy the requirement that emergency schedule lookups must remain available to all operators. The team needs an operations signal rather than another design or one-time test. What should it track?
- Track quota denials, tenant fairness and false throttling
- Apply a single global rate cap that blocks every tenant equally
- Design per-tenant API quotas and fairness policies using Apigee
- Load test abusive tenant traffic while verifying emergency operators succeed
Explanation
Correct Answer
A:
Track quota denials, tenant fairness and false throttling reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (one external client causes an overloaded trip-planning API while most users are normal) rather than treating the first successful test as permanent assurance.
Incorrect Answers
B:
A global cap penalizes unaffected users rather than noisy clients. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that emergency schedule lookups must remain available to all operators.
C:
The alternative “Design per-tenant API quotas and fairness policies using Apigee” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, gateway logs show one tenant produces 80% of requests. The option “Track quota denials, tenant fairness and false throttling” instead addresses the requested ongoing operational assurance.
D:
The alternative “Load test abusive tenant traffic while verifying emergency operators succeed” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, gateway logs show one tenant produces 80% of requests. The option “Track quota denials, tenant fairness and false throttling” instead addresses the requested ongoing operational assurance.
Question 284
Case study: Regional public broadcaster: license-compliant migration planning
Regional public broadcaster relies on license-compliant migration planning to deliver its operational commitments. The current architectural problem is that cloud project budget ignores legacy transcoding license entitlements. The team has recorded this evidence: vendor contract requires designated cores and annual renewal. Any proposed response must preserve the requirement that broadcast licensing must remain valid across hybrid operation.
Consider Regional public broadcaster and its license-compliant migration planning workload. The issue is that cloud project budget ignores legacy transcoding license entitlements; the current observation is that vendor contract requires designated cores and annual renewal. The team must ensure that broadcast licensing must remain valid across hybrid operation. The change committee needs to understand the current system rather than install a fix yet. What should it do?
- Choose a hosting disposition reflecting license and future refactor cost
- Inventory entitlement terms, renewal dates and workload migration sequence
- Assume cloud pay-as-you-go billing automatically grants third-party software licenses
- Stage licensed capacity migration with legal review and rollback
Explanation
Correct Answer
B:
Inventory entitlement terms, renewal dates and workload migration sequence is the appropriate diagnostic because the observation—vendor contract requires designated cores and annual renewal—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (cloud project budget ignores legacy transcoding license entitlements) before the design is approved.
Incorrect Answers
A:
The alternative “Choose a hosting disposition reflecting license and future refactor cost” is target architecture selection; it does not establish why the observed path failed. In the reported observation, vendor contract requires designated cores and annual renewal. The option “Inventory entitlement terms, renewal dates and workload migration sequence” instead addresses the requested root-cause evidence.
C:
Infrastructure payment does not confer separate application rights. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that broadcast licensing must remain valid across hybrid operation.
D:
The alternative “Stage licensed capacity migration with legal review and rollback” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, vendor contract requires designated cores and annual renewal. The option “Inventory entitlement terms, renewal dates and workload migration sequence” instead addresses the requested root-cause evidence.
Question 285
National grocery cooperative plans to update Gemini Cloud Assist runbook recommendations. Investigators found that review finds recommendations do not reflect a special pharmacy-workload SLA, consistent with the reported problem that an engineer proposes applying suggested infrastructure edits directly to production. The response must satisfy the requirement that critical pharmacy distribution cannot be disrupted by unreviewed changes. The team needs an operations signal rather than another design or one-time test. What should it track?
- Define human-reviewed change proposals with policy and unit tests
- Run resilience tests confirming the recommendation preserves pharmacy service
- Execute every model-generated shell command as project Owner without review
- Track AI-assisted changes, rejected suggestions and postrelease incidents
Explanation
Correct Answer
D:
Track AI-assisted changes, rejected suggestions and postrelease incidents reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (an engineer proposes applying suggested infrastructure edits directly to production) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Define human-reviewed change proposals with policy and unit tests” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, review finds recommendations do not reflect a special pharmacy-workload SLA. The option “Track AI-assisted changes, rejected suggestions and postrelease incidents” instead addresses the requested ongoing operational assurance.
B:
The alternative “Run resilience tests confirming the recommendation preserves pharmacy service” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, review finds recommendations do not reflect a special pharmacy-workload SLA. The option “Track AI-assisted changes, rejected suggestions and postrelease incidents” instead addresses the requested ongoing operational assurance.
C:
An AI suggestion is not an authorized or validated operational change. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that critical pharmacy distribution cannot be disrupted by unreviewed changes.
Question 286
The payment token audit environment at City parking payment app faces this issue: service records full PAN in debug logs while application database is tokenized. Supporting evidence shows that log sample includes unmasked card numbers in error traces. The architect must preserve the requirement that payment operations require minimized log retention and incident-ready evidence. Which migration or rollout step best manages risk, dependencies and reversibility?
- Remove PAN from telemetry and apply scoped tokenization and log redaction
- Use TLS on log transport and keep full card numbers indefinitely
- Monitor new PAN detections and changes in logging pipeline
- Deploy sanitized logging with backfill remediation and evidence preservation
Explanation
Correct Answer
D:
Deploy sanitized logging with backfill remediation and evidence preservation is a controlled means to introduce the approved architecture while meeting the requirement that payment operations require minimized log retention and incident-ready evidence. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Remove PAN from telemetry and apply scoped tokenization and log redaction” describes the chosen design, but not how it is introduced safely. In the reported observation, log sample includes unmasked card numbers in error traces. The option “Deploy sanitized logging with backfill remediation and evidence preservation” instead addresses the requested controlled implementation.
B:
Transport encryption alone does not minimize sensitive logged content. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that payment operations require minimized log retention and incident-ready evidence.
C:
The alternative “Monitor new PAN detections and changes in logging pipeline” addresses later monitoring rather than the actual controlled deployment. In the reported observation, log sample includes unmasked card numbers in error traces. The option “Deploy sanitized logging with backfill remediation and evidence preservation” instead addresses the requested controlled implementation.
Question 287
The SQL query optimization environment at Community bank faces this issue: a loan search endpoint slowed after adding optional fuzzy-name filters. Supporting evidence shows that EXPLAIN plans show full scans on a growing application table. The architect must preserve the requirement that loan updates must remain strongly consistent. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Monitor index bloat, costly queries and lock contention
- Design appropriate indexes and search pattern without changing transactional semantics
- Add more web servers without addressing the repeated full SQL scans
- Compare p95 and correctness of filtered results on representative workload
Explanation
Correct Answer
A:
Monitor index bloat, costly queries and lock contention reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a loan search endpoint slowed after adding optional fuzzy-name filters) rather than treating the first successful test as permanent assurance.
Incorrect Answers
B:
The alternative “Design appropriate indexes and search pattern without changing transactional semantics” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, EXPLAIN plans show full scans on a growing application table. The option “Monitor index bloat, costly queries and lock contention” instead addresses the requested ongoing operational assurance.
C:
A database plan problem will persist across extra web instances. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that loan updates must remain strongly consistent.
D:
The alternative “Compare p95 and correctness of filtered results on representative workload” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, EXPLAIN plans show full scans on a growing application table. The option “Monitor index bloat, costly queries and lock contention” instead addresses the requested ongoing operational assurance.
Question 288
Case study: Subscription video startup: BigQuery warehouse scan cost
Subscription video startup relies on BigQuery warehouse scan cost to deliver its operational commitments. The current architectural problem is that queries scan every historical event for simple daily subscriber counts. The team has recorded this evidence: query plan shows 5TB scanned despite filtering for yesterday. Any proposed response must preserve the requirement that marketing results must arrive within its daily budget.
The BigQuery warehouse scan cost environment at Subscription video startup faces this issue: queries scan every historical event for simple daily subscriber counts. Supporting evidence shows that query plan shows 5TB scanned despite filtering for yesterday. The architect must preserve the requirement that marketing results must arrive within its daily budget. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Alert on nonpartitioned scans, query budgets and freshness
- Replace predicates with full-table SELECT star on each dashboard load
- Use date-partitioned tables and suitable clustering with governed query patterns
- Compare scanned bytes and answer parity for the same daily report
Explanation
Correct Answer
A:
Alert on nonpartitioned scans, query budgets and freshness reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (queries scan every historical event for simple daily subscriber counts) rather than treating the first successful test as permanent assurance.
Incorrect Answers
B:
Full scans multiply spend without improving daily freshness. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that marketing results must arrive within its daily budget.
C:
The alternative “Use date-partitioned tables and suitable clustering with governed query patterns” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, query plan shows 5TB scanned despite filtering for yesterday. The option “Alert on nonpartitioned scans, query budgets and freshness” instead addresses the requested ongoing operational assurance.
D:
The alternative “Compare scanned bytes and answer parity for the same daily report” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, query plan shows 5TB scanned despite filtering for yesterday. The option “Alert on nonpartitioned scans, query budgets and freshness” instead addresses the requested ongoing operational assurance.
Question 289
Wildlife conservation nonprofit plans to update field-research collection. Investigators found that team interviews identify intermittent connectivity and controlled-location access, consistent with the reported problem that donor funding requires an inexpensive platform but volunteers collect sensitive species locations. The response must satisfy the requirement that precise nesting coordinates must remain inaccessible to public donors. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?
- Publish exact endangered-species coordinates to prove collection completeness
- Pilot one field team with conflict-aware synchronization and revocable researcher identities
- Use offline-capable mobile capture with encrypted private storage and aggregated donor reports
- Classify location sensitivity, offline sync needs, donation objectives and cost boundaries
Explanation
Correct Answer
D:
Classify location sensitivity, offline sync needs, donation objectives and cost boundaries is the appropriate diagnostic because the observation—team interviews identify intermittent connectivity and controlled-location access—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (donor funding requires an inexpensive platform but volunteers collect sensitive species locations) before the design is approved.
Incorrect Answers
A:
Sensitive location disclosure could enable poaching and defeat privacy requirements. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that precise nesting coordinates must remain inaccessible to public donors.
B:
The alternative “Pilot one field team with conflict-aware synchronization and revocable researcher identities” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, team interviews identify intermittent connectivity and controlled-location access. The option “Classify location sensitivity, offline sync needs, donation objectives and cost boundaries” instead addresses the requested root-cause evidence.
C:
The alternative “Use offline-capable mobile capture with encrypted private storage and aggregated donor reports” is target architecture selection; it does not establish why the observed path failed. In the reported observation, team interviews identify intermittent connectivity and controlled-location access. The option “Classify location sensitivity, offline sync needs, donation objectives and cost boundaries” instead addresses the requested root-cause evidence.
Question 290
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 managed Prometheus scraping workload has a documented risk: several GKE services expose metrics but the monitoring system has blind spots after namespace moves. The review found that scrape health shows targets disappeared when Kubernetes labels changed. The architecture must also ensure that capacity alerts must remain tied to actual service discovery. What enduring Google Cloud design should the team choose now that the failure mode is understood?
- Treat all unlabeled zero metrics as healthy application inactivity
- Watch missing targets, cardinality growth and failed scrapes
- Configure Managed Service for Prometheus collectors with stable target discovery
- Inspect Kubernetes service selectors, relabeling and scrape permissions
Explanation
Correct Answer
C:
Configure Managed Service for Prometheus collectors with stable target discovery targets the underlying issue (several GKE services expose metrics but the monitoring system has blind spots after namespace moves) rather than merely reporting symptoms. It also preserves the required outcome (capacity alerts must remain tied to actual service discovery), which a target-state design must satisfy.
Incorrect Answers
A:
Missing scrape targets can look like falsely healthy zeros. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that capacity alerts must remain tied to actual service discovery.
B:
The alternative “Watch missing targets, cardinality growth and failed scrapes” measures results without defining the preventive design now required. In the reported observation, scrape health shows targets disappeared when Kubernetes labels changed. The option “Configure Managed Service for Prometheus collectors with stable target discovery” instead addresses the requested architecture selection.
D:
The alternative “Inspect Kubernetes service selectors, relabeling and scrape permissions” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, scrape health shows targets disappeared when Kubernetes labels changed. The option “Configure Managed Service for Prometheus collectors with stable target discovery” instead addresses the requested architecture selection.