Which Kubernetes service type is dependent on your Kubernetes offering and may vary significantly between On-Prem and Cloud?

Which Kubernetes service type is dependent on your Kubernetes offering and may vary significantly between On-Prem and Cloud?

• A. ClusterIP
• B. ExternalName
• C. LoadBalancer
• D. NodePort

Answer: (C)

This item tests how external access for a service is provisioned and how that changes with the environment. A LoadBalancer service asks the cluster to provision an external load balancer for the service. In cloud environments, the cloud provider integration creates a real external load balancer and assigns a public IP or DNS, routing traffic to the service across nodes. In on‑prem deployments, there’s no built‑in cloud controller to create such a resource, so you must deploy and configure an external load balancer yourself (like MetalLB or a hardware/software solution), with environment‑specific IP ranges, health checks, and integration steps. That makes this service type highly dependent on the underlying infrastructure and can vary significantly between on‑prem and cloud setups. Other service types don’t rely on an external load balancer in the same way: ClusterIP stays internal to the cluster, ExternalName points to an external DNS name, and NodePort exposes a port on each node but doesn’t automatically provision an external load balancer.

This item tests how external access for a service is provisioned and how that changes with the environment. A LoadBalancer service asks the cluster to provision an external load balancer for the service. In cloud environments, the cloud provider integration creates a real external load balancer and assigns a public IP or DNS, routing traffic to the service across nodes. In on‑prem deployments, there’s no built‑in cloud controller to create such a resource, so you must deploy and configure an external load balancer yourself (like MetalLB or a hardware/software solution), with environment‑specific IP ranges, health checks, and integration steps. That makes this service type highly dependent on the underlying infrastructure and can vary significantly between on‑prem and cloud setups. Other service types don’t rely on an external load balancer in the same way: ClusterIP stays internal to the cluster, ExternalName points to an external DNS name, and NodePort exposes a port on each node but doesn’t automatically provision an external load balancer.