Explanation:
Box 1: 2
One management group for East, and one for West.
When creating a blueprint definition, you'll define where the blueprint is saved. Blueprints can be saved to a management group or subscription that you have Contributor access to. If the location is a management group, the blueprint is available to assign to any child subscription of that management group.
Box 2: 1
One definition as the you plan to deploy a custom application to each subscription.
With Azure Blueprints, the relationship between the blueprint definition (what should be deployed) and the blueprint assignment (what was deployed) is preserved.
Box 3: 4
One assignment for each subscription.
Reference:
https://docs.microsoft.com/en-us/azure/governance/blueprints/overview

Explanation

References:
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sizes-hpc#h-series

Explanation

Explanation/Reference:
https://docs.microsoft.com/en-us/azure/storage/common/storage-sas-overview

You can send email by using SendGrid bindings in Azure Functions. Azure Functions supports an output binding for SendGrid.
Note: When you're using the Consumption plan, instances of the Azure Functions host are dynamically added and removed based on the number of incoming events.
Reference:
https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-sendgrid
https://docs.microsoft.com/en-us/azure/azure-functions/functions-scale#consumption-plan