You have an Azure Active Directory (Azure AD) tenant named Contoso.com and an Azure Kubernetes Service (AKS) cluster AKS1. You discover that AKS1 cannot be accessed by using accounts from…

Question

Options

• AFrom Azure recreate AKS1.
• BFrom AKS1, upgrade the version of Kubernetes.
• CFrom Azure AD, implement Azure AD Premium.
• DFrom Azure AD, configure the User settings.

• A
  71% (22)
• B
  16% (5)
• C
  6% (2)
• D
  6% (2)

Explanation

Explanation

Recreating AKS1 is necessary because Azure AD integration must be configured at the time of AKS cluster creation - it cannot be enabled on an existing cluster after deployment. If the original cluster was provisioned without Azure AD integration, the only way to enable it (with minimal administrative effort) is to recreate the cluster with the Azure AD integration setting enabled during setup.

Why the distractors are wrong:

• Option B is incorrect because upgrading the Kubernetes version has no bearing on Azure AD authentication - these are entirely separate concerns.
• Option C is incorrect because Azure AD Premium is not required for AKS to authenticate users; basic Azure AD integration works with the free tier.
• Option D is incorrect because configuring User settings in Azure AD won't resolve the underlying issue - the cluster itself lacks the Azure AD integration configuration.

Memory Tip: Think of AKS + Azure AD like a foundation - you can't add it to a building after it's built; you must include it from the ground up. If you see an AKS authentication problem with Azure AD, immediately ask yourself, "Was it configured at creation?" If not, a rebuild is the fix.

No community discussion yet for this question.