Answer-first summary for fast verification
Answer: Replace your monitoring platform with Cloud Monitoring.
The issue is that the legacy on-premises monitoring platform is causing slow notifications for cloud applications. Option A (replacing the legacy platform with Cloud Monitoring) addresses the root cause by using Google's native solution optimized for cloud environments, which provides faster alerting and can monitor both cloud and on-premises resources with proper agent setup. Options B and D do not resolve the alerting bottleneck because they still rely on the legacy system for notifications. Option C avoids the problem rather than solving it. Thus, migrating fully to Cloud Monitoring (A) ensures efficient monitoring and alerting tailored to cloud applications.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
You have migrated some applications to Google Cloud but are still using an on-premises legacy monitoring platform for both on-premises and cloud-deployed applications. You notice that the notification system is slow to respond to time-critical issues in cloud applications. What should you do?
A
Replace your monitoring platform with Cloud Monitoring.
B
Install the Cloud Monitoring agent on your Compute Engine instances.
C
Migrate some traffic back to your old platform. Perform A/B testing on the two platforms concurrently.
D
Use Cloud Logging and Cloud Monitoring to capture logs, monitor, and send alerts. Send them to your existing platform.
No comments yet.