You are designing the subnet configuration for an Azure virtual network named `vnet-prod` that has an address space of . The virtual network currently contains a single subnet named `snet-web` with an address range of . You need to add two new subnets to `vnet-prod` to support the following requirements:
1. Deploy an Azure Bastion host to secure management access to virtual machines.
2. Deploy a Virtual Network Gateway to establish a hybrid connection with an on-premises datacenter.
You want to allocate the minimum recommended address space for both subnets while ensuring they are fully functional and compliant with Microsoft best practices. Which of the following configurations should you implement?
- Create AzureBastionSubnet with the range and GatewaySubnet with the range .Cevap
- BCreate snet-bastion with the range and GatewaySubnet with the range .
- CCreate AzureBastionSubnet with the range and GatewaySubnet with the range . To enable name resolution, you must create a Private DNS Zone and link it directly to AzureBastionSubnet and GatewaySubnet.
- DCreate AzureBastionSubnet with the range and GatewaySubnet with the range . To route all outbound traffic from snet-web through the VPN gateway, you must associate a route table to snet-web with a route of and a next hop type of Virtual Appliance.
Cevap
Create AzureBastionSubnet with the range and GatewaySubnet with the range .
The correct configuration uses the range for a subnet named exactly AzureBastionSubnet and the range for a subnet named exactly GatewaySubnet. This fulfills the naming requirements, respects the minimum subnet size requirement of /26 for Azure Bastion, and adheres to Microsoft's recommended /27 or larger subnet size for the GatewaySubnet.
Adım Adım Çözüm
Anahtar Kavram
Azure virtual network planning requires meeting strict name and prefix constraints for specialized service subnets, specifically a minimum of /26 for AzureBastionSubnet and a recommended minimum of /27 for GatewaySubnet.