Which step does not belong in the path a request to the Kubernetes API follows?

Which step does not belong in the path a request to the Kubernetes API follows?

• A. Authentication
• B. Network Optimization
• C. Authorization
• D. Admission Control

Answer: (B)

Kubernetes processes an API request through a specific pipeline: first the API server authenticates to verify who is making the request, then it authorizes to check whether that identity is allowed to perform the requested action, and next it runs admission controllers to validate or mutate the object before it is stored. If all of these steps pass, the object is written to etcd and the request completes. This sequence ensures only legitimate actions proceed and that policies and defaults are enforced before any data is persisted. Network optimization, while important for overall cluster performance, is not a step in this API request handling path. Networking concerns—routing, load balancing, and network performance—occur outside the API server’s request processing pipeline and do not form part of the authentication/authorization/admission flow.

Kubernetes processes an API request through a specific pipeline: first the API server authenticates to verify who is making the request, then it authorizes to check whether that identity is allowed to perform the requested action, and next it runs admission controllers to validate or mutate the object before it is stored. If all of these steps pass, the object is written to etcd and the request completes. This sequence ensures only legitimate actions proceed and that policies and defaults are enforced before any data is persisted.

Network optimization, while important for overall cluster performance, is not a step in this API request handling path. Networking concerns—routing, load balancing, and network performance—occur outside the API server’s request processing pipeline and do not form part of the authentication/authorization/admission flow.