- Courses
- Tutorials
- Practice
- Jobs
Kubernetes-6
Question 1
Why does creating an Ingress resource alone not route traffic in a Kubernetes cluster?
- A
Ingress works only with LoadBalancer services
- B
Ingress requires kube-proxy to be configured
- C
Ingress cannot expose HTTPS traffic
- D
Ingress rules are inert without an Ingress Controller
Question 2
Which Kubernetes component actually performs TLS termination when using Ingress?
- A
Kubernetes API Server
- B
Service
- C
Ingress Resource
- D
Ingress Controller
Question 3
Which routing capability is unique to Ingress when compared to a Service of type LoadBalancer?
- A
TCP traffic handling
- B
UDP traffic handling
- C
Host-based and path-based routing
- D
External IP allocation
Question 4
Why is Ingress often preferred when exposing multiple HTTP services?
- A
It assigns multiple external IPs
- B
It supports only internal traffic
- C
It allows multiple services to share a single IP/domain
- D
It replaces Services entirely
Question 5
How does Ingress remain stable even when backend Pods scale up or down?
- A
By directly tracking Pod IPs
- B
By using Endpoint resources behind Services
- C
By caching DNS entries
- D
By restarting the Ingress Controller
Question 6
Which scenario best justifies using a Service of type LoadBalancer instead of Ingress?
- A
Exposing multiple HTTP paths
- B
Requiring URL rewriting
- C
Handling non-HTTP protocols like UDP or gRPC
- D
Hosting multiple virtual domains
Question 7
What is the main cost-related drawback of using LoadBalancer services extensively?
- A
Slower routing performance
- B
Limited scalability
- C
One cloud load balancer per service
- D
No TLS support
Question 8
In an Ingress architecture, which object acts as the final destination for routed traffic?
- A
Ingress Controller Pod
- B
Endpoint resource
- C
Pod directly
- D
Kubernetes Service
Question 9
Why is modifying /etc/hosts commonly required when testing Ingress on Minikube?
- A
Minikube lacks DNS support
- B
External DNS providers are blocked
- C
Hostname-based routing requires local name resolution
- D
Ingress Controllers require static IPs
Question 10
Which statement best captures the architectural difference between Ingress and LoadBalancer?
- A
Both sit between clients and Pods
- B
Ingress routes traffic inside the cluster, LoadBalancer sits at the edge
- C
LoadBalancer replaces Services
- D
Ingress works without Services
There are 10 questions to complete.