Can Enabling Ingress and a Custom Scale Rule Fix Container App Access?

AZ-204 By islever Editorial Last updated

Implement containerized solutions

Short answer

A Enabling ingress restores HTTP access and allows the Container App to scale from zero on incoming requests, so the solution meets the goal.

Question

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, create a custom scale rule, and apply the rule to the container app. Does the solution meet the goal?
  1. Yes Correct Answer
  2. No

Key Takeaways

Tests whether enabling ingress plus a custom scale rule resolves an inaccessible Container App; the trap is focusing on the scale rule while ignoring that enabling ingress alone restores HTTP access and automatic scaling.

When Azure Container Apps ingress is disabled and the app scales to zero, users cannot access it. Enabling ingress restores HTTP access and allows scaling from zero, so the proposed solution meets the goal.

Common mistake: Most learners say No, believing the custom scale rule won't bring the app back from zero instances, but they overlook that enabling ingress provides the HTTP endpoint and triggers scaling from zero.

Expert Analysis

Why the Answer Is Correct

Enabling ingress on the Container App provides an HTTP endpoint and allows the platform to scale from zero when a request arrives. As jobolesonihal noted, Microsoft documentation states you only need a custom scale rule or minReplicas "if you don't enable ingress." Since this solution enables ingress, the accessibility issue is resolved. The custom scale rule is an additional valid configuration that can control scaling behavior but is not strictly required; its presence does not prevent the solution from working. Therefore, the proposed solution meets the stated goal of restoring user access.

Why the Other Options Are Wrong

Option B (No) is incorrect because it overlooks the primary effect of enabling ingress. Commenters like manopeydakon argue that ingress and scale rules "won't directly address the issue of the app having scaled to 0 instances," but in Azure Container Apps, enabling ingress triggers HTTP-based scaling from zero. The custom scale rule alone without ingress would be insufficient if the app has no HTTP trigger, but here ingress is enabled. The scale-to-zero state persists only when ingress is disabled and no HTTP traffic can reach the app. Thus, the solution does address the root cause.

Community Comment Notes

The discussion shows a split. jobolesonihal quoted the docs: "If ingress is disabled and you don't define a minReplicas or a custom scale rule" then the app scales to zero with no way to restart. emysa341 voted A, citing that scale rules can be custom. manopeydakon voted B, arguing that enabling ingress and a custom scale rule won't fix the zero-instance problem. onlyforheros also voted B, saying "Creating a custom scale rule won't directly resolve the issue" unless scale is set to 1. These comments highlight the common trap of focusing on the scale rule rather than the ingress enablement.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

In Container Apps scenario questions, first identify whether ingress is enabled or disabled. If the app is inaccessible and ingress is disabled, enabling ingress is the primary fix; scale rules and minReplicas address scaling-to-zero only when ingress remains disabled.

Frequently Asked Questions

Why does enabling ingress alone fix the scaled-to-zero Container App?

With ingress enabled, the app receives HTTP traffic and can scale from zero automatically when a request arrives, so it becomes accessible without a custom scale rule.

Is a custom scale rule required when ingress is enabled?

No, but it doesn't hurt; a custom scale rule can be used with or without ingress, but enabling ingress is the key fix for accessibility.

More AZ-204 FAQ →

Community Votes

B
69%
A
31%

69% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 9 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 9

  1. manopeydakon 👍 4
    No, Enabling ingress and creating a custom scale rule won't directly address the issue of the app having scaled to 0 instances. Ingress and scale rules are related to managing the app's scalability and handling incoming traffic conditions, but they won't bring the app back to running instances if it has scaled down to 0. To resolve the issue of the app having 0 instances, you need to investigate why the app scaled down and take appropriate action. Reviewing scaling settings, resource constraints, and identifying any issues in the app itself would be more relevant to resolving this specific problem.
  2. jobolesonihal 👍 4 Answered B
    Documentation says "Make sure you create a scale rule or set minReplicas to 1 or more if you don't enable ingress. If ingress is disabled and you don't define a minReplicas or a custom scale rule, then your container app will scale to zero and have no way of starting back up."
  3. emysa341 👍 3 Answered A
    A is correct since scale rule can be custom https://learn.microsoft.com/en-us/azure/container-apps/scale-app?pivots=azure-cli#:~:text=Scale%20rules%20are%20implemented%20as%20HTTP%2C%20TCP%2C%20or%20custom.
  4. ryuhei 👍 3
    The problem is the same as #60.
  5. onlyforheros 👍 1 Answered B
    Creating a custom scale rule won't directly resolve the issue of the container app being inaccessible when scaled to 0 instances. Only if you set the scale to 1
Show 4 more comments
  1. Ciupaz 👍 1 Answered A
    Yes, this could be a good solution.
  2. JoaoPelisson 👍 2 Answered B
    Não atende
  3. Munwalinwali 👍 1 Answered B
    #62 is the correct answer
  4. 4d716d6 👍 1 Answered B
    Same as #60

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

How Do You Mitigate Azure Cache for Redis Maintenance Performance Issues?

S-grade

Azure Service Bus FIFO Processing Order

S-grade

How Do You Increase Read Cache in Azure Cache for Redis?

S-grade

Which Cosmos DB consistency level avoids out-of-order writes in multi-region reads?

S-grade

← Back to AZ-204 Study Guide