Question 1
Why are Kubernetes Services necessary when Pods already have IP addresses?
Pod IPs are not routable
Pod IPs change frequently due to Pod recreation
Pod IPs cannot handle traffic
Pod IPs are shared across nodes
Question 2
What is the primary role of a selector in a Kubernetes Service?
Assign a ClusterIP to the Service
Filter traffic at the ingress level
Identify the set of Pods backing the Service
Configure DNS records
Question 3
What happens when a Service is created without a selector?
The Service becomes headless automatically
Kubernetes creates Pods automatically
The Service cannot receive traffic
Endpoints must be managed manually via EndpointSlices
Question 4
Why were EndpointSlices introduced instead of using a single Endpoints object?
To support encrypted traffic
To reduce API server load by segmenting large endpoint sets
To replace Services
To allow multi-port Services
Question 5
Which Service type exposes Pods directly without allocating a ClusterIP?
ExternalName
NodePort
LoadBalancer
Headless
Question 6
In a NodePort Service, which component actually forwards traffic from the node port to Pod IPs?
kube-proxy
kube-scheduler
API Server
CoreDNS
Question 7
Why can a LoadBalancer Service behave differently in Minikube compared to a managed cloud cluster?
Minikube blocks external traffic
Minikube lacks a cloud provider integration for external load balancers
Minikube uses only UDP
Minikube does not support Services
Question 8
What is the advantage of using named ports instead of numeric targetPort values?
Faster networking
Improved security
Decoupling Service configuration from container port numbers
Automatic port discovery
Question 9
Which DNS record type is created when using an ExternalName Service?
A record
AAAA record
SRV record
CNAME record
There are 9 questions to complete.