The correct approach is to use Azure AD Pod Identity (now evolved into Workload Identity) to assign a managed identity to the pod and authenticate to Azure SQL Database. This method is secure because it eliminates the need to store credentials in the container image or environment variables—instead, the pod obtains an Azure AD token through its assigned managed identity, which is then used to authenticate directly to Azure SQL. On the AZ-204 exam, this scenario tests your understanding of identity-based access for containerized workloads, often appearing as a distractor against options like storing connection strings in Kubernetes secrets or using service principals with client secrets. A common trap is assuming secrets are acceptable, but the exam emphasizes zero-trust credential management. Remember: pods get tokens, not passwords—think “identity, not secret” to avoid the trap.
AZ-204 Implement Azure security Practice Question
This AZ-204 practice question tests your understanding of implement azure security. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You are deploying a containerized application to Azure Kubernetes Service (AKS). The application needs to access Azure SQL Database securely. Which approach should you use to avoid storing credentials in the container image?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Azure AD Pod Identity (Workload Identity) to assign a managed identity to the pod and authenticate to SQL
Option B is correct because Azure AD Pod Identity (now evolved into Workload Identity) allows you to assign a managed identity to a pod, which can then authenticate to Azure SQL Database without any credentials stored in the image or environment variables. This approach uses Azure AD tokens obtained via the pod's identity, eliminating the need for connection strings or secrets in the container.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Store the connection string in a Kubernetes Secret and mount it as an environment variable
Why it's wrong here
Secrets are base64 encoded but not encrypted by default; this is not the most secure approach.
✓
Use Azure AD Pod Identity (Workload Identity) to assign a managed identity to the pod and authenticate to SQL
Why this is correct
Workload Identity integrates with AKS to provide managed identities to pods, eliminating the need for stored credentials.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use a service principal and store its credentials in Azure Key Vault, then use the Key Vault Secrets Store CSI driver
Why it's wrong here
This is valid but more complex than Workload Identity for AKS.
✗
Hardcode the credentials in the Dockerfile
Why it's wrong here
Hardcoding credentials is a security risk and should never be done.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often choose Option A (Kubernetes Secret) because it seems like a standard Kubernetes pattern, but they overlook that the question specifically requires avoiding any credential storage in the image or environment, which a Secret still represents.
Detailed technical explanation
How to think about this question
Under the hood, Azure AD Pod Identity works by injecting an Azure AD token into the pod via the Azure Identity mutating admission webhook, which the pod can then use to authenticate to Azure SQL using an access token instead of a username/password. The token is obtained using the Azure Identity SDK (e.g., DefaultAzureCredential) and is valid for a limited time, requiring automatic refresh. In a real-world scenario, this approach also simplifies credential rotation and auditing, as the managed identity is tied to the pod's lifecycle and can be granted granular permissions via Azure RBAC.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-204 question in full detail.
Implement Azure security — This question tests Implement Azure security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use Azure AD Pod Identity (Workload Identity) to assign a managed identity to the pod and authenticate to SQL — Option B is correct because Azure AD Pod Identity (now evolved into Workload Identity) allows you to assign a managed identity to a pod, which can then authenticate to Azure SQL Database without any credentials stored in the image or environment variables. This approach uses Azure AD tokens obtained via the pod's identity, eliminating the need for connection strings or secrets in the container.
What should I do if I get this AZ-204 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.