You need to recommend a solution for the App1 maintenance task. The solution must minimize costs.
What should you include in the recommendation?
You need to recommend a solution for the App1 maintenance task. The solution must minimize costs.
What should you include in the recommendation?
To minimize costs and automate the execution of PowerShell scripts every hour, an Azure Function is the most suitable option. Azure Functions is a serverless compute service that allows you to run event-triggered code without having to explicitly provision or manage infrastructure. This means you only pay for the compute time you consume, which is cost-effective, especially for tasks that are time-triggered like this hourly maintenance. Additionally, Azure Functions can be written in PowerShell, making it easy to copy files from the App1 instances in multiple regions. This approach avoids the overhead and complexity of managing a virtual machine or the potentially higher costs and complexity associated with provisioning and managing a Logic App for simple scripting tasks.
Azure function will need to be run from every region. This will need 2 functions. Logic app can be created centrally and executed for both regions as per given requirement. "The PowerShell script will run from a central location."
"Azure Functions resources are region-specific and can't be moved across regions. You must create a copy of your existing function app resources in the target region, then redeploy your functions code over to the new app." https://learn.microsoft.com/en-us/azure/azure-functions/functions-move-across-regions
You can create a Consumption logic app in multi-tenant Azure Logic Apps by using the JSON file for a logic app workflow definition. You can then manage your logic app by running the cmdlets in the Az.LogicApp PowerShell module. Reference: https://docs.microsoft.com/en-us/azure/logic-apps/quickstart-logic-apps-azure-powershell
Azure function as a resource is created in a region but it can access data store from a different region if access is provided. A single function from a region should be able to do the job. I have no reason to believe that a logic app can access data store from two regions but a function cannot. Answer is B.
I am confident it's B. Azure Function. I had this question on the exam today, and I got 979, in the Design Infrastrcture Solutions, I was 100% correct, and this quesiton belongs to this catagory.
For the App1 maintenance task, I would recommend using an **Azure Function** (Option B). Azure Functions is a serverless compute service that lets you run event-triggered code without having to explicitly provision or manage infrastructure. Given that the maintenance task needs to run every hour, this can be easily configured with a timer trigger in Azure Functions. This approach would minimize costs as you only pay for the compute time you consume - there is no charge when your code is not running. Plus, with Azure Functions, you can write your function code in PowerShell, which aligns with your requirement to run a PowerShell script.
PowerShell script and every hour, this is Azure Function for sure.
zure Functions are ideal for running scheduled tasks, such as hourly PowerShell scripts, without the overhead of maintaining a virtual machine. They offer a serverless compute service that allows you to execute code on-demand without having to provision and manage infrastructure, thereby minimizing cost
B. an Azure function
Both Azure function and Logic App may solve the problem but in terms of cost, Logic App is more efficient. Azure Functions need to have VNet integration to connect to every resource. As it is in different regions, they need Dedicated plan with a VNet Gateway (with its charges). See the matrix in https://learn.microsoft.com/en-us/azure/azure-functions/functions-networking-options?tabs=azure-cli#virtual-network-integration
I'd say Logic App because we don't know how much time the powershell script is going to take (with the risk of being over the 10 minutes allowed from the consumption plan); and something should still trigger the azure function periodically, so it would require another component
I choose B.
Super clear that one cannot run functions with one central copy across regions. So it has to be Logic Apps.
The correct answer is B. an Azure Function. Azure Functions is a serverless compute service that lets you run event-triggered code without having to explicitly provision or manage infrastructure. In this case, you can create a timer-triggered function that runs your PowerShell script every hour. This approach is cost-effective because with Azure Functions, you only pay for the time your code runs. Option A, Azure Logic App, is more suited for workflows and would be an overkill for this scenario. Option C, an Azure Virtual Machine, would require you to manage the infrastructure and would be more costly. Option D, an App Service WebJob, could also work but it would require an App Service plan which might be more expensive than Azure Functions. Therefore, Azure Functions would be the most cost-effective solution for this scenario.
I would agree with B and below show why https://learn.microsoft.com/en-us/azure/azure-functions/functions-compare-logic-apps-ms-flow-webjobs
Azure Logic Apps does not have a native connector to directly run PowerShell scripts within its workflows
Final Answer: an Azure logic app
"Every hour, you will run a maintenance task by invoking a PowerShell script that copies files from all the App1 instances. " --> This shows that require coding for copying is taken care of by PowerShell script and now it just need to be scheduled and executed. Logic App does not need coding Azure Functions need coding. So ruling out Azure Functions. Answer is Logic App.
Bro you need to run a PS script, which can be the code of the function
Azure Logic App. The key here is the term "every hour" "Every hour, you will run a maintenance task by invoking a PowerShell script that copies files from all the App1 instances. The PowerShell script will run from a central location." In Azure Logic App, you can schedule every hour.
timer-triggered azure function: exists
Wrong. The thing you call "key" should be "minimize costs". As for "every hour" all those options can be timed to execute hourly.
I'd say Logic App because we don't know how much time the powershell script is going to take (with the risk of being over the 10 minutes allowed from the consumption plan); and something should still trigger the azure function periodically, so it would require another component
The function code can be the script itlelf, so you don't need to code 2 components