How can you expose a service externally using Route?

• A. Create a Route that targets the Service; the Route exposes an external hostname for the app.
• B. Expose the service by creating a LoadBalancer service of type NodePort.
• C. Expose the service by mounting a Route as a volume.
• D. Expose the service by editing the Route to point to ingress.

Answer: (A)

Exposing a service externally is accomplished by creating a Route that targets the Service. A Route provides an external host name and uses the OpenShift router to forward incoming HTTP/S traffic to the backend Service, which then reaches the pods. This is the standard way to make an application accessible outside the cluster in OpenShift, with the router handling the DNS name and routing rules.

Other approaches don’t fit the Route mechanism: a LoadBalancer-type service can expose traffic, but it uses a different path than a Route; mounting a Route as a volume isn’t meaningful because routes are for network traffic, not storage; and editing a Route to point to ingress isn’t how Routes work since a Route directs traffic to a Service and relies on the OpenShift router rather than Kubernetes Ingress.