Examice

Exam AZ-204 All QuestionsBrowse all questions from this exam

Question 98

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?

Yes

Correct Answer: A

When a container app in Azure Container Apps scales to 0 instances, it is usually because there is no active scale rule keeping it at a minimum number of instances. Enabling ingress to allow traffic and then creating a custom scale rule to manage the scale based on your specific needs would address the scaling issue. By doing so, the app will avoid scaling down to 0 instances, ensuring that it is available to handle requests. Therefore, enabling ingress, creating a custom scale rule, and applying the rule to the container app effectively meets the goal.

Discussion

manopeydakonOption: B

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.

emysa341Option: 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.

de8a1d8

Right, page says : Important 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.

ryuhei

The problem is the same as #60.

MarcosAn

Yes, same cenario as previus question.

jobolesonihalOption: 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."

MunwalinwaliOption: B

#62 is the correct answer

JoaoPelissonOption: B

Não atende

onlyforherosOption: 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

4d716d6Option: B

Same as #60

vkalynenko

#60 mentioned Http scale rule, not custom

CiupazOption: A

Yes, this could be a good solution.