1Z0-997-25 Question 163
Single answerAn e-commerce application running on multiple OCI Compute instances behind a Load Balancer is experiencing intermittent performance bottlenecks. The team wants to implement the OCI Observability platform to proactively identify and troubleshoot the issues. Which approach best ensures end-to-end visibility and proactive alerting using OCI� native Observability components?
- A
Enable Monitoring on Compute instances, configure custom Metrics to track CPU usage, and rely on the default Log retention inside each VM.
- B
Configure OCI Logging to capture instance logs, forward them to Logging Analytics for advanced analysis, set up Oracle Cloud Infrastructure Monitoring with Alarms, and integrate Alarms with Notifications for proactive alerts.
- C
Manually download log files from each Compute instance, open them locally for analysis, and schedule an OS-level cron job to send email notifications when error codes are found.
- D
Integrate Logs directly with an external third-party analytics tool without configuring any OCI Logging or Monitoring services.
Show answer and explanation
Correct answer: B
Explanation
OCI� Observability platform offers built-in Logging, Logging Analytics, Monitoring, Alarms, and Notifications to help diagnose performance bottlenecks and proactively alert on issues. Configuring end-to-end visibility involves sending logs to OCI Logging and Logging Analytics for analysis, setting up Monitoring for relevant metrics, creating Alarms, and using Notifications for real-time alerts. Refer to the Oracle documentation on Logging and Observability (docs.oracle.com/en-us/iaas/Content/Observability/home.htm) for best practices and detailed configurations.
- A. Incorrect.
Option 1: Incorrect. Although enabling Monitoring on Compute instances and customizing Metrics is useful, solely depending on default local Logs does not leverage the centralized Logging and advanced analytics capabilities in OCI. This approach lacks a proactive detection and correlation mechanism for performance issues.
- B. Correct.
Option 2: Correct. By capturing logs in OCI Logging and analyzing them with Logging Analytics, you gain deeper insights into performance issues. OCI Monitoring and Alarms help you track custom metrics or built-in metrics (like CPU usage, memory, etc.), and Notifications provide automated alerting. This fully uses the OCI Observability platform for end-to-end visibility.
- C. Incorrect.
Option 3: Incorrect. Manually downloading logs and reviewing them locally is time-consuming and prone to human error. While OS-level email alerts can be configured, this approach does not provide the comprehensive analytics or correlation that Logging Analytics and OCI Monitoring offer.
- D. Incorrect.
Option 4: Incorrect. Using an external tool without leveraging OCI� built-in Observability services might miss out on efficient, native integrations (such as Logging, Logging Analytics, Alarms, and Notifications). It also typically requires additional setup and maintenance, reducing the value of OCI� end-to-end Observability framework.