AZ-700 · Question #255
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 virtual machines in Subnet1 are unable to activate because the Azure Firewall, which intercepts all outbound internet traffic, is blocking the necessary communication.
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 machine operating systems were activated. You need to ensure that the virtual machines can be activated. What should you do?
Options
- ATo Subnet1, associate a network security group (NSG) that allows outbound access to port 1688.
- BOn FW1, create an outbound network rule that allows traffic to the Azure Key Management
- CDeploy a NAT gateway.
- DDeploy an application security group that allows outbound traffic to 1688.
How the community answered
(32 responses)- A6% (2)
- B81% (26)
- C3% (1)
- D9% (3)
Why each option
The virtual machines in Subnet1 are unable to activate because the Azure Firewall, which intercepts all outbound internet traffic, is blocking the necessary communication.
While port 1688 is correct for KMS, an NSG on Subnet1 would not be effective because the traffic is already being routed to FW1 by the UDR (0.0.0.0/0), making the firewall the blocking point.
Windows virtual machines activate against Azure Key Management Service (KMS) hosts using TCP port 1688. Since the route table directs all outbound internet-bound traffic (0.0.0.0/0) from Subnet1 to FW1, an outbound network rule must be created on FW1 to allow traffic to the Azure KMS service tag on port 1688 for activation to succeed.
A NAT gateway provides outbound internet connectivity but does not bypass or configure rules on an Azure Firewall to allow specific traffic like KMS activation.
An application security group (ASG) helps group VMs for NSG rules, but it does not directly configure outbound access through an Azure Firewall; ASGs work with NSGs, and the firewall is the primary block.
Concept tested: Azure Firewall outbound rules for Windows activation
Source: https://learn.microsoft.com/en-us/azure/architecture/reference-architectures/dmz/secure-vnet-dmz#allow-kms-outbound-network-access
Community Discussion
No community discussion yet for this question.