Explanation

References:
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/managed-disks-overview

Explanation

Explanation

Box 1: No
Azure resources deployed to a single resource group can be located in different regions. The resource group only contains metadata about the resources it contains.
When creating a resource group, you need to provide a location for that resource group. You may be wondering, "Why does a resource group need a location? And, if the resources can have different locations than the resource group, why does the resource group location matter at all?" The resource group stores metadata about the resources. When you specify a location for the resource group, you're specifying where that metadata is stored. For compliance reasons, you may need to ensure that your data is stored in a particular region.
Box 2: No
Tags for Resources are not inherited by default from their Resource Group Box 3: Yes A resource group can be used to scope access control for administrative actions. By default, permissions set at the resource level are inherited by the resources in the resource group.
Reference:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-overview

Explanation
With the public cloud, you get pay-as-you-go pricing - you pay only for what you use, no CapEx costs. With the public cloud, you have self-service management. You are responsible for the deployment and configuration of the cloud resources such as virtual machines or web sites. The underlying hardware that hosts the cloud resources is managed by the cloud provider.
https://docs.microsoft.com/en-gb/learn/modules/principles-cloud-computing/4-cloud-deployment-models