Practice Test 4 | Microsoft Azure Administrator | AZ-104 | Dumps | Mock Test
A company currently has 2 Azure subscriptions: WebMagic-staging and WebMagic-production.
WebMagic-staging has the following virtual networks.
| Name | Address space | Location |
| vnet-staging-01 | 10.10.10.0/24 | West Europe |
| vnet-staging-02 | 172.16.0.0/16 | West US |
The virtual networks have the following subnets.
| Name | Address space | Location |
| snet-staging-11 | 10.10.10.0/24 | vnet-staging-01 |
| snet-staging-21 | 172.16.0.0/18 | vnet-staging-02 |
| snet-staging-22 | 172.16.128.0/18 | vnet-staging-02 |
WebMagic-production has the following virtual network.
| Name | Address space | Location |
| vnet-production | 10.10.128.0/17 | Canada Central |
This network contains the following subnets.
| Name | Address space |
| snet-production-01 | 10.10.130.0/24 |
| snet-production-02 | 10.10.131.0/24 |
Can you establish a VNet-to-VNet VPN connection between vnet-staging-01 and vnet-staging-02?
A. Yes
B. No
Explanation:
Answer – B
To create a VNet-to-VNet VPN between two virtual networks, you need to have a special subnet – gateway subnet. Azure recommends reserve /27 or /28 CIDR blocks for this subnet. The virtual network vnet-staging-01 (10.10.10.0/24) has /24 CIDR blocks of address space. This space is already taken by snet-staging-11 subnet (10.10.10.0/24). This is why there is no sufficient address space to create a gateway subnet and to establish a VNet-to-VNet VPN connection between two VNETs. We need to resize subnet space or create an additional IP address range for the gateway subnet.
For more information on configuring VNet-to-VNet connections, please visit the following URL-
Comments are closed, but trackbacks and pingbacks are open.