Correct:
* From the Azure portal, modify an action group of Azure Monitor.
Incorrect:
* Deploy an Azure Resource Manager template that configures AppInsights1.
* Deploy an Azure Resource Manager template that configures the analyticsItems child resource of AppInsights1.
* Deploy an Azure Resource Manager template that configures the ProactiveDetectionConfigs child resource of AppInsights1.
* From the Azure portal, create a service health alert of Azure Monitor.
* From the Azure portal, modify a smart detection rule of AppInsights1.
* From the Azure portal, modify diagnostic settings of AppInsights1.
Note:
To implement push notifications for an unusual increase in the rate of failed HTTP requests for an Azure App Service Web App using Azure Application Insights, you can configure an alert rule that monitors the failed request rate and triggers an action group when a threshold is exceeded. This action group can then send notifications through various channels, including email, SMS, or webhook to trigger a push notification.
When Azure Monitor data indicates that there might be a problem with your infrastructure or application, an alert is triggered. You can use an action group to send a notification such as a voice call, SMS, push, or email when the alert is triggered in addition to the alert itself. Action groups are a collection of notification preferences and actions. Azure Monitor, Azure Service Health, and Azure Advisor use action groups to notify users about the alert and take an action.
Reference:
https://learn.microsoft.com/en-us/azure/azure-monitor/alerts/action-groups

The Update operation allows you to modify a message's content and its visibility timeout. You can use this operation to update the visibility timeout for a message that has already been retrieved from the queue.
When you retrieve (or "receive") a message from the queue, you can specify the visibility timeout at that point. This is useful when you want to process the message but delay its visibility to other consumers.

Explanation:
Box 1: Run Command
This capability is useful in all scenarios where you want to run a script within a VM. It's one of the only ways to troubleshoot and remediate a VM that doesn't have the RDP or SSH port open, because of improper network or administrative user configuration.
Box 2: Customer Script Extension
The Custom Script Extension downloads and executes scripts on Azure virtual machines. This extension is useful for post deployment configuration, software installation, or any other configuration or management tasks. Scripts can be downloaded from Azure storage or GitHub, or provided to the Azure portal at extension run time. The Custom Script Extension integrates with Azure Resource Manager templates, and can be run using the Azure CLI, PowerShell, Azure portal, or the Azure Virtual Machine REST API.
Reference:
https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/custom-script-windows
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/run-scripts-in-vm

Explanation:
Box 1: fixed
The `Default' policy does 4 exponential retries and from my experience the interval times are often too short in situations.
Box 2: PT10S
PT10s will be the better answer, 5 attempts with each 10 seconds delay satisfy the requirement
"The label printer must only receive up to 5 attempts within one minute" Box 3: 5 Reference:
https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-exception-handling