Bird
0
0

Why is it recommended to avoid storing large binary files in Kubernetes Secrets?

hard📝 Conceptual Q10 of 15
Microservices - Orchestration with Kubernetes
Why is it recommended to avoid storing large binary files in Kubernetes Secrets?
ASecrets cannot store binary data, only text
BKubernetes automatically deletes large Secrets after 1 hour
CSecrets are base64 encoded and stored in etcd, increasing storage and performance overhead
DLarge files cause Secrets to become read-only
Step-by-Step Solution
Solution:

  1. Step 1: Understand Secret storage mechanism

    Secrets are base64 encoded and stored in etcd, the Kubernetes cluster database.

  2. Step 2: Consider impact of large binary data

    Storing large binaries increases etcd size, causing performance and storage issues.

  3. Final Answer:

    Secrets are base64 encoded and stored in etcd, increasing storage and performance overhead -> Option C

  4. Quick Check:

    Large binary in Secrets causes etcd overhead = C [OK]
Quick Trick: Avoid large binaries in Secrets to protect etcd performance [OK]
Common Mistakes:
MISTAKES
  • Believing Secrets auto-delete large data
  • Thinking Secrets cannot store binary data
  • Assuming large files make Secrets read-only

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Microservices Quizzes
Authentication and Authorization - Role-based access control - Quiz 4medium Event-Driven Architecture - Eventual consistency handling - Quiz 15hard Monitoring and Observability - Correlation IDs - Quiz 15hard Monitoring and Observability - Metrics collection (Prometheus) - Quiz 7medium Monitoring and Observability - Distributed tracing (Jaeger, Zipkin) - Quiz 3easy Orchestration with Kubernetes - Pods and deployments for services - Quiz 13medium Resilience Patterns - Timeout pattern - Quiz 15hard Resilience Patterns - Bulkhead pattern - Quiz 3easy Service Mesh - Service mesh concept - Quiz 1easy Service Mesh - Istio overview - Quiz 12easy