Which option is NOT a primary service type in Kubernetes?

Which option is NOT a primary service type in Kubernetes?

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

Answer: (B)

Kubernetes services are exposed in specific ways defined by their type, which determines how clients reach the service. The valid service types are ClusterIP, NodePort, LoadBalancer, and ExternalName. ClusterIP is the default and enables intra-cluster access; NodePort opens a static port on each node to expose the service externally through the node IPs; LoadBalancer asks the cloud provider to provision an external load balancer that routes to the service; ExternalName maps the service to an external DNS name. The option named SwitchBalancer is not a recognized service type in Kubernetes, so it isn’t a primary service type. The other choices correspond to real service types, whereas SwitchBalancer does not exist in this context.

Kubernetes services are exposed in specific ways defined by their type, which determines how clients reach the service. The valid service types are ClusterIP, NodePort, LoadBalancer, and ExternalName. ClusterIP is the default and enables intra-cluster access; NodePort opens a static port on each node to expose the service externally through the node IPs; LoadBalancer asks the cloud provider to provision an external load balancer that routes to the service; ExternalName maps the service to an external DNS name. The option named SwitchBalancer is not a recognized service type in Kubernetes, so it isn’t a primary service type. The other choices correspond to real service types, whereas SwitchBalancer does not exist in this context.