Google Professional Cloud Developer
Get started today
Ultimate access to all questions.
HipLocal's current environment includes APIs running on Compute Engine VMs in GCP, state stored in a single-instance MySQL database, and no logging. They aim to improve resilience for their MySQL deployment while meeting business requirements (global expansion, user scalability, compliance) and technical requirements (metrics, monitoring, logging, serverless architecture, secure access).
Which MySQL configuration should they implement to achieve these goals?
(Note: The original OCR/case study text was streamlined for clarity while preserving all key details—business/technical requirements, existing environment, and objectives.)
HipLocal's current environment includes APIs running on Compute Engine VMs in GCP, state stored in a single-instance MySQL database, and no logging. They aim to improve resilience for their MySQL deployment while meeting business requirements (global expansion, user scalability, compliance) and technical requirements (metrics, monitoring, logging, serverless architecture, secure access).
Which MySQL configuration should they implement to achieve these goals?
(Note: The original OCR/case study text was streamlined for clarity while preserving all key details—business/technical requirements, existing environment, and objectives.)
Explanation:
HipLocal's requirement to improve the resilience of their MySQL deployment while meeting their business and technical requirements is best addressed by replacing the current single instance MySQL instance with Cloud SQL and configuring high availability. This approach leverages Google's managed services to ensure scalability, reduce infrastructure management time and cost, and comply with Google-recommended practices for cloud computing. Cloud SQL's high availability configuration provides automatic failover, enhancing the application's resilience and uptime, which is crucial for expanding to new regions and supporting more concurrent users. Options A and B involve maintaining or partially migrating to Compute Engine, which does not fully align with the move to a serverless architecture or reduce management overhead as effectively as Cloud SQL. Option D is incorrect because Cloud SQL requires explicit configuration for high availability; redundancy is not provided without further configuration.