Answer-first summary for fast verification
Answer: Configure a single region instance of Cloud Spanner initially and then configure multi-region Cloud Spanner instances after securing funding
**Correct Answer: C. Configure a single region instance of Cloud Spanner initially and then configure multi-region Cloud Spanner instances after securing funding** - **Initial Cost Optimization**: Starting with a single-region Cloud Spanner instance is more cost-effective than a multi-region setup. You only pay for the resources in one region. - **Global Expansion and Performance**: Cloud Spanner is designed for global scale and offers strong consistency with horizontal scaling. After securing funding, transitioning to a multi-region configuration allows you to distribute your database across multiple regions, providing lower latency for global users and increased availability. - **Native JDBC Driver**: Cloud Spanner offers a native JDBC driver, fulfilling the requirement for optimized performance when expanding globally. **Why Not Others?** - **A & D**: Switching from Cloud SQL to Bigtable introduces eventual consistency, which might not be suitable for all web application workloads. Also, Bigtable lacks a native JDBC driver. - **B**: While starting with a highly available instance of Cloud SQL is resilient, it doesn’t provide the global scale and low latency across regions that Cloud Spanner offers. The transition to Bigtable also involves significant application changes and lacks a native JDBC driver.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You are running a web application that currently serves customers from a single region in Asia. You are planning to expand your services globally, but initially, you want to optimize for cost. After securing funding, you plan to optimize for global presence and performance using a native JDBC driver. Which option should you choose?
A
Start with a zonal instance of Cloud SQL for PostgreSQL, and then use Bigtable with US, Europe, and Asia replication after securing funding.
B
Start with a highly available instance of Cloud SQL for PostgreSQL, and then use Bigtable with US, Europe, and Asia replication after securing funding.
C
Configure a single region instance of Cloud Spanner initially and then configure multi-region Cloud Spanner instances after securing funding
D
Start with a zonal instance of Cloud SQL for PostgreSQL and then use Cloud SQL for PostgreSQL with highly available configuration after securing funding.
No comments yet.