GOOGLE-PROFESSIONAL-CLOUD-DEVELOPER practice question 26 of 35
In order to meet their business requirements, how should HipLocal store their application state?
Full set: 265 questionsThe question implies business requirements for a highly available, globally scalable, and strongly consistent database, which are common for modern applications. Cloud Spanner is a unique, fully managed relational database service designed for these specific needs. It provides horizontal scalability across regions, synchronous replication for high availability (up to 99.999% SLA), and strong transactional consistency at a global scale. Migrating the application state to Cloud Spanner directly addresses the challenges of scaling a traditional relational database like MySQL for a global user base while minimizing operational overhead.
A. Use local SSDs to store state. Local SSDs provide temporary, block-level storage. They are ephemeral and data is lost if the VM instance is stopped or terminated, making them unsuitable for persistent state.
B. Put a memcache layer in front of MySQL. Memcache is a caching solution. While it can improve read performance, it does not solve the underlying scalability, availability, or global distribution limitations of the MySQL database itself.
D. Replace the MySQL instance with Cloud SQL. Cloud SQL is a fully managed regional database service. It does not offer the native global distribution and horizontal scalability that Cloud Spanner provides for a massive, worldwide application.
1. Google Cloud Documentation, "What is Cloud Spanner?": "Cloud Spanner is a fully managed, mission-critical, relational database service that offers transactional consistency at global scale, schemas, SQL... and automatic, synchronous replication for high availability." This directly supports the choice of Spanner for global scale and high availability.
2. Google Cloud Documentation, "Choosing a storage option": This guide compares database options. It positions Cloud Spanner for "unlimited scale" and "global consistency," while Cloud SQL is categorized under "Relational databases" with a focus on regional deployments for applications like WordPress or e-commerce.
3. Google Cloud Documentation, "Local SSDs": "Data on a local SSD persists only until the instance is stopped or deleted... Because of these limitations, do not use local SSDs for storage that must be persistent." This confirms why option A is incorrect.
4. Google Cloud Documentation, "Cloud SQL features": The documentation describes Cloud SQL's high availability configuration using a regional standby instance, which contrasts with Cloud Spanner's multi-region, global architecture. This highlights why Cloud SQL is less suitable for the implied global requirements.
Keep practicing
Take the free GOOGLE-PROFESSIONAL-CLOUD-DEVELOPER practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other GOOGLE-PROFESSIONAL-CLOUD-DEVELOPER practice questions
- Question 1You have an application controlled by a managed instance group. When you deploy a new ver…
- Question 2Your service adds text to images that it reads from Cloud Storage. During busy times of t…
- Question 3You have been tasked with planning the migration of your company’s application from on-pr…
- Question 4You plan to make a simple HTML application available on the internet. This site keeps inf…
- Question 5HipLocal's APIs are showing occasional failures, but they cannot find a pattern. They wan…
- Question 6Your company has created an application that uploads a report to a Cloud Storage bucket. …
