Google Cloud Certified Professional Cloud Database Engineer Practice Mode

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose D2

  1. Microservices Best Practices: • The database-per-service pattern reduces contention by isolating workloads. Each microservice uses a dedicated Cloud SQL instance, preventing cross-service resource competition. • Smaller instances are easier to scale independently based on individual service needs. 2. Horizontal Scaling: • Splitting the monolithic database into smaller instances aligns with Google’s recommendation for horizontal scaling in microservices (search result). • Avoids hitting connection limits, I/O bottlenecks, or lock contention that may occur in a single large instance, even if CPU utilization appears normal. 3. Minimal Refactoring: • Requires only configuration changes (e.g., updating connection strings) rather than rewriting application logic.

• Chose C1

  Storage Size Impact: Increasing the storage size for your Cloud SQL instance can improve performance because Cloud SQL automatically increases the IOPS (Input/Output Operations Per Second) as the storage size increases. This can help resolve performance bottlenecks related to disk I/O, which might be the underlying issue given that CPU utilization is normal. No Major Refactoring: This approach does not require any significant changes to your application architecture or code, making it a straightforward solution. Scalability: By increasing the storage size, you can ensure that your instance has the necessary IOPS to handle the increasing load as your application grows.

• Chose C1

  cant do major refactoring. also CPU utilization is under control then mostly issue is with IOPS capacity of CloudSQL we need to increase storage space. to increase IOPS