Azure Container Instances CPU Limits vs Requests
You have an Azure subscription that contains a container group named Group1. Group1 contains two Azure container instances as shown in the following table. You need to ensure that container2 can use CPU resources without negatively affecting container1. What should you do? - 
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Removing a container's resource limit sets its maximum usage to its resource request, preventing bursting that could starve other containers in the group.
This page explains how to configure CPU resource limits and requests in an Azure Container Instances group to prevent one container from negatively affecting another. It establishes that removing resource limits caps usage at the request value, ensuring fair allocation.
Choosing D (Decrease limit of container2 to two CPUs) because it seems to restrict container2, but a limit must be greater than or equal to the request, making this configuration invalid.
Community Discussion (8 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Removing the resource limit for both containers (Option C) ensures that neither container can consume more CPU than its requested amount. According to Azure documentation, if a resource limit is not specified, the container's maximum resource usage defaults to its resource request. This prevents container2 from bursting beyond its 3 CPU request and stealing CPU time from container1, which guarantees container1 always has its 2 CPUs available.Why the Other Options Are Wrong
Option A increases container1's limit, allowing it to burst, but does nothing to restrict container2 from bursting and consuming shared CPU resources. Option B increases container2's limit to six CPUs, which exceeds the container group's total allocation of 5 CPUs and exacerbates the risk of container2 starving container1. Option D suggests decreasing container2's limit to two CPUs, but Azure requires that a container's resource limit be greater than or equal to its resource request; since container2 requests 3 CPUs, a limit of 2 is invalid.Community Comment Notes
Several learners initially doubted option C but confirmed its correctness based on Microsoft documentation stating "If you don't specify a resource limit, the container instance's maximum resource usage is the same as its resource request." As FatFatSam noted, option D is invalid because "The resource limit of a container instance must be greater than or equal to the mandatory resource request property." Some, like 117b84e, incorrectly favored D based on AI suggestions, failing to recognize the Azure constraint on limits versus requests.Official Reference
Exam Strategy
When dealing with Azure Container Instances resource limits, remember that omitting a limit caps the container at its request, preventing bursting. Always verify that any proposed limit is greater than or equal to the request and does not exceed the container group's total resources.
Related Analysis
Practice All AZ-104 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AZ-104 Practice Test →