You are planning the IP addressing scheme for a new Azure virtual network named `vnet-logistics` that has an address space of . You need to create two subnets to meet the following requirements:
- A subnet for Azure Bastion that supports the minimum required subnet prefix size.
- A subnet named `snet-db` that must support at least database servers.
You must minimize the number of IP addresses allocated to both subnets to conserve the address space for future expansion.
Which two of the following subnet configurations should you implement? (Select two.)
- A subnet named `AzureBastionSubnet` with an address space of Cevap
- A subnet named `snet-db` with an address space of Cevap
- CA subnet named `snet-bastion` with an address space of
- DA subnet named `AzureBastionSubnet` with an address space of
- EA subnet named `snet-db` with an address space of
Cevap
The correct configurations are a subnet named `AzureBastionSubnet` with an address space of , and a subnet named `snet-db` with an address space of .
The correct subnet configurations are the subnet named `AzureBastionSubnet` with a prefix and the subnet named `snet-db` with a prefix. Azure Bastion enforces a strict naming requirement of `AzureBastionSubnet` and a minimum prefix size of `/26`. For the database subnet, hosting servers requires at least total IP addresses because Azure reserves 5 IP addresses in every subnet. A prefix provides exactly addresses, leaving usable, which satisfies the host requirement while minimizing address space consumption.
Adım Adım Çözüm
Anahtar Kavram
Subnet sizing and naming requirements in Azure, including reserved IP addresses and service-specific subnet constraints.