Does enabling ingress with minReplicas 1 fix Container Apps scale-to-zero?
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 have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You deploy an Azure Container Apps app and disable ingress on the container app. Users report that they are unable to access the container app. You investigate and observe that the app has scaled to 0 instances. You need to resolve the issue with the container app. Solution: Enable ingress and configure the minimum replicas to 1 for the container app. Does the solution meet the goal?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests Azure Container Apps scaling rules: without ingress you must define minReplicas (or a custom scale rule), otherwise the app scales to zero, and the trap is blaming only the replica count while ignoring that ingress must also be re-enabled for user access.
An Azure Container Apps app was deployed with ingress disabled and scaled to zero instances, making it unreachable. This page confirms that enabling ingress while setting the minimum replica count to 1 is a valid fix, so the answer to 'Does the solution meet the goal?' is Yes (A).
Choosing No (B) because the learner assumes replica configuration alone is irrelevant, or because they confuse the default minReplicas of 0 with a hard restriction — the real defect is that disabling ingress plus no minReplicas removed any trigger to restart the app.
Community Discussion (7 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Enabling ingress on the Container Apps app restores the HTTP/TCP endpoint that users lost when ingress was disabled, so external traffic can reach the app again. Setting minimum replicas to 1 guarantees at least one revision instance is always running, which is exactly what prevents the observed scale-to-zero state. Azure's Container Apps scaling documentation states that if ingress is disabled and you do not define a minReplicas value or a custom scale rule, the app will scale to zero with no way to start back up. The proposed solution therefore addresses both halves of the failure: reachability (ingress) and availability (minReplicas = 1), so it meets the goal.Why the Other Options Are Wrong
Option B (No) would only be defensible if the solution failed to restore access or still permitted zero instances, which is not the case here. The dissenting view argues that "the minimum replica of the scale can be 0," but a minimum of 0 is precisely the misconfiguration that produced the outage when combined with disabled ingress — it is not a reason to reject the fix. No other option is presented, so the only competing answer is a flat rejection that ignores how ingress and replica minimums interact in Container Apps.Community Comment Notes
Most voters selected Yes, with Mahesh1222 stating that "The minimum replicas setting=1 ensures that the app always has at least one instance running." sky_may reinforced this from the Microsoft documentation, quoting that "then your container app will scale to zero and have no way of starting back up," which matches the symptom reported in the scenario. FeriAZ and manopeydakon both split the fix into its two effects — ingress reopens external traffic routes while minReplicas keeps an instance alive. Only emysa341 chose B, citing the scale-app page's note that the minimum number of replicas can be 0 — true as a default, but that is the very condition that caused the problem, not evidence the solution fails.Official Reference
Exam Strategy
When an AZ-204 item asks whether a solution meets the goal, verify each clause of the solution against a documented behavior rather than judging the solution as a whole. Here both clauses map to real Container Apps settings, so a two-part fix that restores ingress and forces a non-zero minimum is a valid Yes.
Frequently Asked Questions
Why does a Container App scale to zero when ingress is disabled?
With ingress disabled and no minReplicas or custom scale rule defined, Container Apps has no HTTP traffic trigger and defaults to zero replicas, leaving no way for the app to start back up.
Why not just set minReplicas to 1 without enabling ingress?
A running instance alone is not enough — users still need the ingress endpoint to reach the app, so the outage would persist for external callers.