1Z0-997-25 Question 156
Select 2Your organization has deployed a microservices-based application on Oracle Container Engine for Kubernetes (OKE). The operations team wants to implement a centralized observability solution to collect, analyze, and visualize logs and metrics from all microservices in near real-time. They also need the ability to set automated alerts and quickly drill down for root cause analysis. Which TWO configurations are recommended to establish a robust observability solution in this scenario?
- A
Enable OCI Logging for OKE and configure a Service Connector Hub to automatically forward logs to Logging Analytics.
- B
Install a third-party agent directly on each container to stream logs to an external open-source logging platform.
- C
Export logs to Object Storage using the default OKE settings and manually retrieve them for analysis.
- D
Create custom Log Groups in OCI Logging to separate microservice logs and configure alarms in OCI Monitoring.
- E
Rely on default Kubernetes logging to stdout and only monitor workloads using basic kubectl logs commands.
Show answer and explanation
Correct answers: A, D
Explanation
In Oracle Cloud Infrastructure, a recommended best practice for observability is to leverage native OCI Logging, Logging Analytics, and OCI Monitoring to collect and analyze logs and metrics in real-time. Configuring Service Connector Hub for automated log forwarding to Logging Analytics, and using custom Log Groups with appropriate alarms in OCI Monitoring, helps unify log storage, visualization, alerting, and deep diagnostics. For further guidance, refer to OCI Logging, Logging Analytics, and Monitoring documentation.
- A. Correct.
Option 1 is CORRECT. Enabling OCI Logging at the cluster level and using Service Connector Hub to forward logs to Logging Analytics provides centralized log collection and advanced analytics. This approach eliminates the need to manage multiple custom agents and allows you to configure alerts and dashboards in OCI.
- B. Incorrect.
Option 2 is INCORRECT. While third-party agents can collect logs, Oracle recommends using native OCI Logging for easier management, security, and integration with Logging Analytics. This approach reduces overhead and leverages built-in OCI features.
- C. Incorrect.
Option 3 is INCORRECT. Exporting logs solely to Object Storage for manual retrieval does not provide near real-time visibility or out-of-the-box analytics capabilities. This approach is suitable for archiving, but it doesn�t fulfill the requirement for real-time monitoring and alerts.
- D. Correct.
Option 4 is CORRECT. Creating custom Log Groups in OCI Logging allows you to organize logs by microservice or functionality. Pairing this with OCI Monitoring alarms ensures you can set proactive alerts for log patterns and anomalies. This combination supports a comprehensive observability strategy.
- E. Incorrect.
Option 5 is INCORRECT. Relying only on stdout and kubectl logs provides minimal basic logging. This method does not allow for advanced correlation, visualization, and alerting. It also does not meet the requirement for a centralized observability platform.