Q: 2
Your organization is running a MySQL workload in Cloud SQL. Suddenly you see a degradation in
database performance. You need to identify the root cause of the performance degradation. What
should you do?
Options
Discussion
Option B, Logs let you dig deeper, but first thing is to check metrics like CPU and memory in Cloud Monitoring. A is tempting but can miss the bigger picture.
A , Logs Explorer should highlight any error spikes or slow queries logged by MySQL. I usually start there for quick clues when performance drops. Not 100% sure it's the fastest way here though.
Don’t think A is right here. B lets you check CPU, memory, and storage metrics in real time, which almost always show where the slowdown starts with Cloud SQL. If you’ve hit performance issues before, that’s usually the first place to look. Pretty sure it’s B.
Its A
B makes the most sense. Cloud Monitoring gives you real-time visibility into CPU, memory, and disk usage, which are usually behind performance drops in Cloud SQL. Logs (A) are helpful but more for digging deeper after spotting an issue. Pretty sure B is the right first move.
B , Cloud Monitoring gives a quick view of resource bottlenecks that usually cause Cloud SQL slowdowns. A looks tempting but is more for digging into specific events after you know something’s up. Pretty sure B is what Google expects here. Disagree?
A is wrong, B. Metrics from Cloud Monitoring show resource issues way quicker for Cloud SQL performance hits.
Be respectful. No spam.
