1Z0-997-25 Question 168
Single answerYou manage a microservices-based application running on multiple Oracle Cloud Infrastructure (OCI) compartments. The application experiences sporadic timeouts, and your team needs a unified way to correlate logs and metrics across all microservices while preserving compartment security boundaries. Which approach would best enable centralized logging, efficient analytics, and secure separation of data?
- A
Use the default OCI Logging service in each compartment, then periodically export logs to an external aggregator for index and search
- B
Configure a single Logging Analytics instance in a central compartment and create log groups in each compartment that feed into this instance
- C
Create a Service Connector in each compartment to send logs to OCI Monitoring, then rely on alarm triggers to investigate correlated issues
- D
Combine all microservices into one compartment to unify logs in a single place and then enable Logging Analytics
Show answer and explanation
Correct answer: B
Explanation
Centralizing logs in OCI Logging Analytics while preserving compartment boundaries is a standard best practice for multi-compartment applications. Each compartment sends logs to a central Logging Analytics instance, leveraged for advanced correlation, visualization, and analysis. Detailed steps and guidelines can be found in the Oracle Cloud Infrastructure Observability and Management documentation, which provides recommended architecture patterns, including how to organize log groups, configure log sources, and set up logging policies for secure cross-compartment data collection.
- A. Incorrect.
Option 1 is incorrect because periodically exporting logs to an external aggregator does not provide real-time correlation and can be more operationally complex. The Observability platform in OCI allows centralized, near real-time log collection and analysis within Logging Analytics, so exporting logs manually is less efficient.
- B. Correct.
Option 2 is correct. By configuring Logging Analytics in a single compartment and defining log groups in each microservice's compartment, you can maintain compartment-level security while still centralizing logs for analytics. This approach is cost-effective, provides near real-time correlation, and exploits OCI Observability best practices.
- C. Incorrect.
Option 3 is incorrect because sending logs to OCI Monitoring via Service Connector alone is not sufficient for log correlation or in-depth log analysis. OCI Monitoring focuses on metrics and alarms, while Logging Analytics is designed for comprehensive log management and correlation.
- D. Incorrect.
Option 4 is incorrect because moving everything into a single compartment compromises the design principle of compartment-based isolation and least privilege. It can also complicate governance and cost tracking, as departments or teams often require separate compartments.