If the --authorization-mode flag is not specified when starting the Kubernetes API server, what default mode is used?

If the --authorization-mode flag is not specified when starting the Kubernetes API server, what default mode is used?

• A. RBAC
• B. AlwaysAllow
• C. ABAC
• D. Node

Answer: (B)

When the API server starts, it needs to know how to authorize requests. If you don’t specify the --authorization-mode flag, Kubernetes uses AlwaysAllow by default. That means the API server allows all requests unless something else blocks them, which is convenient for initial setup but insecure for production. To enforce access controls, you should explicitly set a mode like RBAC or ABAC (or combine modes such as RBAC,Node). The other options listed are valid modes, but they’re not the default; they require explicit configuration.

When the API server starts, it needs to know how to authorize requests. If you don’t specify the --authorization-mode flag, Kubernetes uses AlwaysAllow by default. That means the API server allows all requests unless something else blocks them, which is convenient for initial setup but insecure for production. To enforce access controls, you should explicitly set a mode like RBAC or ABAC (or combine modes such as RBAC,Node). The other options listed are valid modes, but they’re not the default; they require explicit configuration.