You need to migrate a 2TB relational database to Google Cloud Platform. You do not have the resources to significantly refactor the application that uses this database and cost to operate is of…

Question

Options

• ACloud Spanner
• BCloud Bigtable
• CCloud Firestore
• DCloud SQL

• A
  3% (1)
• B
  6% (2)
• C
  15% (5)
• D
  76% (25)

Explanation

Cloud SQL is the right choice because it's a fully managed relational database service (supporting MySQL, PostgreSQL, and SQL Server) that lets you lift-and-shift an existing relational workload with minimal application refactoring - and it's significantly cheaper to operate than enterprise alternatives.

• A (Cloud Spanner) is wrong because, while it's a managed relational database, it's designed for globally distributed, horizontally scalable workloads and carries a much higher cost - overkill for a standard migration where cost is the primary concern.
• B (Cloud Bigtable) is wrong because it's a NoSQL wide-column store optimized for massive analytical/time-series workloads; migrating a relational schema to it would require significant application refactoring, violating a key constraint.
• C (Cloud Firestore) is wrong because it's a NoSQL document database suited for mobile/web apps with flexible schemas, not a drop-in replacement for a relational database.

Memory tip: Think "SQL → Cloud SQL" - if your app already speaks SQL and you can't rewrite it, Cloud SQL is the managed service that speaks the same language at the lowest operational cost.

No community discussion yet for this question.