Google Professional Cloud Architect Practice Test 51
Question 500
At Wildlife conservation nonprofit, the field-research collection workload has a documented risk: donor funding requires an inexpensive platform but volunteers collect sensitive species locations. The review found that team interviews identify intermittent connectivity and controlled-location access. The architecture must also ensure that precise nesting coordinates must remain inaccessible to public donors. 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 stale devices, data-sharing grants and synchronization conflicts
- Validate conflicting offline edits and confirm public reports cannot expose nest coordinates
- Classify location sensitivity, offline sync needs, donation objectives and cost boundaries
- Accept the deployment ticket as proof that the control has no remaining security or availability risk
- Publish exact endangered-species coordinates to prove collection completeness
- Use offline-capable mobile capture with encrypted private storage and aggregated donor reports
Explanation
Correct Answers
A:
Watch stale devices, data-sharing grants and synchronization conflicts reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (donor funding requires an inexpensive platform but volunteers collect sensitive species locations) rather than treating the first successful test as permanent assurance. It supplies the ongoing observation requested.
B:
Validate conflicting offline edits and confirm public reports cannot expose nest coordinates is a direct acceptance test of the path implicated by team interviews identify intermittent connectivity and controlled-location access. It checks that the original risk (donor funding requires an inexpensive platform but volunteers collect sensitive species locations) has actually been controlled and tests that permitted operations still meet the requirement that precise nesting coordinates must remain inaccessible to public donors. It supplies the separate post-change acceptance result requested.
C:
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. It supplies the pre-design diagnostic evidence requested.
Incorrect Answers
D:
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: team interviews identify intermittent connectivity and controlled-location access.
E:
Sensitive location disclosure could enable poaching and defeat privacy requirements. It cannot satisfy the required evidence stages.
F:
Designing field-research collection addresses the root cause, but this specific three-part question asks for evidence to diagnose, accept and continuously verify the response to donor funding requires an inexpensive platform but volunteers collect sensitive species locations, not another design proposal.
Question 501
Consider National energy research agency and its customer-held encryption custody workload. The issue is that key users and key administrators are the same operational group; the current observation is that IAM audit finds anyone who deploys workloads can disable and destroy keys. The team must ensure that regulatory continuity requires separate key destruction approval. The change committee needs to understand the current system rather than install a fix yet. What should it do?
- Split Cloud KMS key-admin and cryptographic-use roles with protected approval flow
- Grant cryptoKeyAdmin to every application service account
- Migrate grants while maintaining service cryptographic access
- Analyze who can encrypt, decrypt, rotate, disable and schedule destruction
Explanation
Correct Answer
D:
Analyze who can encrypt, decrypt, rotate, disable and schedule destruction is the appropriate diagnostic because the observation—IAM audit finds anyone who deploys workloads can disable and destroy keys—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (key users and key administrators are the same operational group) before the design is approved.
Incorrect Answers
A:
The alternative “Split Cloud KMS key-admin and cryptographic-use roles with protected approval flow” is target architecture selection; it does not establish why the observed path failed. In the reported observation, IAM audit finds anyone who deploys workloads can disable and destroy keys. The option “Analyze who can encrypt, decrypt, rotate, disable and schedule destruction” instead addresses the requested root-cause evidence.
B:
Applications do not need key lifecycle destruction authority. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that regulatory continuity requires separate key destruction approval.
C:
The alternative “Migrate grants while maintaining service cryptographic access” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, IAM audit finds anyone who deploys workloads can disable and destroy keys. The option “Analyze who can encrypt, decrypt, rotate, disable and schedule destruction” instead addresses the requested root-cause evidence.
Question 502
Consider Clinical AI summarization service and its retrieved prompt injection workload. The issue is that untrusted patient notes include instructions asking the assistant to email records externally; the current observation is that red-team canary causes the assistant to propose unauthorized tool calls. The team must ensure that clinical outputs may be viewed, but protected records must never be exported by retrieved text. Which acceptance test should demonstrate both protection against the failure and continued authorized service?
- Inject malicious retrieved notes and confirm no unauthorized data export executes
- 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
A:
Inject malicious retrieved notes and confirm no unauthorized data export executes is a direct acceptance test of the path implicated by red-team canary causes the assistant to propose unauthorized tool calls. It checks that the original risk (untrusted patient notes include instructions asking the assistant to email records externally) has actually been controlled and tests that permitted operations still meet the requirement that clinical outputs may be viewed, but protected records must never be exported by retrieved text.
Incorrect Answers
B:
The alternative “Map retrieval-to-tool trust boundaries and external tool privileges” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, red-team canary causes the assistant to propose unauthorized tool calls. The option “Inject malicious retrieved notes and confirm no unauthorized data export executes” instead addresses the requested acceptance verification.
C:
The alternative “Deploy safe tool policies and adversarial tests before production access” documents change execution but not its operational acceptance result. In the reported observation, red-team canary causes the assistant to propose unauthorized tool calls. The option “Inject malicious retrieved notes and confirm no unauthorized data export executes” instead addresses the requested acceptance verification.
D:
Retrieved patient text is untrusted data, not authorization. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that clinical outputs may be viewed, but protected records must never be exported by retrieved text.
Question 503
Case study: Global coffee chain: Cloud Logging retention
Global coffee chain relies on Cloud Logging retention to deliver its operational commitments. The current architectural problem is that project logs disappear after 30 days but fraud investigations extend six months. The team has recorded this evidence: retention check shows no archived log bucket for point-of-sale events. Any proposed response must preserve the requirement that fraud evidence must be retrievable under restricted access.
At Global coffee chain, the Cloud Logging retention workload has a documented risk: project logs disappear after 30 days but fraud investigations extend six months. The review found that retention check shows no archived log bucket for point-of-sale events. The architecture must also ensure that fraud evidence must be retrievable under restricted access. What follow-up metric or alert will identify emerging failures after the initial acceptance test?
- Retrieve an older synthetic fraud event and confirm its integrity
- Monitor sink health, retention policy drift and archive retrieval
- Rely only on application console scrollback as the audit archive
- Use suitable log buckets/sinks with governed retention and protected access
Explanation
Correct Answer
B:
Monitor sink health, retention policy drift and archive retrieval reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (project logs disappear after 30 days but fraud investigations extend six months) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Retrieve an older synthetic fraud event and confirm its integrity” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, retention check shows no archived log bucket for point-of-sale events. The option “Monitor sink health, retention policy drift and archive retrieval” instead addresses the requested ongoing operational assurance.
C:
Transient console views do not meet retention and integrity needs. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that fraud evidence must be retrievable under restricted access.
D:
The alternative “Use suitable log buckets/sinks with governed retention and protected access” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, retention check shows no archived log bucket for point-of-sale events. The option “Monitor sink health, retention policy drift and archive retrieval” instead addresses the requested ongoing operational assurance.
Question 504
The private research assistant environment at Regional financial adviser faces this issue: employees want document-grounded answers without granting a chatbot access to privileged trading APIs. Supporting evidence shows that demo agent follows instructions embedded in retrieved research PDFs. The architect must preserve the requirement that approved internal reports must be cited and trading authorization separate. Which migration or rollout step best manages risk, dependencies and reversibility?
- Ground answers in vetted enterprise search and isolate actions behind explicit identity checks
- Introduce approved corpus sources with prompt-injection tests and read-only permissions
- Treat every retrieved document as an instruction from the security administrator
- Watch tool-denial logs, citation fidelity and document-access grants
Explanation
Correct Answer
B:
Introduce approved corpus sources with prompt-injection tests and read-only permissions is a controlled means to introduce the approved architecture while meeting the requirement that approved internal reports must be cited and trading authorization separate. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Ground answers in vetted enterprise search and isolate actions behind explicit identity checks” describes the chosen design, but not how it is introduced safely. In the reported observation, demo agent follows instructions embedded in retrieved research PDFs. The option “Introduce approved corpus sources with prompt-injection tests and read-only permissions” instead addresses the requested controlled implementation.
C:
Untrusted document content cannot grant privileged tool authority. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that approved internal reports must be cited and trading authorization separate.
D:
The alternative “Watch tool-denial logs, citation fidelity and document-access grants” addresses later monitoring rather than the actual controlled deployment. In the reported observation, demo agent follows instructions embedded in retrieved research PDFs. The option “Introduce approved corpus sources with prompt-injection tests and read-only permissions” instead addresses the requested controlled implementation.
Question 505
At Hospital imaging research unit, the regulated data classification workload has a documented risk: an AI training workflow ingests medical reports with accidental patient identifiers. The review found that dataset profiler finds patient IDs inside free-text radiology comments. The architecture must also ensure that only approved deidentified inputs may enter model training. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Use Sensitive Data Protection inspection/deidentification with governance controls
- Classify identifiable fields and exposure paths with sample inspections
- Insert deidentification before training and quarantine unresolved findings
- Trust a generic prompt to remove every patient ID from raw input
Explanation
Correct Answer
B:
Classify identifiable fields and exposure paths with sample inspections is the appropriate diagnostic because the observation—dataset profiler finds patient IDs inside free-text radiology comments—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (an AI training workflow ingests medical reports with accidental patient identifiers) before the design is approved.
Incorrect Answers
A:
The alternative “Use Sensitive Data Protection inspection/deidentification with governance controls” is target architecture selection; it does not establish why the observed path failed. In the reported observation, dataset profiler finds patient IDs inside free-text radiology comments. The option “Classify identifiable fields and exposure paths with sample inspections” instead addresses the requested root-cause evidence.
C:
The alternative “Insert deidentification before training and quarantine unresolved findings” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, dataset profiler finds patient IDs inside free-text radiology comments. The option “Classify identifiable fields and exposure paths with sample inspections” instead addresses the requested root-cause evidence.
D:
Prompt guidance is not a deterministic privacy-control boundary. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that only approved deidentified inputs may enter model training.
Question 506
Case study: National utility network: Terraform state protection
National utility network relies on Terraform state protection to deliver its operational commitments. The current architectural problem is that team stores Terraform state publicly in a source repository with embedded secrets. The team has recorded this evidence: security scan detects database credentials and sensitive IP inventory in state. Any proposed response must preserve the requirement that all state edits require audited locking and backup.
At National utility network, the Terraform state protection workload has a documented risk: team stores Terraform state publicly in a source repository with embedded secrets. The review found that security scan detects database credentials and sensitive IP inventory in state. The architecture must also ensure that all state edits require audited locking and backup. Which post-change test most reliably distinguishes a functioning control from a merely successful installation?
- Place the same state JSON in a publicly readable object bucket
- Run concurrent planned applies and verify state consistency and access denial
- Locate state secrets, writer permissions and concurrent execution hazards
- Migrate state to restricted storage and rotate any exposed secrets
Explanation
Correct Answer
B:
Run concurrent planned applies and verify state consistency and access denial is a direct acceptance test of the path implicated by security scan detects database credentials and sensitive IP inventory in state. It checks that the original risk (team stores Terraform state publicly in a source repository with embedded secrets) has actually been controlled and tests that permitted operations still meet the requirement that all state edits require audited locking and backup.
Incorrect Answers
A:
Public state exposes sensitive configuration and cannot enforce controlled locking. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that all state edits require audited locking and backup.
C:
The alternative “Locate state secrets, writer permissions and concurrent execution hazards” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, security scan detects database credentials and sensitive IP inventory in state. The option “Run concurrent planned applies and verify state consistency and access denial” instead addresses the requested acceptance verification.
D:
The alternative “Migrate state to restricted storage and rotate any exposed secrets” documents change execution but not its operational acceptance result. In the reported observation, security scan detects database credentials and sensitive IP inventory in state. The option “Run concurrent planned applies and verify state consistency and access denial” instead addresses the requested acceptance verification.
Question 507
Case study: Online ticket lottery: reservation API
Online ticket lottery relies on reservation API to deliver its operational commitments. The current architectural problem is that the planned single service is sized for ordinary traffic but purchases arrive in minute-long surges. The team has recorded this evidence: load tests show 40x burst with a limited pool of unique seats. Any proposed response must preserve the requirement that a seat must not be reserved twice under concurrent requests.
Online ticket lottery plans to update reservation API. Investigators found that load tests show 40x burst with a limited pool of unique seats, consistent with the reported problem that the planned single service is sized for ordinary traffic but purchases arrive in minute-long surges. The response must satisfy the requirement that a seat must not be reserved twice under concurrent requests. Which target-state design is best justified by the evidence and required business outcome?
- Cache seat ownership only in eventually consistent edge storage
- Choose elastic stateless entrypoints with atomic reservation storage and admission control
- Measure burst concurrency, lock contention and reservation expiry windows
- Track queue admission, reservation conflicts and failed checkout rate
Explanation
Correct Answer
B:
Choose elastic stateless entrypoints with atomic reservation storage and admission control targets the underlying issue (the planned single service is sized for ordinary traffic but purchases arrive in minute-long surges) rather than merely reporting symptoms. It also preserves the required outcome (a seat must not be reserved twice under concurrent requests), which a target-state design must satisfy.
Incorrect Answers
A:
Stale edge ownership cannot prevent double booking. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that a seat must not be reserved twice under concurrent requests.
C:
The alternative “Measure burst concurrency, lock contention and reservation expiry windows” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, load tests show 40x burst with a limited pool of unique seats. The option “Choose elastic stateless entrypoints with atomic reservation storage and admission control” instead addresses the requested architecture selection.
D:
The alternative “Track queue admission, reservation conflicts and failed checkout rate” measures results without defining the preventive design now required. In the reported observation, load tests show 40x burst with a limited pool of unique seats. The option “Choose elastic stateless entrypoints with atomic reservation storage and admission control” instead addresses the requested architecture selection.
Question 508
Case study: International bank holding company: regulated data-center extension
International bank holding company relies on regulated data-center extension to deliver its operational commitments. The current architectural problem is that the proposed Dedicated Interconnect lacks a backup location and depends on a single metro facility. The team has recorded this evidence: site survey lists one colocation provider and a common power feed for both links. Any proposed response must preserve the requirement that settlement services require redundant connectivity with predictable private latency.
Consider International bank holding company and its regulated data-center extension workload. The issue is that the proposed Dedicated Interconnect lacks a backup location and depends on a single metro facility; the current observation is that site survey lists one colocation provider and a common power feed for both links. The team must ensure that settlement services require redundant connectivity with predictable private latency. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Coordinate circuit turn-up and route preference in staged change windows
- Install two ports in the same rack and call them regionally redundant
- Analyze metro failure domains, routing owners and throughput commitments
- Design geographically separated Interconnect circuits with independent BGP sessions and failover
- Track circuit utilization, BGP flaps and SLA breaches
Explanation
Correct Answers
A:
Coordinate circuit turn-up and route preference in staged change windows is a controlled means to introduce the approved architecture while meeting the requirement that settlement services require redundant connectivity with predictable private latency. 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 geographically separated Interconnect circuits with independent BGP sessions and failover targets the underlying issue (the proposed Dedicated Interconnect lacks a backup location and depends on a single metro facility) rather than merely reporting symptoms. It also preserves the required outcome (settlement services require redundant connectivity with predictable private latency), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
Incorrect Answers
B:
Common power and facility dependencies defeat geographic resilience. The shortcut does not supply the requested design and safe rollout for regulated data-center extension, where site survey lists one colocation provider and a common power feed for both links.
C:
This diagnoses the original issue (the proposed Dedicated Interconnect lacks a backup location and depends on a single metro facility), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
E:
Monitoring regulated data-center extension for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: the proposed Dedicated Interconnect lacks a backup location and depends on a single metro facility.
Question 509
Case study: Regional transport network: low-latency dispatch API
Regional transport network relies on low-latency dispatch API to deliver its operational commitments. The current architectural problem is that dispatch requests cross the internet to an API hosted in another region. The team has recorded this evidence: flow logs show round trips go through a centralized NAT despite local backends. Any proposed response must preserve the requirement that private dispatch callers require restricted routing and prompt responses.
Consider Regional transport network and its low-latency dispatch API workload. The issue is that dispatch requests cross the internet to an API hosted in another region; the current observation is that flow logs show round trips go through a centralized NAT despite local backends. The team must ensure that private dispatch callers require restricted routing and prompt responses. 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?
- Monitor backend health, route changes and private latency
- Accept the deployment ticket as proof that the control has no remaining security or availability risk
- Put a public forwarding rule on every internal backend for simplicity
- Probe regional calls and reject unintended public egress paths
- Inspect hybrid route tables, peering limitations and service DNS
- Choose regional internal load balancing and private connectivity paths
Explanation
Correct Answers
A:
Monitor backend health, route changes and private latency reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (dispatch requests cross the internet to an API hosted in another region) rather than treating the first successful test as permanent assurance. It supplies the ongoing observation requested.
D:
Probe regional calls and reject unintended public egress paths is a direct acceptance test of the path implicated by flow logs show round trips go through a centralized NAT despite local backends. It checks that the original risk (dispatch requests cross the internet to an API hosted in another region) has actually been controlled and tests that permitted operations still meet the requirement that private dispatch callers require restricted routing and prompt responses. It supplies the separate post-change acceptance result requested.
E:
Inspect hybrid route tables, peering limitations and service DNS is the appropriate diagnostic because the observation—flow logs show round trips go through a centralized NAT despite local backends—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (dispatch requests cross the internet to an API hosted in another region) before the design is approved. It supplies the pre-design diagnostic evidence requested.
Incorrect Answers
B:
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: flow logs show round trips go through a centralized NAT despite local backends.
C:
Public ingress violates the explicit private dispatch boundary. It cannot satisfy the required evidence stages.
F:
Designing low-latency dispatch API addresses the root cause, but this specific three-part question asks for evidence to diagnose, accept and continuously verify the response to dispatch requests cross the internet to an API hosted in another region, not another design proposal.
Question 510
Consider Regional newspaper platform and its automated infrastructure catalog workload. The issue is that each team manually creates different VM images for the same application tier; the current observation is that asset review shows inconsistent IAM, patch settings and logging between regions. The team must ensure that new sites must have consistent repeatable baseline controls. Which continuous monitoring approach best reveals recurrence or changing dependencies?
- Rebuild a test environment and compare deployed policy to approved baseline
- Monitor module drift, change approvals and obsolete versions
- Let each engineer edit production resources manually without recording changes
- Publish reusable Terraform modules with policy tests and documented ownership
Explanation
Correct Answer
B:
Monitor module drift, change approvals and obsolete versions reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (each team manually creates different VM images for the same application tier) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Rebuild a test environment and compare deployed policy to approved baseline” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, asset review shows inconsistent IAM, patch settings and logging between regions. The option “Monitor module drift, change approvals and obsolete versions” instead addresses the requested ongoing operational assurance.
C:
Manual one-off changes are hard to reproduce or audit. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that new sites must have consistent repeatable baseline controls.
D:
The alternative “Publish reusable Terraform modules with policy tests and documented ownership” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, asset review shows inconsistent IAM, patch settings and logging between regions. The option “Monitor module drift, change approvals and obsolete versions” instead addresses the requested ongoing operational assurance.