Explanation:
Given the requirement to start small and scale globally with minimal downtime, Cloud Spanner is the best choice due to its horizontal scalability and global distribution capabilities. Starting with a regional configuration (Option A) is cost-effective for the pilot phase but lacks global scalability. A multi-region configuration (Option B) is ideal for global expansion and high availability, making it the correct choice for long-term needs. Cloud SQL (Options C and D) is not as scalable or globally distributed as Cloud Spanner, making them less suitable for the described scenario.
Ultimate access to all questions.
How should you design a database strategy for a new web application that begins with a small pilot in one country but must scale to support millions of users globally while maintaining 24/7 availability with minimal maintenance downtime?
A
Use Cloud Spanner in a regional configuration.
B
Use Cloud Spanner in a multi-region configuration.
C
Use Cloud SQL with cross-region replicas.
D
Use highly available Cloud SQL with multiple zones.
No comments yet.