1Z0-1067-25 Question 119
Single answerAn operations team manages a microservices-based application deployed on Oracle Container Engine for Kubernetes (OKE). They need to aggregate container logs centrally and perform advanced analytics across logs from multiple pods. Which method would best help them gather and analyze these logs in Oracle Logging Analytics for end-to-end observability?
- A
Deploy and manage the Oracle Logging Analytics Agent on each running container in OKE.
- B
Enable cluster-level logging to send container and pod logs to OCI Logging, then configure a Service Connector to forward these logs to Logging Analytics.
- C
Configure OCI Cloud Guard to collect logs automatically and ingest them into Logging Analytics.
- D
Take manual snapshots of the container file system and upload them into Logging Analytics.
Show answer and explanation
Correct answer: B
Explanation
Using OCI Logging in conjunction with Logging Analytics is a common best practice for achieving centralized observability. By enabling cluster-level logging in Oracle Container Engine for Kubernetes (OKE) and then setting up a Service Connector, administrators can seamlessly ingest logs into Logging Analytics. This allows for efficient retention, searching, and advanced log correlation across microservices. Refer to the official Oracle Logging Analytics and OKE documentation for detailed steps on configuring cluster-level logging and Service Connector Hub for log forwarding.
- A. Incorrect.
Option 1 is incorrect because installing the Agent inside each container can be unnecessarily complex, difficult to maintain, and is not the recommended approach. Typically, you deploy the Agent on a node or VM, not on every container.
- B. Correct.
Option 2 is correct. Configuring the OKE cluster-level logging to send container logs to OCI Logging and then using a Service Connector to route those logs to Logging Analytics is a recommended design. It centralizes the log collection and leverages OCI native integrations for easier maintenance and efficient log analysis.
- C. Incorrect.
Option 3 is incorrect. OCI Cloud Guard is a security-focused service used to detect and respond to misconfigurations and security issues. It is not designed to serve as the primary log collection mechanism for Observability.
- D. Incorrect.
Option 4 is incorrect. Manually taking container snapshots and uploading them is impractical for real-time log collection and does not provide automated or continuous observability.