Adding a Triggered WebJob for Continuous Running of App1 in Azure
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 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 add a triggered WebJob to App1.
Does this meet the goal?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B.B
You need to change to Basic pricing Tier.
Note: 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/The proposed solution of adding a triggered WebJob to App1 does not meet the goal of ensuring that the app runs continuously for the entire day.
WebJobs in Azure are background tasks that can be used to perform long-running processes, scheduled tasks, or run continuously in the background. However, in this case, adding a triggered WebJob to App1 will not prevent the app from stopping after running continuously for 60 minutes.
Since App1 is associated with the Free pricing tier, it is subject to certain limitations such as the fact that apps in the Free pricing tier are unloaded from memory after 20 minutes of idle time, and they are also limited to 60 minutes of continuous execution time.
To ensure that App1 runs continuously for the entire day, one possible solution would be to upgrade the App Service plan to a higher tier that allows for continuous execution time beyond 60 minutes. Alternatively, you could configure App1 to use an Always On feature, which keeps the app loaded in memory at all times, preventing it from being unloaded after a period of inactivity.
Therefore, the correct answer to the question is B. No, the proposed solution of adding a triggered WebJob to App1 does not meet the goal.
