Google Professional Cloud Database Engineer Question 89
Select 2Google Cloud PlatformYou are tasked with designing a database solution for an application that requires high availability and scalability while minimizing costs. The application has unpredictable traffic patterns, with peak loads occurring sporadically. Which combination of database solutions should you choose to optimize costs while meeting these requirements?
- A
Use Cloud Spanner with a multi-region configuration for high availability and scalability.
- B
Choose Cloud SQL with read replicas and scale vertically during peak traffic.
- C
Implement Firestore in Native mode with on-demand pricing to handle unpredictable traffic.
- D
Use BigQuery for storing and querying the application's transactional data.
- E
Adopt Cloud Bigtable for handling high-throughput, low-latency workloads with dynamic scaling.
Show answer and explanation
Correct answers: C, E
Explanation
To optimize costs for unpredictable traffic patterns, it's essential to choose database solutions that automatically scale and charge based on actual usage. Firestore in Native mode offers automatic scaling and on-demand pricing, making it suitable for sporadic traffic. Cloud Bigtable is another cost-effective choice for high-throughput, low-latency workloads with dynamic scaling capabilities. Other options, like Cloud Spanner or Cloud SQL, might meet the requirements but are less cost-efficient for this specific use case.
- A. Incorrect.
Cloud Spanner is highly available and scalable, but its multi-region configuration is expensive and better suited for global-scale applications with consistent traffic, not cost optimization for sporadic traffic.
- B. Incorrect.
Cloud SQL with read replicas can scale vertically, but this approach is less cost-effective for unpredictable traffic patterns, as you may need to over-provision resources during peak times.
- C. Correct.
Firestore in Native mode with on-demand pricing is well-suited for unpredictable traffic patterns, as it automatically scales and charges based on usage, optimizing costs.
- D. Incorrect.
BigQuery is designed for analytical workloads, not transactional data. Using it for this scenario would result in inefficiencies and higher costs.
- E. Correct.
Cloud Bigtable is optimized for high-throughput, low-latency workloads and can dynamically scale to handle sporadic traffic efficiently, making it cost-effective for such scenarios.