Google Professional Cloud Architect Practice Test 4
Question 30
Municipal environmental sensors plans to update streaming pipeline deployment. Investigators found that new parser interprets temperature units differently from prior version, consistent with the reported problem that operators change sensor parsers directly in production and corrupt previously valid samples. The response must satisfy the requirement that environmental alerts must preserve accurate measurements. The team needs an operations signal rather than another design or one-time test. What should it track?
- Treat all sensor readings as degrees Celsius regardless of source metadata
- Define versioned schemas and stable transformation contracts
- Replay mixed unit messages and prove normalized readings match expected values
- Watch schema errors and suspicious unit-distribution changes
Explanation
Correct Answer
D:
Watch schema errors and suspicious unit-distribution changes reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (operators change sensor parsers directly in production and corrupt previously valid samples) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
Ignoring units changes physical meaning of measurements. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that environmental alerts must preserve accurate measurements.
B:
The alternative “Define versioned schemas and stable transformation contracts” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, new parser interprets temperature units differently from prior version. The option “Watch schema errors and suspicious unit-distribution changes” instead addresses the requested ongoing operational assurance.
C:
The alternative “Replay mixed unit messages and prove normalized readings match expected values” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, new parser interprets temperature units differently from prior version. The option “Watch schema errors and suspicious unit-distribution changes” instead addresses the requested ongoing operational assurance.
Question 31
Consider Industrial maintenance provider and its equipment-manual visual search workload. The issue is that staff send photos of parts and want to find matching safety documents; the current observation is that sample images are noisy while text identifiers are only partly visible. The team must ensure that manual search must not invent equipment safety instructions. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Let a generative model invent manufacturer safety procedures without retrieved evidence
- Assess image feature quality, metadata and trusted manual indexing
- Combine suitable Vision API extraction with grounded document search against approved manuals
- Pilot a small catalog with human review for low-confidence matches
- Track image extraction errors and obsolete manual versions
Explanation
Correct Answers
C:
Combine suitable Vision API extraction with grounded document search against approved manuals targets the underlying issue (staff send photos of parts and want to find matching safety documents) rather than merely reporting symptoms. It also preserves the required outcome (manual search must not invent equipment safety instructions), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
D:
Pilot a small catalog with human review for low-confidence matches is a controlled means to introduce the approved architecture while meeting the requirement that manual search must not invent equipment safety instructions. 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.
Incorrect Answers
A:
Hallucinated safety instructions can create physical risk. The shortcut does not supply the requested design and safe rollout for equipment-manual visual search, where sample images are noisy while text identifiers are only partly visible.
B:
This diagnoses the original issue (staff send photos of parts and want to find matching safety documents), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
E:
Monitoring equipment-manual visual search for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: staff send photos of parts and want to find matching safety documents.
Question 32
Case study: Regional outpatient clinics: clinical application identity
Regional outpatient clinics relies on clinical application identity to deliver its operational commitments. The current architectural problem is that container workloads use downloadable service-account keys in application configuration. The team has recorded this evidence: repository scan finds a private key committed in a build manifest. Any proposed response must preserve the requirement that production services require no long-lived exportable keys.
Regional outpatient clinics plans to update clinical application identity. Investigators found that repository scan finds a private key committed in a build manifest, consistent with the reported problem that container workloads use downloadable service-account keys in application configuration. The response must satisfy the requirement that production services require no long-lived exportable keys. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?
- Map callers, workload principals, leaked-key exposure and required IAM permissions
- Rotate exposed keys and migrate workloads to short-lived identity tokens safely
- Store the JSON key in a differently named repository folder
- Use Workload Identity Federation for GKE and narrowly scoped Google service accounts
Explanation
Correct Answer
A:
Map callers, workload principals, leaked-key exposure and required IAM permissions is the appropriate diagnostic because the observation—repository scan finds a private key committed in a build manifest—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (container workloads use downloadable service-account keys in application configuration) before the design is approved.
Incorrect Answers
B:
The alternative “Rotate exposed keys and migrate workloads to short-lived identity tokens safely” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, repository scan finds a private key committed in a build manifest. The option “Map callers, workload principals, leaked-key exposure and required IAM permissions” instead addresses the requested root-cause evidence.
C:
Renaming credentials does not protect or revoke them. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that production services require no long-lived exportable keys.
D:
The alternative “Use Workload Identity Federation for GKE and narrowly scoped Google service accounts” is target architecture selection; it does not establish why the observed path failed. In the reported observation, repository scan finds a private key committed in a build manifest. The option “Map callers, workload principals, leaked-key exposure and required IAM permissions” instead addresses the requested root-cause evidence.
Question 33
Case study: Community telehealth provider: clinical deployment training
Community telehealth provider relies on clinical deployment training to deliver its operational commitments. The current architectural problem is that a platform modernization plan assigns unfamiliar GKE on-call duties without staff enablement. The team has recorded this evidence: postmortems show alerts ignored because responders lack cluster permissions. Any proposed response must preserve the requirement that patient scheduling must be supported around the clock.
At Community telehealth provider, the clinical deployment training workload has a documented risk: a platform modernization plan assigns unfamiliar GKE on-call duties without staff enablement. The review found that postmortems show alerts ignored because responders lack cluster permissions. The architecture must also ensure that patient scheduling must be supported around the clock. What follow-up metric or alert will identify emerging failures after the initial acceptance test?
- Track runbook usage, responder readiness and escalation failures
- Run a simulated critical incident and verify correct escalation and resolution
- Plan role-specific training, escalation and supported operational runbooks
- Give production Owner to everyone as an alternative to training
Explanation
Correct Answer
A:
Track runbook usage, responder readiness and escalation failures reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a platform modernization plan assigns unfamiliar GKE on-call duties without staff enablement) rather than treating the first successful test as permanent assurance.
Incorrect Answers
B:
The alternative “Run a simulated critical incident and verify correct escalation and resolution” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, postmortems show alerts ignored because responders lack cluster permissions. The option “Track runbook usage, responder readiness and escalation failures” instead addresses the requested ongoing operational assurance.
C:
The alternative “Plan role-specific training, escalation and supported operational runbooks” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, postmortems show alerts ignored because responders lack cluster permissions. The option “Track runbook usage, responder readiness and escalation failures” instead addresses the requested ongoing operational assurance.
D:
Broad privilege does not create operational competence. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that patient scheduling must be supported around the clock.
Question 34
At Regional bank mortgage service, the SLI boundary selection workload has a documented risk: frontend availability dashboard shows 100% while database commit errors abort applications. The review found that synthetic API probes use a cached read endpoint only. The architecture must also ensure that home-loan approvals require successful authorized durable writes. Which post-change test most reliably distinguishes a functioning control from a merely successful installation?
- Use only HTTP ingress uptime as the loan approval SLI
- Force a database write failure and confirm SLI/alert reflects unsuccessful approvals
- Identify user-visible commit events and differentiate reads from writes
- Instrument accepted loan operations in live request tracing
Explanation
Correct Answer
B:
Force a database write failure and confirm SLI/alert reflects unsuccessful approvals is a direct acceptance test of the path implicated by synthetic API probes use a cached read endpoint only. It checks that the original risk (frontend availability dashboard shows 100% while database commit errors abort applications) has actually been controlled and tests that permitted operations still meet the requirement that home-loan approvals require successful authorized durable writes.
Incorrect Answers
A:
A reachable proxy does not prove committed financial transactions. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that home-loan approvals require successful authorized durable writes.
C:
The alternative “Identify user-visible commit events and differentiate reads from writes” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, synthetic API probes use a cached read endpoint only. The option “Force a database write failure and confirm SLI/alert reflects unsuccessful approvals” instead addresses the requested acceptance verification.
D:
The alternative “Instrument accepted loan operations in live request tracing” documents change execution but not its operational acceptance result. In the reported observation, synthetic API probes use a cached read endpoint only. The option “Force a database write failure and confirm SLI/alert reflects unsuccessful approvals” instead addresses the requested acceptance verification.
Question 35
The Cloud Run database connection storms environment at E-commerce promotion service faces this issue: a serverless revision scales quickly and exhausts a legacy SQL server's connection pool. Supporting evidence shows that database logs show connection refusals at promotion launch. The architect must preserve the requirement that backend must remain within database concurrency limits. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Allow unlimited cold-start instances to open independent large pools
- Stage maximum-instance limits and traffic splitting before peak events
- Set Cloud Run concurrency and instance limits with appropriate pooling
- Track rejected requests, instance count and DB pool utilization
- Calculate per-instance connection pools, maximum instances and request bursts
Explanation
Correct Answers
B:
Stage maximum-instance limits and traffic splitting before peak events is a controlled means to introduce the approved architecture while meeting the requirement that backend must remain within database concurrency limits. 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:
Set Cloud Run concurrency and instance limits with appropriate pooling targets the underlying issue (a serverless revision scales quickly and exhausts a legacy SQL server's connection pool) rather than merely reporting symptoms. It also preserves the required outcome (backend must remain within database concurrency limits), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
Incorrect Answers
A:
Unbounded scaling overwhelms a fixed database dependency. The shortcut does not supply the requested design and safe rollout for Cloud Run database connection storms, where database logs show connection refusals at promotion launch.
D:
Monitoring Cloud Run database connection storms for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: a serverless revision scales quickly and exhausts a legacy SQL server's connection pool.
E:
This diagnoses the original issue (a serverless revision scales quickly and exhausts a legacy SQL server's connection pool), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
Question 36
The sensitive research boundary environment at University public data project faces this issue: the analytics team shares projects with public application workloads. Supporting evidence shows that review finds protected training datasets readable from an unrelated compute project. The architect must preserve the requirement that university policy forbids exfiltration of patient-linked samples. What test must pass before the business accepts the remediated architecture?
- Use only object naming conventions to stop exfiltration
- Map trusted projects, access pathways, APIs and data-exfiltration threats
- Stage perimeter dry-run and egress policies before enforcing access boundaries
- Test denied cross-perimeter access and allowed research collaboration paths
Explanation
Correct Answer
D:
Test denied cross-perimeter access and allowed research collaboration paths is a direct acceptance test of the path implicated by review finds protected training datasets readable from an unrelated compute project. It checks that the original risk (the analytics team shares projects with public application workloads) has actually been controlled and tests that permitted operations still meet the requirement that university policy forbids exfiltration of patient-linked samples.
Incorrect Answers
A:
Naming cannot enforce data-access boundaries. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that university policy forbids exfiltration of patient-linked samples.
B:
The alternative “Map trusted projects, access pathways, APIs and data-exfiltration threats” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, review finds protected training datasets readable from an unrelated compute project. The option “Test denied cross-perimeter access and allowed research collaboration paths” instead addresses the requested acceptance verification.
C:
The alternative “Stage perimeter dry-run and egress policies before enforcing access boundaries” documents change execution but not its operational acceptance result. In the reported observation, review finds protected training datasets readable from an unrelated compute project. The option “Test denied cross-perimeter access and allowed research collaboration paths” instead addresses the requested acceptance verification.
Question 37
Online grocery delivery plans to update feature KPI design. Investigators found that business dashboards show missed deliveries after new routing service launch, consistent with the reported problem that migration success is defined as number of VMs shut down while delivery failures increase. The response must satisfy the requirement that the program must improve delivered-order reliability, not just infrastructure count. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?
- Call the project successful solely because the cloud invoice fell
- Introduce metrics dashboards with business owners and stable baselines
- Reconcile technical metrics with customer outcomes and fulfillment costs
- Define shared availability, on-time-delivery and cost-per-delivery KPIs
Explanation
Correct Answer
C:
Reconcile technical metrics with customer outcomes and fulfillment costs is the appropriate diagnostic because the observation—business dashboards show missed deliveries after new routing service launch—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (migration success is defined as number of VMs shut down while delivery failures increase) before the design is approved.
Incorrect Answers
A:
Lower spend can accompany worse business performance. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that the program must improve delivered-order reliability, not just infrastructure count.
B:
The alternative “Introduce metrics dashboards with business owners and stable baselines” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, business dashboards show missed deliveries after new routing service launch. The option “Reconcile technical metrics with customer outcomes and fulfillment costs” instead addresses the requested root-cause evidence.
D:
The alternative “Define shared availability, on-time-delivery and cost-per-delivery KPIs” is target architecture selection; it does not establish why the observed path failed. In the reported observation, business dashboards show missed deliveries after new routing service launch. The option “Reconcile technical metrics with customer outcomes and fulfillment costs” instead addresses the requested root-cause evidence.
Question 38
The 24-hour booking network environment at Emergency veterinary service faces this issue: the migration estimate ignores the impact of a failed regional booking queue. Supporting evidence shows that incident records show bookings lost when the only queue broker restarts. The architect must preserve the requirement that emergency hospitals must reconcile bookings after a site outage. What test must pass before the business accepts the remediated architecture?
- Calculate booking RPO/RTO, delivery guarantees and regional dependency chains
- Use an in-memory single-instance queue for all accepted bookings
- Dual-write for a controlled pilot with deterministic booking identifiers
- Simulate broker failure and confirm no duplicate bookings or lost accepted requests
Explanation
Correct Answer
D:
Simulate broker failure and confirm no duplicate bookings or lost accepted requests is a direct acceptance test of the path implicated by incident records show bookings lost when the only queue broker restarts. It checks that the original risk (the migration estimate ignores the impact of a failed regional booking queue) has actually been controlled and tests that permitted operations still meet the requirement that emergency hospitals must reconcile bookings after a site outage.
Incorrect Answers
A:
The alternative “Calculate booking RPO/RTO, delivery guarantees and regional dependency chains” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, incident records show bookings lost when the only queue broker restarts. The option “Simulate broker failure and confirm no duplicate bookings or lost accepted requests” instead addresses the requested acceptance verification.
B:
A volatile single broker loses accepted work on restart. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that emergency hospitals must reconcile bookings after a site outage.
C:
The alternative “Dual-write for a controlled pilot with deterministic booking identifiers” documents change execution but not its operational acceptance result. In the reported observation, incident records show bookings lost when the only queue broker restarts. The option “Simulate broker failure and confirm no duplicate bookings or lost accepted requests” instead addresses the requested acceptance verification.
Question 39
Consider Municipal parking authority and its legacy Oracle billing workload. The issue is that a tightly coupled database license cannot run cost-effectively in a naive VM lift-and-shift; the current observation is that license assessment shows processor-based fees exceed projected cloud infrastructure savings. The team must ensure that metered invoices must reconcile across cutover. The target architecture is approved; execution without disruption is the remaining decision. Which rollout action is best?
- Monitor license exposure, query regressions and reconciliation failures
- Trial a compatible subset with dual invoices and a rollback date
- Select a phased database disposition using compatibility and total cost, not VM price alone
- Ignore license rights because compute is billed hourly
Explanation
Correct Answer
B:
Trial a compatible subset with dual invoices and a rollback date is a controlled means to introduce the approved architecture while meeting the requirement that metered invoices must reconcile across cutover. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Monitor license exposure, query regressions and reconciliation failures” addresses later monitoring rather than the actual controlled deployment. In the reported observation, license assessment shows processor-based fees exceed projected cloud infrastructure savings. The option “Trial a compatible subset with dual invoices and a rollback date” instead addresses the requested controlled implementation.
C:
The alternative “Select a phased database disposition using compatibility and total cost, not VM price alone” describes the chosen design, but not how it is introduced safely. In the reported observation, license assessment shows processor-based fees exceed projected cloud infrastructure savings. The option “Trial a compatible subset with dual invoices and a rollback date” instead addresses the requested controlled implementation.
D:
Cloud billing does not nullify software licensing obligations. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that metered invoices must reconcile across cutover.
Question 40
At Medical supply chain, the CDC job performance regression workload has a documented risk: a nightly database export finishes late despite unchanged source volume. The review found that telemetry shows a new transformation now triggers full-table reloads. The architecture must also ensure that hospital inventory reports must arrive before morning replenishment. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Compare pipeline execution plan, input cardinality and transformation deltas
- Change to incremental CDC processing with checkpointed offsets
- Provision more dashboard servers while keeping the full reload
- Canary revised pipeline and reconcile late-arriving updates
Explanation
Correct Answer
A:
Compare pipeline execution plan, input cardinality and transformation deltas is the appropriate diagnostic because the observation—telemetry shows a new transformation now triggers full-table reloads—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (a nightly database export finishes late despite unchanged source volume) before the design is approved.
Incorrect Answers
B:
The alternative “Change to incremental CDC processing with checkpointed offsets” is target architecture selection; it does not establish why the observed path failed. In the reported observation, telemetry shows a new transformation now triggers full-table reloads. The option “Compare pipeline execution plan, input cardinality and transformation deltas” instead addresses the requested root-cause evidence.
C:
Dashboard compute does not correct an inefficient ingestion path. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that hospital inventory reports must arrive before morning replenishment.
D:
The alternative “Canary revised pipeline and reconcile late-arriving updates” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, telemetry shows a new transformation now triggers full-table reloads. The option “Compare pipeline execution plan, input cardinality and transformation deltas” instead addresses the requested root-cause evidence.