PROFESSIONAL-DATA-ENGINEER · Question #163
You work for a mid-sized enterprise that needs to move its operational system transaction data from an on-premises database to GCP. The database is about 20 TB in size. Which database should you…
The correct answer is A. Cloud SQL. Cloud SQL is the right choice because it's GCP's fully managed relational database service (MySQL, PostgreSQL, SQL Server) designed for migrating traditional on-premises OLTP/transactional workloads - exactly the use case described, and it supports databases up to ~64 TB per…
Question
Options
- ACloud SQL
- BCloud Bigtable
- CCloud Spanner
- DCloud Datastore
How the community answered
(47 responses)- A72% (34)
- B17% (8)
- C4% (2)
- D6% (3)
Explanation
Cloud SQL is the right choice because it's GCP's fully managed relational database service (MySQL, PostgreSQL, SQL Server) designed for migrating traditional on-premises OLTP/transactional workloads - exactly the use case described, and it supports databases up to ~64 TB per instance.
Cloud Bigtable (B) is a NoSQL wide-column store optimized for high-throughput analytics and time-series data, not structured transactional systems migrated from relational databases. Cloud Spanner (C) is also a relational database, but it's designed for globally distributed, horizontally scalable workloads at massive scale - it's overkill and cost-prohibitive for a single 20 TB enterprise migration. Cloud Datastore (D) is a NoSQL document database suited for web/mobile app data, not relational transactional data.
Memory tip: Think of the question keywords - "operational," "transaction data," and "on-premises database." These signal a traditional relational workload. Cloud SQL = lift-and-shift for relational OLTP. Spanner is for when you've outgrown Cloud SQL and need global scale.
Topics
Community Discussion
No community discussion yet for this question.