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 layer for an interactive gaming and analytics platform with two distinct workloads:
You want to optimize the performance-to-volume cost ratio for both workloads while minimizing operational overhead. Which storage architecture should you choose?
BigQuery is a fully managed, serverless columnar OLAP data warehouse designed for running interactive SQL aggregations and petabyte-scale analytical queries across massive datasets.
The 150 TB telemetry store only needed interactive SQL aggregations and business intelligence reporting (such as daily dashboards) rather than single-digit millisecond operational reads and sorted row-key range scans.
In many cloud-native architectures, Bigtable and BigQuery complement each other: Bigtable serves high-throughput ingestion and low-latency operational reads, while BigQuery queries Bigtable via external tables or exported snapshots for deep OLAP analytics.
Cloud Bigtable HDD storage uses spinning hard disk drives to provide high storage density (16 TB per node) at a lower per-gigabyte cost than SSD storage. It is designed for massive, write-heavy datasets where sequential scans are common and read latency is not critical.
The entire 150 TB workload consisted exclusively of latency-insensitive, write-heavy batch archiving (such as daily offline reporting) with no user-facing single-digit millisecond reads or sub-millisecond caching requirements.
Even when cost optimization is a priority, using HDD for user-facing applications often backfires because extra nodes must be provisioned just to handle random read QPS, eroding the per-GB storage savings.
Cloud Bigtable is a fully managed, petabyte-scale NoSQL wide-column database designed for high-throughput operational and analytical workloads. Memorystore for Redis is a fully managed in-memory data store built on Redis that delivers sub-millisecond latency for caching, session management, and real-time data structures.
Pairing Bigtable SSD with Memorystore for Redis matches each workload's access pattern and latency tier to the most cost-effective storage medium, ensuring sub-millisecond caching for active sessions and scalable, low-latency analytics over massive historical data.
The Bigtable in-memory tier is a specialized hybrid storage option in Enterprise Plus that adds a RAM layer to Bigtable SSD nodes using remote direct memory access (RDMA). It provides read-through caching for sub-millisecond point-read latency through the standard Bigtable API.
The total active dataset fit within a 10-node cluster, required only sub-millisecond single-row point lookups (such as an online ML feature store), and did not require Redis data structures like Sorted Sets.
Separating the 40 GB hot cache into Memorystore for Redis lets Bigtable scale independently beyond 10 nodes to support petabyte-scale analytical workloads.
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