A library runs on a cloud Kubernetes environment and wants the platform to provision an external load balancer IP for a public web Service. Which Service type requests that?
Select an answer to reveal the explanation.
Short Explanation
Want the cloud to hand you a public LB address? Type LoadBalancer — ClusterIP and headless won't place that order.
Full Explanation
A library running on a cloud Kubernetes environment that wants the platform to provision an external load balancer IP for a public web Service should use type LoadBalancer, which asks the cloud or environment integration to provision an external load balancer fronting the Service. That is the Service type that places the order for an external address via cloud controller manager or equivalent integration for citizen-facing library sites.
ClusterIP with externalTrafficPolicy Local does not force the cloud to allocate a public LB. Headless Services do not instruct the CCM to publish Network Load Balancer hostnames in Endpoints as described. NodePort with sessionAffinity None is not synonymous with LoadBalancer on all providers.
Exam caveat: LoadBalancer usually implies NodePort allocation underneath on many clouds; absence of a cloud integration leaves the Service pending an external IP. Operational check: create the LoadBalancer Service, wait for EXTERNAL-IP, and verify public HTTPS to the library site. This distinction matters on the CKA because distractors often mix adjacent objects that sound related but solve a different control-plane problem. This distinction matters on the CKA because distractors often mix adjacent objects that sound related but solve a different control-plane problem.