Explanation:

Box 1: Yes
Most services go to private preview then public preview before being released to general availability.
The private preview is only available to certain Azure customers for evaluation purposes. The public preview is available to all Azure customers.
Box 2: No
Azure services in public preview can be managed using the regular management tools: Azure Portal, Azure CLI and PowerShell.
Box 3: No
Services in private or public preview are usually offered at reduced costs. However, the costs increase, not decrease when the services are released to general availability.

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 .microso ft.com/e n-us/azure/a zure-r esource-ma nager/resource-group-overview

Explanation:
Subscription
At the Azure portal, select Subscriptions. Select the subscription you want to assign and then select Access Control. Select Add to add a user to the subscription
https://learn.microsoft.com/en-us/partne r-center/assign-azure-subscri p tions#:~:text=At%2 0the%20Azure%
20po rtal%2C%20select,the%20user%20 will%20have%20access .

Explanation:

Box 1: No
North America has several Azure regions, including West US, Central US, South Central US, East Us, and Canada East.
Box 2: Yes
A region is a set of datacenters deployed within a latency-defined perimeter and connected through a dedicated regional low-latency network.
Box 3: No
Outbound data transfer is charged at the normal rate and inbound data transfer is free.
References:
https://azure.microsoft.com/en-us/global-infrastructure/regions/
https://azure.microsoft.com/en-us/pricing/details/bandwidth/