Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise analytics application deployed in Google Cloud processes financial transaction logs. The compliance team mandates that all log data must strictly adhere to data residency regulations and never leave the europe-west3 (Frankfurt) location.
The data access pattern is characterized as follows:
Which Cloud Storage bucket configuration and lifecycle management strategy should you implement to minimize costs while complying with all requirements?
This architecture leverages a regional Cloud Storage bucket in europe-west3 combined with automated Object Lifecycle Management rules. It places objects initially in Standard storage and progressively shifts them through Nearline and Coldline storage before deleting them at the end of their compliance retention window.
europe-west3, all object data at rest is guaranteed to remain strictly within the Frankfurt region, satisfying the regulatory requirements.Using a regional bucket satisfies data residency mandates without incurring multi-region egress or replication overhead. Matching the data lifecycle transitions to the exact access cadence (Standard for hot data, Nearline for monthly access, Coldline for rare access) minimizes total cost of ownership (TCO).
Setting the default storage class of a bucket to Coldline storage causes every newly written object to immediately inherit the Coldline tier, which is designed for data accessed at most once a quarter.
The data were written once and rarely or never read for the first 90 days, such as secondary database backups or cold audit logs.
A multi-regional Cloud Storage bucket in the eu location stores object data redundantly across multiple geographic regions within the European Union (such as Belgium, Germany, and the Netherlands).
europe-west3 (Frankfurt). Multi-regional buckets replicate data across several separate countries/regions across the EU, violating specific local jurisdiction boundaries.The workload required continental high availability across European data centers and did not have strict localized data sovereignty constraints requiring data to remain only in Frankfurt.
The Rapid storage class in zonal buckets is designed for data-intensive AI/ML and streaming analytics workloads requiring microsecond-scale latencies and direct compute co-location within a single zone.
europe-west3-a). If that zone experiences an outage, access to the logs is interrupted. Standard regional buckets automatically provide multi-zone availability across three zones within the region.The workload was a specialized high-performance AI training pipeline requiring co-located low-latency scratch storage rather than general-purpose compliance log retention.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated