Soru

Zorluk: KolayCreate and Configure Virtual Networks and Subnets

You are designing the IP addressing and subnetting strategy for a new Azure Virtual Network (VNet). You plan to deploy both an Azure Bastion host and an Azure VPN Gateway. Which two of the following configuration requirements must you meet when creating the subnets for these resources? (Select two)

  1. The subnet hosting the Azure Bastion service must be named AzureBastionSubnetCevap
  2. The subnet hosting the VPN Gateway must be named GatewaySubnetCevap
  3. C
    The Azure Bastion subnet can be named BastionSubnet to align with custom enterprise naming standards
  4. D
    The Azure Bastion subnet can be configured with a prefix size of /29 to minimize IP address consumption

Cevap

The subnet hosting the Azure Bastion service must be named AzureBastionSubnet, and the subnet hosting the VPN Gateway must be named GatewaySubnet.
Azure enforces strict, case-sensitive naming conventions for certain platform-managed subnets. The subnet for Azure Bastion must be named exactly AzureBastionSubnet, and the subnet for a VPN Gateway must be named exactly GatewaySubnet. These specific names allow the Azure platform to correctly provision and manage these services within the virtual network.

Adım Adım Çözüm

1
Identify the naming conventions for specialized Azure subnets.
The Azure Bastion subnet must be named AzureBastionSubnet, and the Virtual Network Gateway subnet must be named GatewaySubnet.
Azure services look for these exact, case-sensitive names to bind and deploy the gateway and bastion resources.
2
Determine the subnet size requirements for Azure Bastion.
The Azure Bastion subnet requires a prefix size of /26 or larger.
A size of /26 provides 64 IP addresses (59 usable after Azure reservations), which is the minimum requirement for Bastion scaling.

Anahtar Kavram

Azure Virtual Networks require specific names and size constraints for dedicated subnets like AzureBastionSubnet and GatewaySubnet.
Tahmini Süre:45s
Bu soruyu puanla