When a Pod is deployed without an explicitly assigned Service Account, which Service Account is automatically assigned?

When a Pod is deployed without an explicitly assigned Service Account, which Service Account is automatically assigned?

• A. system
• B. default
• C. default-serviceaccount
• D. pod

Answer: (B)

When you don’t specify a Service Account for a Pod, Kubernetes binds the Pod to the default Service Account in that Pod’s namespace. Every namespace includes a default Service Account named default, and Kubernetes will attach this SA to the Pod automatically, mounting its credentials so the Pod can interact with the Kubernetes API (unless you override it with a different serviceAccountName). The other names listed aren’t standard Service Accounts in Kubernetes, so they wouldn’t be used by default.

When you don’t specify a Service Account for a Pod, Kubernetes binds the Pod to the default Service Account in that Pod’s namespace. Every namespace includes a default Service Account named default, and Kubernetes will attach this SA to the Pod automatically, mounting its credentials so the Pod can interact with the Kubernetes API (unless you override it with a different serviceAccountName). The other names listed aren’t standard Service Accounts in Kubernetes, so they wouldn’t be used by default.