mcnz.com migrated its busy ticketing platform database to Cloud SQL for MySQL six months ago and monitoring now shows persistently low CPU and memory usage which indicates the instance is oversized…

Question

Options

• AMigrate the database to a self managed MySQL instance on Compute Engine to gain cost control
• BTurn off automated backups to reduce storage charges
• CReview and apply Cloud SQL rightsizing recommendations for the instance
• DResize to a smaller machine type that matches metrics from the last 90 days

Explanation

The most efficient action is to review and apply Cloud SQL rightsizing recommendations generated by Google Cloud's Recommender service. This service automatically analyzes CPU and memory utilization metrics over time and produces specific, data-driven instance size recommendations-eliminating manual analysis effort and reducing the risk of under-provisioning. Option A (migrating to self-managed MySQL on Compute Engine) is operationally complex, increases management burden, and is not guaranteed to reduce costs. Option B (disabling automated backups) is a risky cost-cutting measure that compromises recoverability. Option D (manually resizing based on 90-day metrics) is similar in outcome to C but less efficient because it requires manual analysis rather than leveraging the built-in Recommender tooling.

No community discussion yet for this question.