The answer is the Azure Policy for Kubernetes (preview) initiative. This is correct because it includes built-in policies specifically designed to enforce security controls on AKS clusters, such as auditing and denying the creation of privileged containers, by evaluating Kubernetes admission controller requests against defined constraints. On the Microsoft Cybersecurity Architect exam, this question tests your understanding of how Azure Policy integrates with Kubernetes to provide guardrails at the cluster level, often appearing as a scenario where you must choose between policy enforcement, monitoring, or identity solutions. A common trap is confusing Defender for Cloud’s workload protection, which monitors but does not enforce, or Azure RBAC, which controls permissions but not container security. Remember: if the task is to automatically audit or deny a specific container configuration, think Azure Policy for Kubernetes, not just any security tool. Memory tip: “Policy prevents, Defender detects.”
SC-100 Design security solutions for infrastructure Practice Question
This SC-100 practice question tests your understanding of design security solutions for infrastructure. 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.
Your organization is deploying Azure Kubernetes Service (AKS) and plans to use Azure Policy to enforce security controls on the cluster. The security team wants to automatically audit and deny the creation of privileged containers. Which Azure Policy initiative should you assign?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Azure Policy for Kubernetes (preview)
Option A is correct because the Azure Policy for Kubernetes initiative (preview) includes built-in policies to enforce security constraints like preventing privileged containers. Option B is wrong because Defender for Cloud's workload protection provides monitoring but not policy enforcement. Option C is wrong because Azure RBAC roles control permissions, not container security. Option D is wrong because AKS Pod Identity is for pod authentication to Azure resources.
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Azure RBAC roles for AKS
Why it's wrong here
RBAC controls who can perform actions, not what can be deployed.
✓
Azure Policy for Kubernetes (preview)
Why this is correct
This initiative includes policies to restrict privileged containers, host networking, and other security settings.
Related concept
Authentication checks who the user is.
✗
Microsoft Defender for Containers
Why it's wrong here
Defender for Containers provides threat detection, not policy-based denial of resource creation.
✗
AKS Pod Identity
Why it's wrong here
Pod Identity allows pods to assume Azure identities, unrelated to container privilege enforcement.
Common exam traps
Common exam trap: authentication is not authorization
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Detailed technical explanation
How to think about this question
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
KKey Concepts to Remember
Authentication checks who the user is.
Authorization controls what the user is allowed to do after login.
Privilege levels affect access to EXEC and configuration commands.
AAA, TACACS+ and RADIUS can separate login success from command access.
TExam Day Tips
→Do not assume successful login means full administrative access.
→Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
→Separate login problems from permission problems before choosing the answer.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
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 SC-100 question in full detail.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related SC-100 questions on access control and AAA configuration.
Design security solutions for infrastructure — This question tests Design security solutions for infrastructure — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Azure Policy for Kubernetes (preview) — Option A is correct because the Azure Policy for Kubernetes initiative (preview) includes built-in policies to enforce security constraints like preventing privileged containers. Option B is wrong because Defender for Cloud's workload protection provides monitoring but not policy enforcement. Option C is wrong because Azure RBAC roles control permissions, not container security. Option D is wrong because AKS Pod Identity is for pod authentication to Azure resources.
What should I do if I get this SC-100 question wrong?
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related SC-100 questions on access control and AAA configuration.
What is the key concept behind this question?
Authentication checks who the user is.
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 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.