AZ-204 · Question #559
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…
The correct answer is B. No. While enabling ingress resolves the access issue, simply adding a TCP scale rule without setting minimum replicas does not prevent the Azure Container App from scaling to zero instances when idle, nor is it always the most appropriate scaling method for HTTP traffic.
Question
Options
- AYes
- BNo
How the community answered
(56 responses)- A29% (16)
- B71% (40)
Why each option
While enabling ingress resolves the access issue, simply adding a TCP scale rule without setting minimum replicas does not prevent the Azure Container App from scaling to zero instances when idle, nor is it always the most appropriate scaling method for HTTP traffic.
Enabling ingress is necessary for external access. However, relying solely on a TCP scale rule, without configuring minimum replicas, may still allow the app to scale to 0 when idle, potentially leading to cold start delays or not fully resolving the observed scaling issue if continuous availability is desired.
While enabling ingress allows external access, a TCP scale rule is often not the primary or most efficient scaling method for typical HTTP-based container apps, which primarily scale on HTTP requests. Furthermore, simply adding a scale rule doesn't prevent the app from scaling to 0 instances if `minReplicas` is set to 0 and there are no active connections.
Concept tested: Azure Container Apps ingress, scaling, and replica management
Source: https://learn.microsoft.com/en-us/azure/container-apps/scale-app
Topics
Community Discussion
No community discussion yet for this question.