100% Latest & Updated Google Professional Cloud Architect Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 20
A payment processor demands recovery of its customer authorization API within 20 minutes after a full regional disruption. Which operational action best maintains keeping failover viable as releases change after launch?
- Keep the recovery architecture frozen after major application releases
- Review recovery incidents only after customer complaints
- Exercise recovery regularly and update runbooks with actual recovery timings
- Track backup spend instead of recovery durations
Explanation
Correct Answer
C:Recurring tests detect drift between documented recovery plans and deployed dependencies
Incorrect Answers
A:New dependencies may break old plans. Recurring tests detect drift between documented recovery plans and deployed dependencies.
B:Misses proactively detected drift. Recurring tests detect drift between documented recovery plans and deployed dependencies.
D:Cost alone does not establish RTO readiness. Recurring tests detect drift between documented recovery plans and deployed dependencies.
Question 21
A logistics broker must accept shipment-status updates from many independent partner systems with inconsistent retry schedules. Which architecture most directly meets the need for an ingestion contract resilient to partner retries?
- Expose a validated API contract and buffer accepted events through Pub/Sub
- Call every partner synchronously from the customer-facing order API
- Store inbound updates only in each ephemeral app process
- Accept free-form partner payloads without schema validation
Explanation
Correct Answer
A:Decoupling request receipt from downstream processing limits partner retry amplification
Incorrect Answers
B:Unreliable clients can hold the request open. Decoupling request receipt from downstream processing limits partner retry amplification.
C:Restart loses unprocessed data. Decoupling request receipt from downstream processing limits partner retry amplification.
D:Malformed events cannot be processed consistently. Decoupling request receipt from downstream processing limits partner retry amplification.
Question 22
A logistics broker must accept shipment-status updates from many independent partner systems with inconsistent retry schedules. Which implementation choice most directly delivers duplicate-safe ingestion?
- Assign partner event identifiers and enforce idempotent downstream state transitions
- Use partner timestamps alone as deduplication keys
- Permit consumers to process each delivery with an unconditional insert
- Discard temporarily unprocessable shipment updates after one retry
Explanation
Correct Answer
A:Retries must not create repeated shipment milestones or duplicate invoicing
Incorrect Answers
B:Colliding timestamps may represent separate updates. Retries must not create repeated shipment milestones or duplicate invoicing.
C:Redelivery can create repeated business records. Retries must not create repeated shipment milestones or duplicate invoicing.
D:Transient outages cause incomplete shipment timelines. Retries must not create repeated shipment milestones or duplicate invoicing.
Question 23
A logistics broker must accept shipment-status updates from many independent partner systems with inconsistent retry schedules. Which validation would best establish correctness of end-to-end partner processing?
- Check a single happy-path partner upload
- Monitor queue throughput without reconciling shipment state
- Verify API certificates but never replay updates
- Inject duplicates and delayed events and reconcile final shipment milestones
Explanation
Correct Answer
D:A passing HTTP status does not prove the downstream shipment sequence is consistent
Incorrect Answers
A:Does not test out-of-order events. A passing HTTP status does not prove the downstream shipment sequence is consistent.
B:High processing rate can hide duplicated milestones. A passing HTTP status does not prove the downstream shipment sequence is consistent.
C:Transport security does not establish delivery semantics. A passing HTTP status does not prove the downstream shipment sequence is consistent.
Question 24
A logistics broker must accept shipment-status updates from many independent partner systems with inconsistent retry schedules. Which operational action best maintains partner failure recovery after launch?
- Delete malformed payloads immediately without a recoverable record
- Raise API timeouts and leave backlogs unobserved
- Report only request-volume totals to partners
- Monitor ingestion backlogs and isolate malformed partner payloads for replay
Explanation
Correct Answer
D:Backlog and dead-letter visibility makes delivery failures actionable without dropping accepted events
Incorrect Answers
A:Loses context for correction and replay. Backlog and dead-letter visibility makes delivery failures actionable without dropping accepted events.
B:Does not expose delayed subscriber processing. Backlog and dead-letter visibility makes delivery failures actionable without dropping accepted events.
C:Provides no visibility into milestones lost downstream. Backlog and dead-letter visibility makes delivery failures actionable without dropping accepted events.
Question 25
A customer-facing API has a strict 99.95% SLO and must continue serving after a single zone becomes unavailable. Which architecture most directly meets the need for zonal failure tolerance?
- Deploy redundant serving capacity across zones behind an appropriate load balancer
- Run the API entirely in one zone with multiple replicas
- Replicate static objects across regions while the API remains single-zone
- Rely on manual rebuild after a zone fails
Explanation
Correct Answer
A:Independent zonal capacity avoids making one zone the only point of service
Incorrect Answers
B:A zonal outage still removes all capacity. Independent zonal capacity avoids making one zone the only point of service.
C:Object replication does not protect the running service. Independent zonal capacity avoids making one zone the only point of service.
D:User-facing availability would depend on slow intervention. Independent zonal capacity avoids making one zone the only point of service.
Question 26
A customer-facing API has a strict 99.95% SLO and must continue serving after a single zone becomes unavailable. Which implementation choice most directly delivers zonal recovery implementation?
- Route traffic to unhealthy instances because they remain registered
- Create a second zone but allocate insufficient serving capacity
- Disable autoscaling during a failure to prevent cost fluctuations
- Configure health checks and autoscaling policies on the redundant serving groups
Explanation
Correct Answer
D:Health-directed traffic and spare capacity are necessary for a zone-loss scenario
Incorrect Answers
A:Fails to isolate unavailable capacity. Health-directed traffic and spare capacity are necessary for a zone-loss scenario.
B:Alternate placement without capacity may still breach the SLO. Health-directed traffic and spare capacity are necessary for a zone-loss scenario.
C:Does not address the surge on surviving zones. Health-directed traffic and spare capacity are necessary for a zone-loss scenario.
Question 27
A customer-facing API has a strict 99.95% SLO and must continue serving after a single zone becomes unavailable. Which validation would best establish actual SLO resilience?
- Disable a serving zone during a load test and measure successful user requests
- Inspect healthy instance counts during normal conditions
- Measure only average CPU utilization across zones
- Verify backup files exist but do not invoke the API
Explanation
Correct Answer
A:A failover test measures the user-facing service rather than merely instance health
Incorrect Answers
B:Does not test behavior when a zone disappears. A failover test measures the user-facing service rather than merely instance health.
C:Does not establish request success or latency. A failover test measures the user-facing service rather than merely instance health.
D:Storage recovery evidence is not user-facing SLO evidence. A failover test measures the user-facing service rather than merely instance health.
Question 28
A customer-facing API has a strict 99.95% SLO and must continue serving after a single zone becomes unavailable. Which operational action best maintains operational SLO enforcement after launch?
- Alert only when all application VMs have stopped
- Monitor burn rate against the request-based availability SLO and page on actionable windows
- Page for every one-off successful health-check timeout
- Use monthly availability reports as the only operational detector
Explanation
Correct Answer
B:Error-budget burn alerts reveal sustained reliability risk earlier than uptime snapshots
Incorrect Answers
A:Misses significant customer error-budget burn. Error-budget burn alerts reveal sustained reliability risk earlier than uptime snapshots.
C:Creates noise without actionable sustained signal. Error-budget burn alerts reveal sustained reliability risk earlier than uptime snapshots.
D:Reacts after the incident window closes. Error-budget burn alerts reveal sustained reliability risk earlier than uptime snapshots.
Question 29
A public image catalog serves millions of geographically dispersed viewers and origin latency drives poor page responsiveness. Which architecture most directly meets the need for low-latency global content delivery?
- Deploy only a regional internal load balancer for public images
- Keep all images on an origin VM with no CDN
- Move images to a larger disk in the original region
- Use a global external Application Load Balancer with Cloud CDN for cacheable images
Explanation
Correct Answer
D:Edge caching reduces repeated origin fetches and improves latency for faraway clients
Incorrect Answers
A:Does not provide global edge cache to external viewers. Edge caching reduces repeated origin fetches and improves latency for faraway clients.
B:Repeated distant downloads still pay origin latency. Edge caching reduces repeated origin fetches and improves latency for faraway clients.
C:Storage capacity does not minimize geographic round trips. Edge caching reduces repeated origin fetches and improves latency for faraway clients.
Question 30
A public image catalog serves millions of geographically dispersed viewers and origin latency drives poor page responsiveness. Which implementation choice most directly delivers cache-correct publishing?
- Use the same mutable URL for every version without a cache policy
- Set content cache keys and explicit cache-control headers for versioned media
- Invalidate every object every minute
- Set every public image response to no-store
Explanation
Correct Answer
B:Well-defined cache behavior avoids serving stale images after asset updates
Incorrect Answers
A:May keep old content in client and edge caches. Well-defined cache behavior avoids serving stale images after asset updates.
C:Destroys caching efficiency and increases origin demand. Well-defined cache behavior avoids serving stale images after asset updates.
D:Turns off the edge-cache benefit. Well-defined cache behavior avoids serving stale images after asset updates.
Google Cloud Certified - Professional Cloud Architect (Professional Cloud Architect) Practice Tests