In IBM Cloud Pak for Integration (CP4I) v2021.2, which runs on OpenShift Container Platform (OCP), administrators can configure log forwarding to an external log aggregator (e.g., Elasticsearch, Splunk, or Loki).
OCP uses Fluentd as the log collector, and when log forwarding fails due to the external logging aggregator becoming unavailable, the following happens:
Fluentd buffers the logs in memory (up to a defined limit).
If the buffer reaches its maximum size, OCP follows its default log management policy:
Older logs are rotated and deleted to make space for new logs.
This prevents excessive storage consumption on the OpenShift cluster.
This behavior ensures that the logging system does not stop functioning but rather manages storage efficiently by deleting older logs once the buffer is full.
Log rotation is a default behavior in OCP when storage limits are reached.
If logs cannot be forwarded and the buffer is full, OCP deletes old logs to continue operations.
This is a standard logging mechanism to prevent resource exhaustion.
Why Answer A is Correct?
B. OCP stores the logs in a temporary PVC. → Incorrect
OCP does not automatically store logs in a Persistent Volume Claim (PVC).
Logs are buffered in memory and not redirected to PVC storage unless explicitly configured.
C. OCP extends the buffer size and resumes log collection. → Incorrect
The buffer size is fixed and does not dynamically expand.
Instead of increasing the buffer, older logs are rotated out when the limit is reached.
D. The Fluentd daemon is forced to stop. → Incorrect
Fluentd does not stop when the external log aggregator is down.
It continues collecting logs, buffering them until the limit is reached, and then follows log rotation policies.
Explanation of Incorrect Answers:
IBM Cloud Pak for Integration Logging and Monitoring
OpenShift Logging Overview
Fluentd Log Forwarding in OpenShift
OpenShift Log Rotation and Retention Policy
IBM Cloud Pak for Integration (CP4I) v2021.2 Administration References:
Submit