Google Professional Cloud Architect Practice Test 15
Question 140
Community farming platform plans to update gcloud project configuration. Investigators found that shell history shows wrong active project and accidental unrelated resource creation, consistent with the reported problem that engineers repeatedly use their personal projects when running deployment scripts. The response must satisfy the requirement that deployments must target designated staging projects only. The design review is over and production introduction is next. Which action is the best fit?
- Run deployment automation in isolated configuration environments
- Watch commands targeting unexpected project IDs
- Use explicit project arguments, scoped identities and scripted preflight checks
- Assume whatever project is active in Cloud Shell is always staging
Explanation
Correct Answer
A:
Run deployment automation in isolated configuration environments is a controlled means to introduce the approved architecture while meeting the requirement that deployments must target designated staging projects only. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
The alternative “Watch commands targeting unexpected project IDs” addresses later monitoring rather than the actual controlled deployment. In the reported observation, shell history shows wrong active project and accidental unrelated resource creation. The option “Run deployment automation in isolated configuration environments” instead addresses the requested controlled implementation.
C:
The alternative “Use explicit project arguments, scoped identities and scripted preflight checks” describes the chosen design, but not how it is introduced safely. In the reported observation, shell history shows wrong active project and accidental unrelated resource creation. The option “Run deployment automation in isolated configuration environments” instead addresses the requested controlled implementation.
D:
Ambient CLI context can target the wrong project. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that deployments must target designated staging projects only.
Question 141
National land registry plans to update admin console access. Investigators found that network scan discovers admin endpoints reachable without identity-aware gateway, consistent with the reported problem that staff directly expose internal admin dashboards through public VM IPs. The response must satisfy the requirement that authorized clerks must access remotely without public administrative ingress. The design review is over and production introduction is next. Which action is the best fit?
- Add a public allow-all firewall rule with obscured URL paths
- Cut over clerks through IAP and remove public admin access safely
- Put supported admin applications behind Identity-Aware Proxy with appropriate IAM
- Monitor IAP access failures and unexpected direct ingress rules
Explanation
Correct Answer
B:
Cut over clerks through IAP and remove public admin access safely is a controlled means to introduce the approved architecture while meeting the requirement that authorized clerks must access remotely without public administrative ingress. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
Obscure paths do not restrict authenticated administrative access. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that authorized clerks must access remotely without public administrative ingress.
C:
The alternative “Put supported admin applications behind Identity-Aware Proxy with appropriate IAM” describes the chosen design, but not how it is introduced safely. In the reported observation, network scan discovers admin endpoints reachable without identity-aware gateway. The option “Cut over clerks through IAP and remove public admin access safely” instead addresses the requested controlled implementation.
D:
The alternative “Monitor IAP access failures and unexpected direct ingress rules” addresses later monitoring rather than the actual controlled deployment. In the reported observation, network scan discovers admin endpoints reachable without identity-aware gateway. The option “Cut over clerks through IAP and remove public admin access safely” instead addresses the requested controlled implementation.
Question 142
Consider International hotel operator and its reservation mainframe bridge workload. The issue is that reservation jobs on a mainframe call undocumented nightly batch services; the current observation is that discovery captures eleven downstream dependencies absent from design diagrams. The team must ensure that bookings may not be lost during peak holiday weeks. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Build a verified dependency map and define safe migration waves
- Track batch reconciliation, shadow traffic failures and residual dependencies
- Pilot low-risk read features and dual-write reconciliation before reservation cutover
- Design strangler APIs around stable reservation capabilities with coexistence
- Cut all mainframe links on the first deployment without inventory reconciliation
Explanation
Correct Answers
C:
Pilot low-risk read features and dual-write reconciliation before reservation cutover is a controlled means to introduce the approved architecture while meeting the requirement that bookings may not be lost during peak holiday weeks. 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.
D:
Design strangler APIs around stable reservation capabilities with coexistence targets the underlying issue (reservation jobs on a mainframe call undocumented nightly batch services) rather than merely reporting symptoms. It also preserves the required outcome (bookings may not be lost during peak holiday weeks), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
Incorrect Answers
A:
This diagnoses the original issue (reservation jobs on a mainframe call undocumented nightly batch services), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
B:
Monitoring reservation mainframe bridge for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: reservation jobs on a mainframe call undocumented nightly batch services.
E:
A big-bang cutover risks invisible dependencies and lost bookings. The shortcut does not supply the requested design and safe rollout for reservation mainframe bridge, where discovery captures eleven downstream dependencies absent from design diagrams.
Question 143
Emergency response simulation unit plans to update Firestore emulator testing. Investigators found that test activity creates real private user documents, consistent with the reported problem that developers test access rules only against the live production database. The response must satisfy the requirement that simulations must avoid affecting production patient or responder data. The design review is over and production introduction is next. Which action is the best fit?
- Use the Firestore emulator for rules and app integration tests with synthetic data
- Use production service credentials for every local emulator test
- Monitor CI environment variables and accidental production accesses
- Switch CI to emulator endpoints and isolated test projects
Explanation
Correct Answer
D:
Switch CI to emulator endpoints and isolated test projects is a controlled means to introduce the approved architecture while meeting the requirement that simulations must avoid affecting production patient or responder data. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Use the Firestore emulator for rules and app integration tests with synthetic data” describes the chosen design, but not how it is introduced safely. In the reported observation, test activity creates real private user documents. The option “Switch CI to emulator endpoints and isolated test projects” instead addresses the requested controlled implementation.
B:
Production credentials destroy the isolation expected from testing. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that simulations must avoid affecting production patient or responder data.
C:
The alternative “Monitor CI environment variables and accidental production accesses” addresses later monitoring rather than the actual controlled deployment. In the reported observation, test activity creates real private user documents. The option “Switch CI to emulator endpoints and isolated test projects” instead addresses the requested controlled implementation.
Question 144
Financial audit services group plans to update cloud organization inheritance. Investigators found that audit reveals inconsistent permissions across finance subsidiaries, consistent with the reported problem that security administrators grant broad roles directly to each production project. The response must satisfy the requirement that a central security team must enforce boundaries while subsidiaries run their own workloads. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Inspect inherited IAM, folders, project ownership and org policies
- Migrate grants through tested IAM groups and an exception approval window
- Monitor excess privileged grants, org-policy exceptions and IAM drift
- Place business units under governed folders with group-based least privilege and org-level constraints
- Grant Editor to every subsidiary developer on every production project
Explanation
Correct Answers
B:
Migrate grants through tested IAM groups and an exception approval window is a controlled means to introduce the approved architecture while meeting the requirement that a central security team must enforce boundaries while subsidiaries run their own workloads. 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.
D:
Place business units under governed folders with group-based least privilege and org-level constraints targets the underlying issue (security administrators grant broad roles directly to each production project) rather than merely reporting symptoms. It also preserves the required outcome (a central security team must enforce boundaries while subsidiaries run their own workloads), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
Incorrect Answers
A:
This diagnoses the original issue (security administrators grant broad roles directly to each production project), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
C:
Monitoring cloud organization inheritance for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: security administrators grant broad roles directly to each production project.
E:
Broad organization-wide editing violates separation and least privilege. The shortcut does not supply the requested design and safe rollout for cloud organization inheritance, where audit reveals inconsistent permissions across finance subsidiaries.
Question 145
At Clinical AI summarization service, the retrieved prompt injection workload has a documented risk: untrusted patient notes include instructions asking the assistant to email records externally. The review found that red-team canary causes the assistant to propose unauthorized tool calls. The architecture must also ensure that clinical outputs may be viewed, but protected records must never be exported by retrieved text. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Use explicit tool authorization with Model Armor filtering and restricted context grounding
- Map retrieval-to-tool trust boundaries and external tool privileges
- Deploy safe tool policies and adversarial tests before production access
- Treat any instruction inside retrieved notes as an administrator command
Explanation
Correct Answer
B:
Map retrieval-to-tool trust boundaries and external tool privileges is the appropriate diagnostic because the observation—red-team canary causes the assistant to propose unauthorized tool calls—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (untrusted patient notes include instructions asking the assistant to email records externally) before the design is approved.
Incorrect Answers
A:
The alternative “Use explicit tool authorization with Model Armor filtering and restricted context grounding” is target architecture selection; it does not establish why the observed path failed. In the reported observation, red-team canary causes the assistant to propose unauthorized tool calls. The option “Map retrieval-to-tool trust boundaries and external tool privileges” instead addresses the requested root-cause evidence.
C:
The alternative “Deploy safe tool policies and adversarial tests before production access” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, red-team canary causes the assistant to propose unauthorized tool calls. The option “Map retrieval-to-tool trust boundaries and external tool privileges” instead addresses the requested root-cause evidence.
D:
Retrieved patient text is untrusted data, not authorization. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that clinical outputs may be viewed, but protected records must never be exported by retrieved text.
Question 146
Consider Regional airline and its crew roster API workload. The issue is that a database primary restart causes regional crews to lose schedules for an entire shift; the current observation is that failure logs show read-only standby exists but application uses only one endpoint. The team must ensure that dispatch must read the last approved crew plan during recovery. Which acceptance test should demonstrate both protection against the failure and continued authorized service?
- Classify read/write operations, acceptable staleness and failover dependencies
- Stage client reconnection and crew-cache refresh before database switchover
- Force primary failover and verify authorized roster reads within RTO
- Point every client to an unreplicated local file as the only source
Explanation
Correct Answer
C:
Force primary failover and verify authorized roster reads within RTO is a direct acceptance test of the path implicated by failure logs show read-only standby exists but application uses only one endpoint. It checks that the original risk (a database primary restart causes regional crews to lose schedules for an entire shift) has actually been controlled and tests that permitted operations still meet the requirement that dispatch must read the last approved crew plan during recovery.
Incorrect Answers
A:
The alternative “Classify read/write operations, acceptable staleness and failover dependencies” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, failure logs show read-only standby exists but application uses only one endpoint. The option “Force primary failover and verify authorized roster reads within RTO” instead addresses the requested acceptance verification.
B:
The alternative “Stage client reconnection and crew-cache refresh before database switchover” documents change execution but not its operational acceptance result. In the reported observation, failure logs show read-only standby exists but application uses only one endpoint. The option “Force primary failover and verify authorized roster reads within RTO” instead addresses the requested acceptance verification.
D:
An uncontrolled copy can yield inconsistent safety-critical rosters. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that dispatch must read the last approved crew plan during recovery.
Question 147
At Industrial maintenance provider, the equipment-manual visual search workload has a documented risk: staff send photos of parts and want to find matching safety documents. The review found that sample images are noisy while text identifiers are only partly visible. The architecture must also ensure that manual search must not invent equipment safety instructions. Which post-change test most reliably distinguishes a functioning control from a merely successful installation?
- Assess image feature quality, metadata and trusted manual indexing
- Let a generative model invent manufacturer safety procedures without retrieved evidence
- Pilot a small catalog with human review for low-confidence matches
- Compare top-k retrieval against validated part IDs and approved documents
Explanation
Correct Answer
D:
Compare top-k retrieval against validated part IDs and approved documents is a direct acceptance test of the path implicated by sample images are noisy while text identifiers are only partly visible. It checks that the original risk (staff send photos of parts and want to find matching safety documents) has actually been controlled and tests that permitted operations still meet the requirement that manual search must not invent equipment safety instructions.
Incorrect Answers
A:
The alternative “Assess image feature quality, metadata and trusted manual indexing” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, sample images are noisy while text identifiers are only partly visible. The option “Compare top-k retrieval against validated part IDs and approved documents” instead addresses the requested acceptance verification.
B:
Hallucinated safety instructions can create physical risk. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that manual search must not invent equipment safety instructions.
C:
The alternative “Pilot a small catalog with human review for low-confidence matches” documents change execution but not its operational acceptance result. In the reported observation, sample images are noisy while text identifiers are only partly visible. The option “Compare top-k retrieval against validated part IDs and approved documents” instead addresses the requested acceptance verification.
Question 148
Agricultural crop analysis firm plans to update agentic data preparation. Investigators found that pipeline logs show successful jobs produce artifacts from incompatible schema versions, consistent with the reported problem that different dataset formats feed model training but lineage disappears when one parser fails. The response must satisfy the requirement that model decisions must be explainable against source training records. The approved change has been applied. Which validation provides the clearest evidence the original problem is fixed?
- Inspect schema contracts, transformation versions and artifact references
- Let every pipeline step read and overwrite the same unversioned training table
- Stage parser updates through validation and checkpointed pipeline runs
- Replay identical input across pipeline versions and compare provenance and output
Explanation
Correct Answer
D:
Replay identical input across pipeline versions and compare provenance and output is a direct acceptance test of the path implicated by pipeline logs show successful jobs produce artifacts from incompatible schema versions. It checks that the original risk (different dataset formats feed model training but lineage disappears when one parser fails) has actually been controlled and tests that permitted operations still meet the requirement that model decisions must be explainable against source training records.
Incorrect Answers
A:
The alternative “Inspect schema contracts, transformation versions and artifact references” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, pipeline logs show successful jobs produce artifacts from incompatible schema versions. The option “Replay identical input across pipeline versions and compare provenance and output” instead addresses the requested acceptance verification.
B:
Mutable shared state destroys lineage and reproducibility. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that model decisions must be explainable against source training records.
C:
The alternative “Stage parser updates through validation and checkpointed pipeline runs” documents change execution but not its operational acceptance result. In the reported observation, pipeline logs show successful jobs produce artifacts from incompatible schema versions. The option “Replay identical input across pipeline versions and compare provenance and output” instead addresses the requested acceptance verification.
Question 149
Case study: Payments risk laboratory: encryption key governance
Payments risk laboratory relies on encryption key governance to deliver its operational commitments. The current architectural problem is that payment data uses default encryption but contract requires customer control over key rotation. The team has recorded this evidence: key inventory shows provider-managed keys with no customer-managed lifecycle. Any proposed response must preserve the requirement that regulated card records require tracked access and planned key retirement.
Consider Payments risk laboratory and its encryption key governance workload. The issue is that payment data uses default encryption but contract requires customer control over key rotation; the current observation is that key inventory shows provider-managed keys with no customer-managed lifecycle. The team must ensure that regulated card records require tracked access and planned key retirement. Which continuous monitoring approach best reveals recurrence or changing dependencies?
- Place plaintext encryption keys in shared project metadata
- Deny unauthorized decrypt, rotate a key version and verify service continuity
- Choose Cloud KMS CMEK where supported with separated key administrators and encryption users
- Monitor key disable events, grant drift and rotation compliance
Explanation
Correct Answer
D:
Monitor key disable events, grant drift and rotation compliance reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (payment data uses default encryption but contract requires customer control over key rotation) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
Shared metadata does not provide protected KMS custody. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that regulated card records require tracked access and planned key retirement.
B:
The alternative “Deny unauthorized decrypt, rotate a key version and verify service continuity” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, key inventory shows provider-managed keys with no customer-managed lifecycle. The option “Monitor key disable events, grant drift and rotation compliance” instead addresses the requested ongoing operational assurance.
C:
The alternative “Choose Cloud KMS CMEK where supported with separated key administrators and encryption users” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, key inventory shows provider-managed keys with no customer-managed lifecycle. The option “Monitor key disable events, grant drift and rotation compliance” instead addresses the requested ongoing operational assurance.
Question 150
Case study: Medical appointment SaaS: serverless private database access
Medical appointment SaaS relies on serverless private database access to deliver its operational commitments. The current architectural problem is that Cloud Run service has public database IP access though all systems reside in one VPC. The team has recorded this evidence: connection logs show traffic to a globally routable database endpoint. Any proposed response must preserve the requirement that patient database must only accept internal workload connections.
At Medical appointment SaaS, the Google Cloud design for serverless private database access is affected because Cloud Run service has public database IP access though all systems reside in one VPC. A review found that connection logs show traffic to a globally routable database endpoint. The proposed response must account for the requirement that patient database must only accept internal workload connections. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?
- Permit the database to accept all public IPs because TLS is enabled
- Monitor egress routing drift and private connection saturation
- Use Cloud Run VPC egress integration and private database access
- Attempt external database connection and verify only authorized service succeeds
Explanation
Correct Answer
B:
Monitor egress routing drift and private connection saturation reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (Cloud Run service has public database IP access though all systems reside in one VPC) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
TLS does not meet the private reachability requirement. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that patient database must only accept internal workload connections.
C:
The alternative “Use Cloud Run VPC egress integration and private database access” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, connection logs show traffic to a globally routable database endpoint. The option “Monitor egress routing drift and private connection saturation” instead addresses the requested ongoing operational assurance.
D:
The alternative “Attempt external database connection and verify only authorized service succeeds” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, connection logs show traffic to a globally routable database endpoint. The option “Monitor egress routing drift and private connection saturation” instead addresses the requested ongoing operational assurance.