In the path a request to the Kubernetes API follows, which step occurs immediately after Authorization?

In the path a request to the Kubernetes API follows, which step occurs immediately after Authorization?

• A. Authentication
• B. Admission Control
• C. Validation
• D. Auditing

Answer: (B)

When a request hits the Kubernetes API server, it first authenticates the caller, then checks what the caller is allowed to do (authorization). Immediately after this, the request enters admission control. Admission controllers enforce cluster policies and can mutate the object or reject the request before it’s stored. Auditing is for logging the event, and validation is handled within the admission phase (mutating/validating webhooks) rather than as a separate step in the direct path. So admission control is the next step after authorization because it gates the request with policy hooks before any persistence.

When a request hits the Kubernetes API server, it first authenticates the caller, then checks what the caller is allowed to do (authorization). Immediately after this, the request enters admission control. Admission controllers enforce cluster policies and can mutate the object or reject the request before it’s stored. Auditing is for logging the event, and validation is handled within the admission phase (mutating/validating webhooks) rather than as a separate step in the direct path. So admission control is the next step after authorization because it gates the request with policy hooks before any persistence.