AZ-204: Developing Solutions for Microsoft Azure

Continuous WebJob Type

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 are designing an Azure WebJob that will run on the same instances as a web app.

You want to make use of a suitable WebJob type.

The webjob type should also allow for the option to restrict the WebJob to a single instance.

Solution: You configure the use of the Continuous WebJob type.

Does the solution meet the goal?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B.

Answer: <map><m x1="17" x2="310" y1="132" y2="223" ss="0" a="0" /><m x1="20" x2="309" y1="234" y2="316" ss="0" a="0" /><m x1="21" x2="312" y1="323"

https://docs.microsoft.com/en-us/azure/app-service/webjobs-create#webjob-types

Data will be added to the account every day by a web application.

You need to ensure that an email notification is sent when information is received from IoT devices, and that compute cost is reduced.

You decide to deploy a function app.

Which of the following should you configure the function app to use? Answer by dragging the correct option/s from the list to the answer area.

Options

Azure Cosmos DB
connector

SendGrid action

Consumption plan

Azure Event Hubs
binding

SendGrid binding

Answer
Options

Azure Cosmos DB
connector

SendGrid action

Azure Event Hubs
binding

Answer

Consumption plan

SendGrid binding

The solution of using Continuous WebJob type meets the stated goal of designing an Azure WebJob that will run on the same instances as a web app and also allowing the option to restrict the WebJob to a single instance.

A Continuous WebJob is a type of WebJob in Azure that runs continuously and performs background processing tasks. It is ideal for long-running and non-terminating background tasks such as polling for data, processing a queue, or performing periodic maintenance tasks.

When a Continuous WebJob is deployed on a web app, it runs on all instances of the web app by default. However, it is possible to restrict the Continuous WebJob to a single instance by setting the WEBJOBS_IDLE_TIMEOUT configuration setting to a high value like 29 days. This configuration setting ensures that the Continuous WebJob runs continuously on a single instance and does not move to another instance due to the default 20-minute idle timeout.

Therefore, by configuring the use of Continuous WebJob type and setting the WEBJOBS_IDLE_TIMEOUT configuration setting, the solution meets the goal of designing an Azure WebJob that will run on the same instances as a web app and also allowing the option to restrict the WebJob to a single instance.