The correct option is LoadBalancer.

A Service of type LoadBalancer instructs the cloud provider integration to provision an external load balancer and it automatically allocates an external IP address from the provider's pool and routes traffic to the Service endpoints that back the Pod.

NodePort exposes a static port on each cluster node so clients can reach pods by contacting node IPs and the assigned port. It does not request or receive an external cloud IP automatically and typically requires an external load balancer or other network configuration to be reachable from outside the cluster.

Ingress is an API object for HTTP and HTTPS routing and it is not itself a Service type. An Ingress requires an Ingress Controller to implement the rules and that controller may be exposed via a LoadBalancer or other mechanism. The Ingress resource alone does not automatically allocate a cloud provider external IP.

ClusterIP is the default Service type and it provides internal cluster connectivity only. It does not expose the Service outside the cluster and it does not allocate any external IP address.

Full AWS Practitioner Certification Question