Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You have an Azure subscription that contains 10 virtual networks. The virtual networks are hosted in separate resource groups.
Another administrator plans to create several network security groups (NSGs) in the subscription.
You need to ensure that when an NSG is created, it automatically blocks TCP port 8080 between the virtual networks.
Solution: From the Resource providers blade, you unregister the Microsoft.ClassicNetwork provider.
Does this meet the goal?
Click on the arrows to vote for the correct answer
A. B.B
Use a policy definition.
No, unregistering the Microsoft.ClassicNetwork provider from the Resource Providers blade will not meet the goal of automatically blocking TCP port 8080 between the virtual networks when an NSG is created.
The Microsoft.ClassicNetwork provider is responsible for managing classic virtual networks, which are a type of virtual network that is being phased out in favor of Azure Resource Manager (ARM) virtual networks. Unregistering this provider will not have any effect on NSGs that are created in ARM virtual networks.
To automatically block TCP port 8080 between the virtual networks, you can create an NSG that contains a rule to block traffic on that port, and then associate the NSG with the subnets in each virtual network. This will ensure that any traffic on port 8080 between the virtual networks is automatically blocked.
Alternatively, you can use Azure Firewall to create network rules to block traffic on port 8080 between the virtual networks. Azure Firewall is a fully stateful firewall-as-a-service with built-in high availability and unrestricted cloud scalability.