Google Professional Cloud Database Engineer Question 10
Single answerGoogle Cloud PlatformYour organization is migrating a critical on-premises transactional database to Google Cloud. The current database processes an average of 10,000 transactions per second (TPS) with occasional spikes up to 15,000 TPS. Each transaction averages 3 KB in size, and the organization expects a 30% increase in transactional volume over the next 12 months. The database must support high availability with minimal downtime and provide scalability to accommodate future growth. Which Google Cloud database solution and configuration would best meet these requirements?
- A
Use Cloud SQL with a single regional instance and enable automatic storage scaling.
- B
Deploy Firestore in Native mode for its scalability and serverless architecture.
- C
Use a Spanner instance with multi-region configuration and sufficient node allocation.
- D
Deploy a single-node Memorystore instance for its high-performance caching capability.
Show answer and explanation
Correct answer: C
Explanation
The scenario requires a solution that can handle high TPS, provide scalability for future growth, and ensure high availability. Spanner is the best choice as it is a globally distributed, horizontally scalable relational database. Its multi-region configuration ensures minimal downtime, and it is well-suited for transactional workloads. Other options either lack the necessary scalability, availability, or are not designed for transactional workloads.
- A. Incorrect.
Cloud SQL with a single regional instance may not handle the high transactional throughput or support the scalability required for future growth. Additionally, it does not provide multi-region high availability.
- B. Incorrect.
Firestore is a NoSQL database optimized for document-based use cases, not transactional workloads with high TPS requirements. It is unsuitable for this scenario.
- C. Correct.
Spanner is a globally distributed, horizontally scalable relational database that provides high availability with multi-region configurations. It can handle high transactional throughput and is designed for workloads like this scenario.
- D. Incorrect.
Memorystore is a caching service and not a primary database solution. It cannot handle the transactional consistency and scalability required for a mission-critical workload.