Google Professional Cloud Architect Practice Test 95
Question 940
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.
At Online ticket lottery, the reservation API workload has a documented risk: the planned single service is sized for ordinary traffic but purchases arrive in minute-long surges. The review found that load tests show 40x burst with a limited pool of unique seats. The architecture must also ensure that a seat must not be reserved twice under concurrent requests. What follow-up metric or alert will identify emerging failures after the initial acceptance test?
- Choose elastic stateless entrypoints with atomic reservation storage and admission control
- Simulate 40x competing requests and prove one paid allocation per seat
- Cache seat ownership only in eventually consistent edge storage
- Track queue admission, reservation conflicts and failed checkout rate
Explanation
Correct Answer
D:
Track queue admission, reservation conflicts and failed checkout rate reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (the planned single service is sized for ordinary traffic but purchases arrive in minute-long surges) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Choose elastic stateless entrypoints with atomic reservation storage and admission control” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, load tests show 40x burst with a limited pool of unique seats. The option “Track queue admission, reservation conflicts and failed checkout rate” instead addresses the requested ongoing operational assurance.
B:
The alternative “Simulate 40x competing requests and prove one paid allocation per seat” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, load tests show 40x burst with a limited pool of unique seats. The option “Track queue admission, reservation conflicts and failed checkout rate” instead addresses the requested ongoing operational assurance.
C:
Stale edge ownership cannot prevent double booking. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that a seat must not be reserved twice under concurrent requests.
Question 941
At Retail financial platform, the Google Cloud design for edge web application defense is affected because automated scraping exhausts the app before request processing while legitimate checkout continues. A review found that HTTP logs show one ASN generates most high-rate suspicious requests. The proposed response must account for the requirement that payments require low false-positive blocking and reliable low-latency access. A deployment ticket has been closed. What direct evidence would justify solution signoff?
- Run benign and abusive traffic tests through the load balancer and compare outcomes
- Correlate request properties, attack patterns and genuine customer behavior
- Stage rate rules in preview and ramp enforcement with emergency bypass
- Rely only on a VM host firewall to examine full application-layer request behavior
Explanation
Correct Answer
A:
Run benign and abusive traffic tests through the load balancer and compare outcomes is a direct acceptance test of the path implicated by HTTP logs show one ASN generates most high-rate suspicious requests. It checks that the original risk (automated scraping exhausts the app before request processing while legitimate checkout continues) has actually been controlled and tests that permitted operations still meet the requirement that payments require low false-positive blocking and reliable low-latency access.
Incorrect Answers
B:
The alternative “Correlate request properties, attack patterns and genuine customer behavior” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, HTTP logs show one ASN generates most high-rate suspicious requests. The option “Run benign and abusive traffic tests through the load balancer and compare outcomes” instead addresses the requested acceptance verification.
C:
The alternative “Stage rate rules in preview and ramp enforcement with emergency bypass” documents change execution but not its operational acceptance result. In the reported observation, HTTP logs show one ASN generates most high-rate suspicious requests. The option “Run benign and abusive traffic tests through the load balancer and compare outcomes” instead addresses the requested acceptance verification.
D:
Host-level rules do not provide the same edge application-aware filtering. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that payments require low false-positive blocking and reliable low-latency access.
Question 942
Global pharmacy vendor plans to update private AI endpoint access. Investigators found that network scan finds broad ingress on a model-serving load balancer, consistent with the reported problem that public model endpoints are reachable by unauthorized IPs while containing protected pricing prompts. The response must satisfy the requirement that only corporate approved callers may submit sensitive requests. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?
- Map service callers, endpoint type and private reachability needs
- Migrate known clients to private endpoints and remove public traffic routes
- Use private model-serving access and workload-bound IAM with constrained ingress
- Hide endpoint names in source code but leave public access open
Explanation
Correct Answer
A:
Map service callers, endpoint type and private reachability needs is the appropriate diagnostic because the observation—network scan finds broad ingress on a model-serving load balancer—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (public model endpoints are reachable by unauthorized IPs while containing protected pricing prompts) before the design is approved.
Incorrect Answers
B:
The alternative “Migrate known clients to private endpoints and remove public traffic routes” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, network scan finds broad ingress on a model-serving load balancer. The option “Map service callers, endpoint type and private reachability needs” instead addresses the requested root-cause evidence.
C:
The alternative “Use private model-serving access and workload-bound IAM with constrained ingress” is target architecture selection; it does not establish why the observed path failed. In the reported observation, network scan finds broad ingress on a model-serving load balancer. The option “Map service callers, endpoint type and private reachability needs” instead addresses the requested root-cause evidence.
D:
Obscurity is not an endpoint authorization control. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that only corporate approved callers may submit sensitive requests.
Question 943
Case study: International cinema platform: secure software supply chain
International cinema platform relies on secure software supply chain to deliver its operational commitments. The current architectural problem is that a deployment references mutable container tags from an unaudited third-party registry. The team has recorded this evidence: build provenance report shows tag digest changed after approval. Any proposed response must preserve the requirement that production media services must run only approved signed artifacts.
Consider International cinema platform and its secure software supply chain workload. The issue is that a deployment references mutable container tags from an unaudited third-party registry; the current observation is that build provenance report shows tag digest changed after approval. The team must ensure that production media services must run only approved signed artifacts. The change committee needs to understand the current system rather than install a fix yet. What should it do?
- Canary signed-image enforcement and remove mutable tag assumptions
- Trace build provenance, registry trust and admission permissions
- Use Artifact Registry provenance and Binary Authorization enforcement for approved images
- Allow every external image when its tag says latest-stable
Explanation
Correct Answer
B:
Trace build provenance, registry trust and admission permissions is the appropriate diagnostic because the observation—build provenance report shows tag digest changed after approval—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (a deployment references mutable container tags from an unaudited third-party registry) before the design is approved.
Incorrect Answers
A:
The alternative “Canary signed-image enforcement and remove mutable tag assumptions” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, build provenance report shows tag digest changed after approval. The option “Trace build provenance, registry trust and admission permissions” instead addresses the requested root-cause evidence.
C:
The alternative “Use Artifact Registry provenance and Binary Authorization enforcement for approved images” is target architecture selection; it does not establish why the observed path failed. In the reported observation, build provenance report shows tag digest changed after approval. The option “Trace build provenance, registry trust and admission permissions” instead addresses the requested root-cause evidence.
D:
A mutable tag does not establish artifact authenticity. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that production media services must run only approved signed artifacts.
Question 944
The separation of duties environment at Regional tax administration faces this issue: one engineer both edits production code and approves its own security policy exceptions. Supporting evidence shows that access review shows the same principal has release and audit-admin permissions. The architect must preserve the requirement that regulated changes require an independent approval trail. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Separate release, approval and audit roles with enforceable IAM constraints
- Attempt self-approval and confirm policy blocks it while approved release succeeds
- Monitor break-glass sessions and privilege role conflicts
- Give all developers Owner and rely on an informal promise to avoid self-approval
Explanation
Correct Answer
C:
Monitor break-glass sessions and privilege role conflicts reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (one engineer both edits production code and approves its own security policy exceptions) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Separate release, approval and audit roles with enforceable IAM constraints” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, access review shows the same principal has release and audit-admin permissions. The option “Monitor break-glass sessions and privilege role conflicts” instead addresses the requested ongoing operational assurance.
B:
The alternative “Attempt self-approval and confirm policy blocks it while approved release succeeds” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, access review shows the same principal has release and audit-admin permissions. The option “Monitor break-glass sessions and privilege role conflicts” instead addresses the requested ongoing operational assurance.
D:
An informal promise cannot enforce role separation. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that regulated changes require an independent approval trail.
Question 945
At Regional airline booking platform, the Apigee API consumer management workload has a documented risk: travel agencies call the same reservation endpoint with no consumer-specific quota. The review found that gateway logs show one agency's retry loop overwhelms others. The architecture must also ensure that partners need predictable access without shutting down public bookings. What follow-up metric or alert will identify emerging failures after the initial acceptance test?
- Track per-client quota hits and anomalous retry behavior
- Apply one secret shared by every travel agency with no rate controls
- Simulate an agency retry storm and verify unrelated agencies retain throughput
- Design Apigee API products with per-consumer credentials, quotas and analytics
Explanation
Correct Answer
A:
Track per-client quota hits and anomalous retry behavior reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (travel agencies call the same reservation endpoint with no consumer-specific quota) rather than treating the first successful test as permanent assurance.
Incorrect Answers
B:
Shared identity and unrestricted rate make abusive tenants unaccountable. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that partners need predictable access without shutting down public bookings.
C:
The alternative “Simulate an agency retry storm and verify unrelated agencies retain throughput” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, gateway logs show one agency's retry loop overwhelms others. The option “Track per-client quota hits and anomalous retry behavior” instead addresses the requested ongoing operational assurance.
D:
The alternative “Design Apigee API products with per-consumer credentials, quotas and analytics” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, gateway logs show one agency's retry loop overwhelms others. The option “Track per-client quota hits and anomalous retry behavior” instead addresses the requested ongoing operational assurance.
Question 946
At Airport luggage services, the Google Cloud design for service catalog onboarding is affected because new teams ask for databases by email and receive unrestricted project ownership. A review found that tickets show inconsistent machine sizing and missing application tags. The proposed response must account for the requirement that every project needs approved cost and access boundaries. Which controlled implementation should be used to preserve operational continuity during the change?
- Define self-service catalog templates with IAM and budget constraints
- Launch approved Terraform-backed catalog items for pilot teams
- Continue granting project Owner for all simple database requests
- Monitor template drift and manual overrides
Explanation
Correct Answer
B:
Launch approved Terraform-backed catalog items for pilot teams is a controlled means to introduce the approved architecture while meeting the requirement that every project needs approved cost and access boundaries. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Define self-service catalog templates with IAM and budget constraints” describes the chosen design, but not how it is introduced safely. In the reported observation, tickets show inconsistent machine sizing and missing application tags. The option “Launch approved Terraform-backed catalog items for pilot teams” instead addresses the requested controlled implementation.
C:
Broad manual grants defeat governed repeatability. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that every project needs approved cost and access boundaries.
D:
The alternative “Monitor template drift and manual overrides” addresses later monitoring rather than the actual controlled deployment. In the reported observation, tickets show inconsistent machine sizing and missing application tags. The option “Launch approved Terraform-backed catalog items for pilot teams” instead addresses the requested controlled implementation.
Question 947
Case study: Rural health provider: patient appointment API
Rural health provider relies on patient appointment API to deliver its operational commitments. The current architectural problem is that one-zone hosting meets average latency but fails an entire zone test. The team has recorded this evidence: chaos test stops a zone and all appointment writes fail. Any proposed response must preserve the requirement that emergency scheduling must recover within five minutes without lost confirmations.
At Rural health provider, the patient appointment API workload has a documented risk: one-zone hosting meets average latency but fails an entire zone test. The review found that chaos test stops a zone and all appointment writes fail. The architecture must also ensure that emergency scheduling must recover within five minutes without lost confirmations. Which post-change test most reliably distinguishes a functioning control from a merely successful installation?
- Fail a zone and verify scheduling recovery and committed appointments within target
- Roll out across zones with controlled DNS and session transition
- Add a larger instance to the same zone and call it disaster recovery
- Measure present zone dependencies, RTO/RPO and database write consistency
Explanation
Correct Answer
A:
Fail a zone and verify scheduling recovery and committed appointments within target is a direct acceptance test of the path implicated by chaos test stops a zone and all appointment writes fail. It checks that the original risk (one-zone hosting meets average latency but fails an entire zone test) has actually been controlled and tests that permitted operations still meet the requirement that emergency scheduling must recover within five minutes without lost confirmations.
Incorrect Answers
B:
The alternative “Roll out across zones with controlled DNS and session transition” documents change execution but not its operational acceptance result. In the reported observation, chaos test stops a zone and all appointment writes fail. The option “Fail a zone and verify scheduling recovery and committed appointments within target” instead addresses the requested acceptance verification.
C:
Vertical scaling does not survive loss of an entire zone. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that emergency scheduling must recover within five minutes without lost confirmations.
D:
The alternative “Measure present zone dependencies, RTO/RPO and database write consistency” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, chaos test stops a zone and all appointment writes fail. The option “Fail a zone and verify scheduling recovery and committed appointments within target” instead addresses the requested acceptance verification.
Question 948
At Online grocery delivery, the Google Cloud design for feature KPI design is affected because migration success is defined as number of VMs shut down while delivery failures increase. A review found that business dashboards show missed deliveries after new routing service launch. The proposed response must account for the requirement that the program must improve delivered-order reliability, not just infrastructure count. Which controlled implementation should be used to preserve operational continuity during the change?
- Define shared availability, on-time-delivery and cost-per-delivery KPIs
- Introduce metrics dashboards with business owners and stable baselines
- Call the project successful solely because the cloud invoice fell
- Track on-time rate, order cancellations and unit economics
Explanation
Correct Answer
B:
Introduce metrics dashboards with business owners and stable baselines is a controlled means to introduce the approved architecture while meeting the requirement that the program must improve delivered-order reliability, not just infrastructure count. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Define shared availability, on-time-delivery and cost-per-delivery KPIs” describes the chosen design, but not how it is introduced safely. In the reported observation, business dashboards show missed deliveries after new routing service launch. The option “Introduce metrics dashboards with business owners and stable baselines” instead addresses the requested controlled implementation.
C:
Lower spend can accompany worse business performance. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that the program must improve delivered-order reliability, not just infrastructure count.
D:
The alternative “Track on-time rate, order cancellations and unit economics” addresses later monitoring rather than the actual controlled deployment. In the reported observation, business dashboards show missed deliveries after new routing service launch. The option “Introduce metrics dashboards with business owners and stable baselines” instead addresses the requested controlled implementation.
Question 949
Case study: Streaming fitness platform: event analytics ingestion
Streaming fitness platform relies on event analytics ingestion to deliver its operational commitments. The current architectural problem is that incoming device events arrive late and in duplicates and dashboards need windows. The team has recorded this evidence: sample payloads show device clocks skew ten minutes across regions. Any proposed response must preserve the requirement that analytics should not interfere with real-time device safety controls.
At Streaming fitness platform, the event analytics ingestion workload has a documented risk: incoming device events arrive late and in duplicates and dashboards need windows. The review found that sample payloads show device clocks skew ten minutes across regions. The architecture must also ensure that analytics should not interfere with real-time device safety controls. Which post-change test most reliably distinguishes a functioning control from a merely successful installation?
- Roll out schema-versioned consumers with dead-letter handling
- Use request arrival timestamps as ground truth without clock handling
- Inspect event-time semantics, watermark lateness and replay handling
- Inject late and duplicate device events and check window aggregates
Explanation
Correct Answer
D:
Inject late and duplicate device events and check window aggregates is a direct acceptance test of the path implicated by sample payloads show device clocks skew ten minutes across regions. It checks that the original risk (incoming device events arrive late and in duplicates and dashboards need windows) has actually been controlled and tests that permitted operations still meet the requirement that analytics should not interfere with real-time device safety controls.
Incorrect Answers
A:
The alternative “Roll out schema-versioned consumers with dead-letter handling” documents change execution but not its operational acceptance result. In the reported observation, sample payloads show device clocks skew ten minutes across regions. The option “Inject late and duplicate device events and check window aggregates” instead addresses the requested acceptance verification.
B:
Arrival time alone distorts late-event analytics. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that analytics should not interfere with real-time device safety controls.
C:
The alternative “Inspect event-time semantics, watermark lateness and replay handling” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, sample payloads show device clocks skew ten minutes across regions. The option “Inject late and duplicate device events and check window aggregates” instead addresses the requested acceptance verification.
Question 950
Consider University financial aid and its support access audit workload. The issue is that a troubleshooting engineer needs to inspect errors but receives project Owner privileges; the current observation is that permission request includes unnecessary user data access. The team must ensure that incident support must follow least privilege and logged access. Which continuous monitoring approach best reveals recurrence or changing dependencies?
- Watch stale support grants and unauthorized data reads
- Create scoped temporary diagnostic roles and privileged session recording
- Give all temporary support contractors permanent Owner access
- Attempt an unrelated data export with diagnostic role and verify denial
Explanation
Correct Answer
A:
Watch stale support grants and unauthorized data reads reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a troubleshooting engineer needs to inspect errors but receives project Owner privileges) rather than treating the first successful test as permanent assurance.
Incorrect Answers
B:
The alternative “Create scoped temporary diagnostic roles and privileged session recording” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, permission request includes unnecessary user data access. The option “Watch stale support grants and unauthorized data reads” instead addresses the requested ongoing operational assurance.
C:
Permanent broad privileges are not justified by a narrow debugging need. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that incident support must follow least privilege and logged access.
D:
The alternative “Attempt an unrelated data export with diagnostic role and verify denial” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, permission request includes unnecessary user data access. The option “Watch stale support grants and unauthorized data reads” instead addresses the requested ongoing operational assurance.