Skip to content

Matching a managed storage service to the workload it needs to serve

Google Cloud offers purpose-built managed storage services spanning relational OLTP, analytical OLAP, NoSQL, object, and in-memory workloads, and the exam expects you to map workload characteristics (data model, scale, consistency, latency, query pattern) to the right service. Choosing correctly hinges on distinguishing transactional vs analytical needs, structured vs unstructured data, and global vs regional consistency requirements.

1 · Learn the must-know

  • Use Cloud SQL for traditional relational OLTP (MySQL, PostgreSQL, SQL Server) at regional scale with vertical scaling limits; use AlloyDB for PostgreSQL-compatible workloads needing higher performance, HTAP analytics, and better scalability than Cloud SQL.
  • Use Spanner when you need horizontally scalable, globally distributed relational data with strong consistency and 99.999% availability SLA (multi-region), typically for mission-critical OLTP at massive scale.
  • Use BigQuery for serverless SQL analytics/data warehousing on structured/semi-structured data at petabyte scale; use BigLake to apply BigQuery's governance, security, and query engine over data stored in open formats (e.g., Parquet) in Cloud Storage or other lakes without duplicating data.
  • Use Bigtable for high-throughput, low-latency NoSQL wide-column workloads (time-series, IoT, ad tech) requiring massive write/read scale but with eventual consistency and no complex joins/transactions.
  • Use Firestore for flexible-schema NoSQL document data with real-time sync, mobile/web SDKs, and strong consistency for smaller-scale transactional app data (not for heavy analytics or massive throughput like Bigtable).
  • Use Cloud Storage for unstructured object data (files, backups, staging for pipelines) at any scale with storage classes for cost/latency tradeoffs, and Memorystore (Redis/Memcached) for managed in-memory caching to reduce latency for frequently accessed data, not as a system of record.

2 · Check your understanding

Check this objectiveFree · always available

A financial services company is building a globally distributed ledger application. The application requires strong consistency, ACID transactions across rows, relational schema with SQL joins, and the ability to scale horizontally across multiple regions without manual sharding. Which managed service should the data engineer choose?

Your objective map0 tried · 0 answered correctly · 67 untouched

What you have tried across GCP PDE's objectives, not a readiness score.

Designing data processing systems~22% of the exam0 of 17 tried
Ingesting and processing the data~25% of the exam0 of 11 tried
Storing the data~20% of the exam0 of 13 tried
Preparing and using data for analysis~15% of the exam0 of 11 tried
Maintaining and automating data workloads~18% of the exam0 of 15 tried

3 · Keep going