The answer is to implement the AKS Secret Store CSI Driver with pod-managed identities. This solution is correct because it enables you to restrict pod access to Azure Key Vault secrets by mounting secrets directly into specific pods through a CSI volume, using a pod-managed identity to authenticate to Key Vault. Only pods assigned that identity can mount the secrets, providing granular, pod-level access control rather than a broader network or RBAC rule. On the Microsoft Cybersecurity Architect exam, this scenario tests your understanding of how to combine Azure-managed identities with the CSI driver for secure secret injection, a common trap being to confuse Azure Policy or Key Vault RBAC as sufficient controls. Remember the key pairing: pod identity authenticates, CSI driver mounts—without both, you cannot achieve true pod-level restriction. A useful memory tip is “CSI mounts, identity counts.”
SC-100 Practice Question: Design security solutions for applications and data
This SC-100 practice question tests your understanding of design security solutions for applications and data. 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.
A company deploys a multi-tier application on Azure Kubernetes Service (AKS). The application uses Azure Key Vault to store secrets. You need to ensure that pod-level access to secrets is restricted to only the pods that require them. What should you implement?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use the AKS Secret Store CSI Driver with pod-managed identities
Option B is correct because AKS Secret Store CSI Driver allows mounting secrets from Key Vault into specific pods using pod identity, ensuring only authorized pods can access secrets. Option A is wrong because RBAC on the Key Vault itself is too coarse. Option C is wrong because Azure Policy for AKS can enforce compliance but doesn't manage secret access. Option D is wrong because managed identity is used for pod identity but needs the CSI driver to mount secrets.
Key principle: ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Use a managed identity for each pod to access Key Vault directly
Why it's wrong here
Managed identity alone doesn't mount secrets; you need the CSI driver for that.
✗
Configure Azure RBAC on the Key Vault to restrict access to the AKS cluster
Why it's wrong here
RBAC on Key Vault controls access at the cluster level, not per pod.
✗
Apply Azure Policy to deny access to Key Vault from unauthorized namespaces
Why it's wrong here
Azure Policy can enforce rules but doesn't provide granular access control for pods.
✓
Use the AKS Secret Store CSI Driver with pod-managed identities
Why this is correct
CSI driver mounts secrets from Key Vault into specific pods using pod identity.
Related concept
Standard ACLs match source addresses.
Common exam traps
Common exam trap: ACLs stop at the first match
ACLs are processed top to bottom. The first matching entry wins, and an implicit deny usually exists at the end.
Detailed technical explanation
How to think about this question
ACL questions test precision: source, destination, protocol, port and direction. A generally correct ACL can still fail if it is applied on the wrong interface or in the wrong direction.
KKey Concepts to Remember
Standard ACLs match source addresses.
Extended ACLs can match source, destination, protocol and ports.
The first matching ACL entry is used.
There is usually an implicit deny at the end.
TExam Day Tips
→Check inbound versus outbound direction.
→Read the ACL from top to bottom.
→Look for a broader permit or deny above the intended line.
Key takeaway
ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this SC-100 question in full detail.
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related SC-100 ACL questions on filtering logic and placement.
Design security solutions for applications and data — This question tests Design security solutions for applications and data — Standard ACLs match source addresses..
What is the correct answer to this question?
The correct answer is: Use the AKS Secret Store CSI Driver with pod-managed identities — Option B is correct because AKS Secret Store CSI Driver allows mounting secrets from Key Vault into specific pods using pod identity, ensuring only authorized pods can access secrets. Option A is wrong because RBAC on the Key Vault itself is too coarse. Option C is wrong because Azure Policy for AKS can enforce compliance but doesn't manage secret access. Option D is wrong because managed identity is used for pod identity but needs the CSI driver to mount secrets.
What should I do if I get this SC-100 question wrong?
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related SC-100 ACL questions on filtering logic and placement.
What is the key concept behind this question?
Standard ACLs match source addresses.
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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Your organization is deploying a new application on Azure Kubernetes Service (AKS). You need to secure container access to Azure resources using managed identities. Which THREE components are required? (Choose THREE.)
hard
✓ A.Pod identity (e.g., aad-pod-identity)
✓ B.Azure AD pod-managed identity (or workload identity)
C.Azure Container Registry
✓ D.Azure Key Vault for secret storage
E.Azure Firewall
Why A: Option A, Option B, and Option D are correct. A pod identity is needed to assign an identity to pods, Azure Key Vault stores secrets, and Azure AD pod-managed identity (or workload identity) provides the identity. Option C is incorrect because Azure Container Registry is for storing images, not identity. Option E is incorrect because Azure Firewall is for network security.
Variation 2. You are designing a microservices application running on Azure Kubernetes Service (AKS). You need to ensure that secrets (e.g., API keys, connection strings) are securely stored and automatically rotated without application downtime. What is the recommended approach?
hard
A.Store secrets in Azure App Configuration with key vault references.
B.Store secrets as Kubernetes Secrets and use a controller to rotate them.
✓ C.Use Azure Key Vault with the Secrets Store CSI driver to mount secrets as volumes and enable rotation.
D.Inject secrets as environment variables from Azure Key Vault using a pod identity.
Why C: Option C is correct because using Azure Key Vault with the Secrets Store CSI driver allows pods to mount secrets as volumes, and rotation is handled by the driver. Option A is wrong because Kubernetes Secrets are base64-encoded, not encrypted by default. Option B is wrong because storing secrets in environment variables is less secure and harder to rotate. Option D is wrong because Azure App Configuration is for configuration, not secrets management.
Last reviewed: Jun 21, 2026
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.
This SC-100 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 SC-100 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.