The correct answer is: A. To provide clearer role separation between infrastructure providers and application developers. The Gateway API improves on traditional Ingress by separating responsibilities: GatewayClass → usually managed by platform/infrastructure team Gateway → usually managed by cluster/network team HTTPRoute → usually managed by application team Why not the others? B — A Service alone does not provide advanced external routing like Gateway API. C — annotation-heavy routing is a limitation of traditional Ingress, not an advantage of Gateway API. D — autoscaling is handled by HPA/VPA/KEDA, not Gateway API. Answer: A.