Option A is correct because it outlines the appropriate method to expose the application to the public using HTTPS over a public IP address in GKE. A NodePort service makes the application accessible on a static port across all nodes, and an ingress resource with a load balancer facilitates external HTTPS access. Option B is incorrect as a ClusterIP service restricts access to within the cluster, and using its IP for public DNS does not enable HTTPS access. Option C is inefficient and unscalable, requiring manual DNS configuration with each node's IP. Option D introduces unnecessary complexity and lacks the scalability and flexibility of a load balancer. For more details, refer to GKE Ingress and GKE Service.