Which security capability in Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE) enables developers to scope IAM permissions at the individual service account level for application pods rather than the host Compute instances?
Correct Answer: C
OKE Workload Identity enables applications running in Kubernetes pods to receive fine-grained OCI IAM permissions based on their Kubernetes identity rather than inheriting broad permissions from the worker node.
Oracle defines a workload identity using the combination of the OKE cluster, Kubernetes namespace, and Kubernetes service account. IAM policies can therefore restrict access to a specific workload using conditions such as request.principal.type= ' workload ' , request.principal.namespace, request.principal.service_account, and request.principal.cluster_id. Instance Principals grant identity to Compute instances, while Kubernetes RBAC controls access to Kubernetes resources rather than OCI services. Resource Principals apply to supported OCI resources but do not provide OKE ' s service-account-specific pod identity model. Thus, Workload Identity is the correct capability.