Exam AZ-300 topic 3 question 5 discussion

From the mentioned link, Here are two scenarios for which WebJobs may be the best choice: You need more control over the code that listens for events, the JobHost object. Functions offers a limited number of ways to customize JobHost behavior in the host.json file. Sometimes you need to do things that can't be specified by a string in a JSON file. For example, only the WebJobs SDK lets you configure a custom retry policy for Azure Storage. You have an App Service app for which you want to run code snippets, and you want to manage them together in the same Azure DevOps environment.

Both should be webjobs as per the reference link: ou have an App Service app for which you want to run code snippets, and you want to manage them together in the same Azure DevOps environment.

webjob for both options as web job can be used for following Timer Azure Storage queues and blobs Azure Service Bus queues and topics Azure Cosmos DB Azure Event Hubs File system and You have an App Service app for which you want to run code snippets, and you want to manage them together in the same Azure DevOps environment.

Correct answer is Webjobs for both scenarios

answer is correct.Webjobs and Webjobs/ https://docs.microsoft.com/en-us/azure/azure-functions/functions-compare-logic-apps-ms-flow-webjobs

Second Box is also WebJobs. Copied from: https://docs.microsoft.com/en-us/azure/azure-functions/functions-compare-logic-apps-ms-flow-webjobs See link above in section "Summary": There it says: ... Here are two scenarios for which WebJobs may be the best choice: - You need more control over the code that listens for events, the JobHost object. Functions offers a limited number of ways to customize JobHost behavior in the host.json file. Sometimes you need to do things that can't be specified by a string in a JSON file. For example, only the WebJobs SDK lets you configure a custom retry policy for Azure Storage. - You have an App Service app for which you want to run code snippets, and you want to manage them together in the same Azure DevOps environment. ...

https://www.c-sharpcorner.com/article/creating-azure-webjobs-to-parse-messages-from-azure-storage-queues/ WebJobs WebJobs

Flow is technically a SaaS solution and it is rarely an answer in this exam. Flow is self-service while Logic Apps is for advanced integration. In the new software architecture models, it is recommended to use WebJobs only when the same Azure DevOps environment is required as Web Apps. For queue data processing, Logic Apps is more likely a solution that WebJobs. My answers: [Logic Apps] [WebJobs]

logic apps and webjobs

It should be Webjobs and logic apps

regarding Azure DevOps, and paraphrasing the Microsoft document... "Here are two scenarios for which WebJobs may be the best choice: You need more control over the code that listens for events, the JobHost object. Functions offers a limited number of ways to customize JobHost behavior in the host.json file. Sometimes you need to do things that can't be specified by a string in a JSON file. For example, only the WebJobs SDK lets you configure a custom retry policy for Azure Storage. You have an App Service app for which you want to run code snippets, and you want to manage them together in the same Azure DevOps environment." so... for option 2 -> Webjobs

See comparison table and summary

https://docs.microsoft.com/en-us/azure/azure-functions/functions-compare-logic-apps-ms-flow-webjobs

WebJobs and Logic Apps https://docs.microsoft.com/en-us/azure/azure-functions/functions-compare-logic-apps-ms-flow-webjobs Logic Apps --> Azure DevOps: source control, testing, support, automation, and manageability in Azure Resource Manager

It should be Webjobs and logic apps https://docs.microsoft.com/en-us/azure/azure-functions/functions-compare-logic-apps-ms-flow-webjobs

Webjobs and Flow