Google Professional Cloud Database Engineer Question 69
Single answerGoogle Cloud PlatformYour company is migrating a legacy on-premises relational database to Google Cloud. The database has strict low-latency requirements, supports complex queries, and needs to handle high transactional throughput. Additionally, the database must scale horizontally to accommodate unpredictable spikes in traffic. Which Google Cloud database solution would you recommend?
- A
Cloud SQL
- B
Cloud Spanner
- C
BigQuery
- D
Firestore
Show answer and explanation
Correct answer: B
Explanation
Cloud Spanner is the optimal choice for this use case because it is a fully managed, globally distributed, horizontally scalable relational database. It meets all the requirements of the scenario, including low latency, support for complex queries, high transactional throughput, and the ability to scale horizontally. Other options like Cloud SQL, BigQuery, and Firestore lack one or more of these critical features, making them less suitable for the given requirements.
- A. Incorrect.
Cloud SQL is a managed relational database service that supports MySQL, PostgreSQL, and SQL Server. While it is suitable for many transactional workloads, it does not natively support horizontal scaling, which makes it less suitable for handling unpredictable spikes in traffic.
- B. Correct.
Cloud Spanner is a globally distributed, horizontally scalable relational database. It is designed for high transactional throughput, supports complex queries, and meets low-latency requirements, making it the best choice for this scenario.
- C. Incorrect.
BigQuery is a serverless data warehouse optimized for analytics and batch processing. It is not designed for high transactional throughput or low-latency transactional operations, so it is not suitable for this use case.
- D. Incorrect.
Firestore is a NoSQL document database suitable for building mobile and web applications. While it scales horizontally and supports low latency, it is not designed to handle complex relational queries or high transactional throughput.