What is the default Kubernetes service type?

What is the default Kubernetes service type?

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

Answer: (D)

The main idea tested here is how Kubernetes controls who can access a Service by its type. When you create a Service without specifying a type, it defaults to ClusterIP. This means Kubernetes assigns an internal cluster IP and creates a DNS entry, so the service is reachable only from within the cluster. It stays isolated from external clients by design, which is ideal for internal communication between Pods. If you need external access, you’d explicitly set a different type, such as NodePort or LoadBalancer, or use Ingress, or map to an external resource with ExternalName.

The main idea tested here is how Kubernetes controls who can access a Service by its type. When you create a Service without specifying a type, it defaults to ClusterIP. This means Kubernetes assigns an internal cluster IP and creates a DNS entry, so the service is reachable only from within the cluster. It stays isolated from external clients by design, which is ideal for internal communication between Pods.

If you need external access, you’d explicitly set a different type, such as NodePort or LoadBalancer, or use Ingress, or map to an external resource with ExternalName.