An application platform team wants routing rules managed by platform operators while letting app teams define routes. Which statement about Gateway API is accurate for this goal?

The correct answer highlights a key benefit of Gateway API: its resource model. It separates the infrastructure concerns (like the Gateway resource, which defines where traffic enters the cluster and is managed by platform operators) from application-specific routing rules (like HTTPRoute resources, which define how traffic is handled for a service and can be managed by application teams). This separation of concerns allows for delegated management, meeting the requirement of platform operators managing routing rules while app teams define routes. Incorrect options: Gateway API supports L7 routing (HTTP/HTTPS) and can terminate TLS, making the statement about L4-only routing and no TLS termination false. Gateway API does not require GKE Hub registration to function between namespaces; its core functionality is independent of GKE Hub. Gateway API allows HTTPRoute resources to be defined in different namespaces than the Gateway resource, provided the Gateway allows binding from those namespaces, making the statement about forced same-namespace definition incorrect.