AZ-500 · Question #627
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…
The correct answer is B. No. The provided solution of assigning the Kubernetes Agentless Operator role to the AKS agent pool's managed identity does not grant the necessary permissions for AKS to pull images from Azure Container Registry. This role is intended for security scanning and does not include…
Question
Options
- AYes
- BNo
How the community answered
(20 responses)- A15% (3)
- B85% (17)
Why each option
The provided solution of assigning the Kubernetes Agentless Operator role to the AKS agent pool's managed identity does not grant the necessary permissions for AKS to pull images from Azure Container Registry. This role is intended for security scanning and does not include data pull permissions for container registries.
Assigning the Kubernetes Agentless Operator role to the AKS agent pool's managed identity does not provide the necessary data pull permissions from an Azure Container Registry.
The Kubernetes Agentless Operator role is primarily used by Azure Defender for Cloud for agentless vulnerability scanning of Kubernetes clusters and does not include permissions to pull container images from an Azure Container Registry. To deploy images from an Azure Container Registry, the AKS cluster's managed identity requires a data-access role like AcrPull on the registry.
Concept tested: AKS image pull permissions from ACR
Source: https://learn.microsoft.com/en-us/azure/defender-for-cloud/permissions-roles#kubernetes-agentless-operator
Topics
Community Discussion
No community discussion yet for this question.