How does an OpenShift Route expose a service externally and what is the role of the Route host?

• A. Route creates a LoadBalancer; host is internal.
• B. Route uses NodePort; host defines the node address.
• C. Route exports via Ingress resource; host is ignored.
• D. Create a Route that points to the service; spec.host defines public hostname; DNS must resolve to the OpenShift router.

Answer: (D)

OpenShift Route exposes a service externally by creating a Route that points to that service, with the OpenShift router handling the external traffic. The host specified in the Route is the public hostname that clients will use to access the service; DNS must resolve that hostname to the router’s address so requests reach the router, which then forwards them to the service. This setup is how the external endpoint is defined and reached. The router can also terminate TLS for that host if configured. Other mechanisms like directly using a LoadBalancer or NodePort don’t define the external hostname and routing in the same way, and the host in the Route isn’t ignored—it’s essential for directing traffic to the right service.