1Z0-997-25 Question 165
Single answerYou have deployed multiple microservices on Oracle Container Engine for Kubernetes (OKE). The application is experiencing intermittent performance issues, and your development team wants to correlate metrics, logs, and distributed traces within a single observability platform. Which approach best achieves full observability with minimal setup on Oracle Cloud Infrastructure?
- A
Use Oracle Cloud Infrastructure Resource Manager to capture microservice logs and metrics, then integrate them into Logging Analytics for correlation
- B
Use Oracle Cloud Infrastructure Monitoring for metrics, Oracle Cloud Infrastructure Logging for logs, and Trace Explorer for distributed tracing, while connecting them via Service Connector Hub
- C
Use Oracle Cloud Infrastructure Streaming for real-time log ingestion and Oracle Functions to transform logs before storing them in an external repository
- D
Run an open-source aggregator on your own instances and forward all logs, metrics, and traces to Oracle Logging Analytics for processing
Show answer and explanation
Correct answer: B
Explanation
Oracle's Observability and Management platform provides an integrated approach to collecting and analyzing telemetry data (metrics, logs, and traces). OCI Monitoring, Logging, Logging Analytics, and Trace Explorer�connected through the Service Connector Hub�enable end-to-end visibility with minimal overhead. This aligns with best practices detailed in the official OCI Observability documentation.
- A. Incorrect.
INCORRECT: Oracle Resource Manager is primarily used for managing infrastructure as code, not for collecting logs and metrics directly. While Logging Analytics can unify logs, Resource Manager is not designed for telemetry ingestion.
- B. Correct.
CORRECT: Oracle Cloud Infrastructure Monitoring, Logging, and Trace Explorer are core OCI services for collecting metrics, logs, and distributed traces, respectively. The Service Connector Hub allows you to route and unify these observability data sources for end-to-end analysis.
- C. Incorrect.
INCORRECT: Although Streaming and Functions can handle log ingestion and transformation, this approach requires significant custom setup and does not provide out-of-the-box correlation for metrics and traces.
- D. Incorrect.
INCORRECT: Using an open-source aggregator is possible but adds management overhead and does not natively integrate metrics, logs, and traces in OCI. Logging Analytics can handle logs effectively, but missing native trace correlation would require additional custom work.