AZ-700 · Question #68
You have an Azure subscription that contains the following resources: - A virtual network named Vnet1 - Two subnets named subnet1 and AzureFirewallSubnet - A public Azure Firewall named FW1 - A…
The correct answer is B. On FW1, create an outbound network rule that allows traffic to the Azure Key Management. The Azure Windows VMs need to connect to the Azure KMS server for Windows activation. The activation requires that the activation request come from an Azure public IP address. To resolve this problem, use the Azure custom route to route activation traffic to the Azure KMS…
Question
You have an Azure subscription that contains the following resources:
- A virtual network named Vnet1
- Two subnets named subnet1 and AzureFirewallSubnet
- A public Azure Firewall named FW1
- A route table named RT1 that is associated to Subnet1
- A rule routing of 0.0.0.0/0 to FW1 in RT1
After deploying 10 servers that run Windows Server to Subnet1, you discover that none of the virtual machines were activated. You need to ensure that the virtual machines can be activated. What should you do?
Options
- AOn FW1, create an outbound service tag rule for AzureCloud.
- BOn FW1, create an outbound network rule that allows traffic to the Azure Key Management
- CDeploy a NAT gateway.
- DTo Subnet1, associate a network security group (NSG) that allows outbound access to port 1688.
How the community answered
(34 responses)- A18% (6)
- B74% (25)
- C3% (1)
- D6% (2)
Explanation
The Azure Windows VMs need to connect to the Azure KMS server for Windows activation. The activation requires that the activation request come from an Azure public IP address. To resolve this problem, use the Azure custom route to route activation traffic to the Azure KMS https://docs.microsoft.com/en-us/troubleshoot/azure/virtual-machines/custom-routes-enable-kms-
Community Discussion
No community discussion yet for this question.