Admission Controllers are invoked after which checks in the API request lifecycle?

Admission Controllers are invoked after which checks in the API request lifecycle?

• A. Authentication and Authorization
• B. Authentication and Validation
• C. Authorization and Validation
• D. Validation and Auditing

Answer: (A)

Requests reach admission controllers only after identity and permission have been established. The API server first authenticates the client to know who they are, then checks authorization to confirm that this user is allowed to perform the requested operation. If those checks pass, the admission chain runs, allowing mutating or validating admission webhooks to inspect, modify, or reject the object before it’s stored. Auditing is a separate logging step that records actions after they occur, not a gating stage for the request. Validation occurs as part of the admission process, but the gating sequence that enables admission is the authentication followed by authorization.

Requests reach admission controllers only after identity and permission have been established. The API server first authenticates the client to know who they are, then checks authorization to confirm that this user is allowed to perform the requested operation. If those checks pass, the admission chain runs, allowing mutating or validating admission webhooks to inspect, modify, or reject the object before it’s stored. Auditing is a separate logging step that records actions after they occur, not a gating stage for the request. Validation occurs as part of the admission process, but the gating sequence that enables admission is the authentication followed by authorization.