Which option correctly places the default service account as the Pod's automatically assigned account when none is specified?

Which option correctly places the default service account as the Pod's automatically assigned account when none is specified?

• A. system
• B. serviceaccount
• C. root
• D. default

Answer: (D)

When a Pod is created without specifying a serviceAccountName, Kubernetes automatically binds it to the namespace’s default service account. Each namespace has a default service account named default, which provides the Pod with an identity to access the API server. The credentials for this account are mounted into the Pod, enabling API calls as that identity, unless you override it by setting serviceAccountName explicitly. The other options don’t fit: system and root aren’t standard default service account names, and serviceaccount is a resource type, not a name. So the correct choice is the default service account named default.

When a Pod is created without specifying a serviceAccountName, Kubernetes automatically binds it to the namespace’s default service account. Each namespace has a default service account named default, which provides the Pod with an identity to access the API server. The credentials for this account are mounted into the Pod, enabling API calls as that identity, unless you override it by setting serviceAccountName explicitly.

The other options don’t fit: system and root aren’t standard default service account names, and serviceaccount is a resource type, not a name. So the correct choice is the default service account named default.