The answer is to use namespace resource quotas per tenant and let the Kubernetes scheduler handle packing. This approach is correct because namespace resource quotas enforce hard limits on CPU, memory, and object counts for each tenant, preventing any single tenant from exhausting cluster resources and breaking multi-tenant isolation. The Kubernetes scheduler then efficiently packs pods within those quotas, optimizing resource utilization without manual intervention. On the AZ-204 exam, this scenario tests your understanding of AKS resource governance in multi-tenant architectures—a common trap is choosing separate clusters (option B), which wastes resources and increases management overhead, or relying solely on Azure Policy (option C), which lacks the per-namespace granularity of quotas. Remember the key distinction: quotas provide hard caps per namespace, while the scheduler handles packing efficiency. Memory tip: “Quotas cap, scheduler packs—no tenant attacks.”
AZ-204 Develop Azure compute solutions Practice Question
This AZ-204 practice question tests your understanding of develop azure compute solutions. 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 company develops a multi-tenant SaaS application hosted on Azure Kubernetes Service (AKS). Each tenant has isolated compute resources. You need to ensure that no single tenant can consume all cluster resources and affect others. You also want to optimize resource utilization by packing pods efficiently. You evaluate the following approaches: A) Use namespace resource quotas per tenant and let the Kubernetes scheduler handle packing. B) Deploy each tenant to a separate AKS cluster. C) Use Azure Policy to enforce pod resource limits. D) Use a service mesh to control traffic between tenants. Which approach should you recommend?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use namespace resource quotas per tenant and let the Kubernetes scheduler handle packing.
Option A is correct because namespace resource quotas per tenant provide hard limits on compute resources (CPU, memory) and object counts, preventing any single tenant from exhausting cluster resources. The Kubernetes scheduler then efficiently packs pods within those quotas, optimizing utilization without manual intervention. This approach balances isolation and resource efficiency in a multi-tenant AKS environment.
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.
✓
Use namespace resource quotas per tenant and let the Kubernetes scheduler handle packing.
Why this is correct
Isolates tenants and optimizes packing.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use a service mesh to control traffic between tenants.
Why it's wrong here
Does not provide resource isolation.
✗
Use Azure Policy to enforce pod resource limits.
Why it's wrong here
Enforces limits but not total resource consumption per tenant.
✗
Deploy each tenant to a separate AKS cluster.
Why it's wrong here
Overkill, expensive, and complex.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse Azure Policy (which enforces pod-level limits) with namespace-level resource quotas, missing that quotas are the correct mechanism for tenant-level aggregate resource isolation in a shared cluster.
Detailed technical explanation
How to think about this question
Namespace resource quotas in Kubernetes are enforced via the ResourceQuota API object, which can limit aggregate CPU and memory requests/limits across all pods in a namespace. The scheduler uses these quotas to make placement decisions, ensuring no pod is scheduled if it would exceed the quota, while still packing pods densely within the limits. In AKS, you can also combine ResourceQuota with LimitRange to set default resource requests/limits per pod, further preventing misconfigured containers from starving others.
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 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 AZ-204 question in full detail.
Develop Azure compute solutions — This question tests Develop Azure compute solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use namespace resource quotas per tenant and let the Kubernetes scheduler handle packing. — Option A is correct because namespace resource quotas per tenant provide hard limits on compute resources (CPU, memory) and object counts, preventing any single tenant from exhausting cluster resources. The Kubernetes scheduler then efficiently packs pods within those quotas, optimizing utilization without manual intervention. This approach balances isolation and resource efficiency in a multi-tenant AKS environment.
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.