Azure policies can be used to define requirements for resource properties during deployment and for already existing resources. Azure Policy controls properties such as the types or locations of resources.
Azure Policy is a service in Azure that you use to create, assign, and manage policies. These policies enforce different rules and effects over your resources, so those resources stay compliant with your corporate standards and service level agreements.
In this question, we would create a Azure policy assigned to the resource group that denies the creation of virtual machines in the resource group.
You could place a read-only lock on the resource group. However, that would prevent the creation of any resources in the resource group, not virtual machines only. Therefore, an Azure Policy is a better solution.
References:
https://docs.microsoft.com/en-us/azure/governance/policy/overview

Explanation:

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 .

Networks in Azure are known as virtual networks. A virtual network can have multiple IP address spaces and multiple subnets. Azure automatically routes traffic between different subnets within a virtual network.
The question states that FinServer must be on a separate network segment. The only way to separate FinServer from the other servers in networking terms is to place the server in a different virtual network to the other servers.
References:
https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-vnet-plan-design-arm

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.