Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
You are designing the data architecture for a global e-commerce platform serving shoppers across North America, Europe, and Asia. The system has two core data requirements:
Which combination of storage services and application-level configuration should you implement?
Bigtable is a high-throughput, low-latency NoSQL wide-column database designed for massive analytical and operational workloads. When configured with multi-cluster replication, it prioritizes availability and partition tolerance under the CAP theorem using eventual consistency across clusters. A write-back (write-behind) cache writes updates to Memorystore for Redis first and flushes them asynchronously to the persistent store.
The workload involved high-throughput time-series, IoT, or telemetry writes that tolerated eventual consistency and required sub-10ms NoSQL writes rather than strict global SQL transactions.
Cache-Control: public, max-age=60 metadata on each uploaded image.Spanner is a globally distributed, horizontally scalable relational database that provides external (strong) consistency, ACID SQL transactions, and high availability across multiple regions. Cloud Storage in a multi-region configuration stores objects redundantly across geographically separated regions with strong global read-after-write consistency, while Cloud CDN caches publicly accessible assets at edge locations worldwide.
Cache-Control: public, max-age=60 metadata on each object caps edge cache lifetime at 60 seconds, mitigating stale reads while preserving global Cloud CDN performance.Cache-Control metadata enforces predictable freshness guarantees across edge caches.Unlike single-primary relational databases or eventually consistent NoSQL stores, Spanner delivers both strong global consistency and multi-region availability for transactional inventory. Pairing Cloud Storage multi-region buckets with Cloud CDN and explicit max-age=60 metadata achieves low-latency global image delivery without violating the 60-second freshness target.
Cache-Control: no-cache headers in client read requests.Cloud SQL is a managed relational database service where a single primary instance handles all write operations, and cross-region read replicas receive updates asynchronously to offload regional read traffic. On the client side, sending Cache-Control: no-cache on HTTP read requests attempts to ask caches to revalidate content on demand.
Cache-Control headers intended to bypass cached content. Without setting Cache-Control metadata on the stored object itself, publicly readable cached objects can remain stale for up to 60 minutes.The application operated within a single region where Cloud SQL zonal high availability sufficed, cross-region reads could tolerate eventual consistency, and stale object behavior was controlled through object metadata rather than client request headers.
AlloyDB for PostgreSQL is a managed PostgreSQL-compatible database offering high performance and zonal high availability within a region. Memorystore for Redis provides an in-memory cache to accelerate reads, while Cloud Storage dual-region buckets with turbo replication ensure asynchronous cross-region object replication within a 15-minute recovery point objective (RPO).
All transactional users resided near a single region, inventory reads could tolerate brief cache staleness, and media assets only needed regional disaster recovery between two specific regions rather than global edge caching.
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