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.
A development team is building a cloud-native telemetry and analytics platform that stores application event records and serves complex SQL aggregation queries. Currently, the dataset is 800 GB, but projected customer growth will expand the volume to 2 PB over the next three years. Most queries filter by event timestamp and tenant ID.
The team has the following requirements for the storage architecture:
Which storage solution should the team select?
BigQuery is a fully managed, serverless petabyte-scale data warehouse built on a massively parallel processing (MPP) architecture. Unlike traditional node-based databases, it uses a columnar storage format and completely decouples compute, memory, and storage, allowing each layer to scale independently.
Compared to Cloud SQL (capped at 64 TB per instance), Filestore (capped at 100 TiB per instance), and Cloud Bigtable (a NoSQL store without native SQL aggregation), BigQuery is the only solution purpose-built to store multiple petabytes of structured event data with decoupled compute costs and fast SQL analytics.
Cloud Bigtable is a fully managed, petabyte- and exabyte-scale NoSQL wide-column database engineered for ultra-low-latency operational workloads, high-throughput ingestion, and key-based or contiguous row-key range scans.
The application required sub-10-millisecond point reads and massive high-throughput writes (such as IoT time-series ingestion, personalization, or real-time fraud detection) accessed via a well-designed row key rather than SQL analytical queries.
In production architectures, teams often stream high-velocity operational events into Bigtable for real-time serving while exporting historical data to BigQuery for petabyte-scale SQL reporting.
Cloud SQL is a fully managed relational database service for MySQL, PostgreSQL, and SQL Server. It provides ACID-compliant transactional processing using Persistent Disk SSD/HDD or Hyperdisk Balanced block storage attached to virtual machine instances.
The workload were an OLTP transactional application whose total dataset remains well below 64 TB and requires strict relational integrity, low-latency row-level updates, and standard SQL joins rather than petabyte-scale analytical aggregations.
Although enabling automatic storage increases prevents minor capacity surprises at gigabyte scale, it cannot overcome Cloud SQL's single-instance 64 TB ceiling or replace a distributed columnar warehouse for multi-petabyte analytics.
Filestore is a fully managed Network File System (NFS) file storage service designed to provide shared hierarchical file storage for Compute Engine virtual machines and Google Kubernetes Engine (GKE) clusters.
The workload required a shared POSIX file system mounted simultaneously across multiple Compute Engine VMs or GKE Pods—such as lift-and-shift enterprise applications, shared configuration directories, or common tooling repositories—within a 100 TiB capacity footprint.
Even when storing analytical file formats like Parquet in Google Cloud, petabyte-scale data lakes typically pair Cloud Storage (which scales to exabytes) or BigQuery rather than Filestore, avoiding Filestore's 100 TiB per-instance limit.
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