Bird
0
0

Why is Fluentd preferred over direct log shipping to Elasticsearch in Kubernetes EFK setups?

hard📝 Conceptual Q10 of 15
Kubernetes - Monitoring and Logging
Why is Fluentd preferred over direct log shipping to Elasticsearch in Kubernetes EFK setups?
AFluentd replaces Kibana for visualization
BFluentd stores logs permanently unlike Elasticsearch
CFluentd buffers logs and handles retries, improving reliability
DFluentd runs only on master nodes, reducing overhead
Step-by-Step Solution
Solution:

  1. Step 1: Understand Fluentd's role in log shipping

    Fluentd buffers logs locally and retries sending on failure, ensuring no data loss.

  2. Step 2: Clarify misconceptions

    Elasticsearch stores logs permanently; Kibana visualizes logs; Fluentd runs on all nodes, not just master.

  3. Final Answer:

    Fluentd buffers logs and handles retries, improving reliability -> Option C

  4. Quick Check:

    Fluentd adds reliability via buffering and retries [OK]
Quick Trick: Fluentd buffers and retries logs for reliability [OK]
Common Mistakes:
  • Thinking Fluentd stores logs permanently
  • Confusing Fluentd with Kibana
  • Assuming Fluentd runs only on master nodes

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Advanced Deployment Patterns - Why advanced patterns matter - Quiz 12easy Advanced Deployment Patterns - Feature flags in Kubernetes - Quiz 13medium Helm Package Manager - Helm charts concept - Quiz 8hard Helm Package Manager - Why Helm simplifies deployments - Quiz 12easy Monitoring and Logging - Why cluster monitoring matters - Quiz 10hard RBAC and Security - Secrets encryption at rest - Quiz 6medium Service Mesh - Mutual TLS for service communication - Quiz 12easy Service Mesh - Traffic management with Istio - Quiz 6medium Service Mesh - Linkerd as lightweight alternative - Quiz 8hard Troubleshooting - Node troubleshooting - Quiz 13medium