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 have an Azure web app named App1. App1 runs in an Azure App Service plan named Plan1. Plan1 is associated to the Free pricing tier.
You discover that App1 stops each day after running continuously for 60 minutes.
You need to ensure that App1 can run continuously for the entire day.
Solution: You change the pricing tier of Plan1 to Basic.
Does this meet the goal?
Click on the arrows to vote for the correct answer
A. B.A
The Free Tier provides 60 CPU minutes / day. This explains why App1 is stops. The Basic tier has no such cap.
https://azure.microsoft.com/en-us/pricing/details/app-service/windows/Answer: B. No.
Explanation:
The issue described in the scenario is related to the idle timeout configured for the Free pricing tier of the Azure App Service plan. By default, the idle timeout is set to 20 minutes for the Free pricing tier, which means that if there is no incoming request to the web app within the 20 minutes, the web app will be stopped automatically to save resources.
To ensure that the App1 web app can run continuously for the entire day, changing the pricing tier of Plan1 to Basic is not the correct solution. The Basic pricing tier also has an idle timeout of 20 minutes by default, which means that the issue will persist even after changing the pricing tier.
Instead, you can modify the idle timeout setting for the App1 web app by following these steps:
Go to the Azure portal and navigate to the App1 web app.
In the left-hand menu, select "Configuration" under the "Settings" section.
Scroll down to the "General settings" section, and change the "Idle timeout" value to "0" (which means that there is no timeout limit).
Save the changes and restart the App1 web app.
After making this change, the App1 web app will be able to run continuously without being stopped by the Azure App Service plan due to idle timeout.
Therefore, the correct answer is B. No, changing the pricing tier of Plan1 to Basic does not meet the goal. The correct solution is to modify the idle timeout setting for the App1 web app.