Soru

Your company has an Azure environment containing three virtual networks:
- `VNet-Hub` ($172.30.0.0/16$): Contains an Azure Firewall with a private IP address of $172.30.0.4$ in a subnet named `AzureFirewallSubnet`.
- `VNet-Prod` ($10.100.0.0/16$): Contains `VM-Prod` deployed in `ProdSubnet` ($10.100.1.0/24$).
- `VNet-Dev` ($10.200.0.0/16$): Contains `VM-Dev` deployed in `DevSubnet` ($10.200.1.0/24$).

Bidirectional peering connections are established between `VNet-Hub` and `VNet-Prod`, and between `VNet-Hub` and `VNet-Dev`.

To comply with security policies, all traffic between `VNet-Prod` and `VNet-Dev` must transit through the Azure Firewall in `VNet-Hub`.

You associate a route table with `ProdSubnet` that contains a route for address prefix $10.200.0.0/16$ with a next hop of $172.30.0.4$ (Virtual appliance).
You associate a route table with `DevSubnet` that contains a route for address prefix $10.100.0.0/16$ with a next hop of $172.30.0.4$ (Virtual appliance).

Azure Firewall rules are configured to permit all traffic between the two spoke networks.
However, `VM-Prod` and `VM-Dev` are unable to communicate.

Which peering configuration must you enable on the virtual network peering connections to allow communication between the virtual networks?