Exam AZ-500 topic 3 question 42 discussion

Answer is correct The following limitations apply: Azure AD can only be enabled on Kubernetes RBAC-enabled cluster. Azure AD legacy integration can only be enabled during cluster creation.

A is correct - though question has been repeated

A You cannot enable AAD integration on an existing AKS cluster unless it was originally created with that option or manually configured (which is more complex and not recommended for minimizing effort). AKS supports Azure AD integration for Kubernetes RBAC only if specified at creation time (or with significant manual steps afterward, which contradicts the “minimize administrative effort” requirement). Options like enabling AAD Premium P2 or changing user settings in Azure AD do not directly resolve the issue of an AKS cluster not being accessible via AAD.

D. From Azure AD, configure the User settings. Here's why: Azure AD Authentication for AKS: Azure AD can be used to enable Azure AD authentication for AKS clusters. This allows users in your Azure AD tenant to access the AKS cluster without needing to manage additional Kubernetes RBAC users. In this case, you need to ensure that the proper User settings are configured in Azure AD to enable access from the users in your tenant. Implementation Steps: You'll need to configure AKS to integrate with Azure AD for Kubernetes RBAC, which involves setting up Azure AD authentication and ensuring that the correct users from Contoso.com are allowed to access the AKS cluster.

Deprecated question it seems

To ensure that AKS1 can be accessed by accounts from Contoso.com, you should: C. From Azure AD, implement Azure AD Premium P2 Explanation: Azure AD Premium P2: Azure AD Premium P2 provides advanced identity protection capabilities, including features such as Conditional Access and Identity Protection. These features can be essential for securing access to resources, including AKS clusters.

Answer: A Explanation: you can only integrate AAD with AKS during cluster creation time (using --enable-aad in your CLI code), not after it has been created. Reference: https://docs.microsoft.com/en-us/azure/aks/azure-ad-integration-cli

A. From Azure, recreate AKS1.

A. From Azure, recreate AKS1.

A is correct answer.

# IN EXAM - 3rd june 2022 (online). Lot of new questions. Good luck !

it is now a legacy feature, this can be enabled on existing aks https://docs.microsoft.com/en-us/azure/aks/managed-aad#enable-aks-managed-azure-ad-integration-on-your-existing-cluster

Exam - 4/11/21

Today's exam 20/10/21..

In Exam 8/4/2021

Azure AD can only be enabled on Kubernetes RBAC-enabled cluster. Azure AD legacy integration can only be enabled during cluster creation.

As of today, you can only integrate AAD with AKS during cluster creation time (using --enable-aad in your CLI code), not after it has been created. So Ans A is correct.