Your organization has hundreds of Cloud SQL for MySQL instances. You want to follow Google- recommended practices to optimize platform costs. What should you do?

Question

Options

• AUse Query Insights to identify idle instances.
• BRemove inactive user accounts.
• CRun the Recommender API to identify overprovisioned instances.
• DBuild indexes on heavily accessed tables.

• A
  17% (9)
• B
  6% (3)
• C
  70% (38)
• D
  7% (4)

Explanation

Options B (removing inactive user accounts) and D (building indexes) are performance or security hygiene tasks that have no direct impact on infrastructure costs. Option A (Query Insights) is a tool for analyzing slow or inefficient queries - useful for performance tuning but not for identifying over-allocated or idle infrastructure. Option C is the Google-recommended approach: the Recommender API includes Cloud SQL-specific recommenders (idle instance recommender and overprovisioned instance recommender) that analyze actual usage metrics like CPU, memory, and connections. At scale with hundreds of instances, programmatically querying the Recommender API surfaces actionable, data-driven cost-optimization opportunities - such as downsizing over-provisioned instances or deleting idle ones - with minimal manual effort.

No community discussion yet for this question.