Bird
0
0

Why might an Ingress controller use a default TLS certificate when the specified secret is missing or invalid?

hard📝 Conceptual Q10 of 15
Kubernetes - Ingress
Why might an Ingress controller use a default TLS certificate when the specified secret is missing or invalid?
ATo avoid dropping HTTPS connections and allow clients to connect with warnings
BBecause Kubernetes automatically generates valid certificates for all Ingresses
CTo disable TLS and downgrade connections to HTTP automatically
DTo redirect all HTTPS traffic to HTTP endpoints
Step-by-Step Solution
Solution:

  1. Step 1: Understand fallback behavior

    Ingress controllers use default certs to keep HTTPS connections alive even if custom certs fail.

  2. Step 2: Explain client impact

    Clients see warnings but can still connect instead of connection failures.

  3. Final Answer:

    To avoid dropping HTTPS connections and allow clients to connect with warnings -> Option A

  4. Quick Check:

    Default cert fallback = keep HTTPS alive with warnings [OK]
Quick Trick: Default cert prevents connection drops, causes warnings [OK]
Common Mistakes:
  • Thinking Kubernetes auto-generates valid certs
  • Assuming fallback disables TLS
  • Believing fallback redirects to HTTP

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
ConfigMaps - Using ConfigMaps as mounted volumes - Quiz 12easy ConfigMaps - Updating ConfigMaps and propagation - Quiz 11easy Health Checks and Probes - HTTP probe configuration - Quiz 11easy Ingress - Ingress controllers (Nginx, Traefik) - Quiz 7medium Networking - Why Kubernetes networking matters - Quiz 14medium Persistent Storage - PersistentVolume (PV) definition - Quiz 8hard Persistent Storage - Volumes vs Persistent Volumes - Quiz 13medium Resource Management - Horizontal Pod Autoscaler - Quiz 14medium Resource Management - Memory requests and limits - Quiz 12easy Secrets - Base64 encoding in Secrets - Quiz 9hard