An administrator is planning the deployment of a new virtual network named `vnet-prod` to support a web application and secure administrative access. The virtual network is assigned the address space .
The administrator must configure three subnets within `vnet-prod` to meet the following requirements:
- A subnet for the web application servers that must support up to concurrent virtual machines.
- A subnet for Azure Bastion to allow secure administration.
- A subnet for a database tier that must support up to virtual machines.
The administrator wants to minimize IP address space waste and allocate the smallest possible CIDR blocks that satisfy these requirements.
Which of the following subnet configurations should the administrator use?
- AzureBastionSubnet: ; Subnet-Web: ; Subnet-DB: Answer
- BBastionSubnet: ; Subnet-Web: ; Subnet-DB:
- CAzureBastionSubnet: ; Subnet-Web: ; Subnet-DB:
- DAzureBastionSubnet: ; Subnet-Web: ; Subnet-DB:
Answer
AzureBastionSubnet: 10.200.0.0/26; Subnet-Web: 10.200.0.64/26; Subnet-DB: 10.200.0.128/28
The configuration specifying AzureBastionSubnet at , Subnet-Web at , and Subnet-DB at is correct because it satisfies all naming, sizing, and usability constraints: first, the Azure Bastion subnet is named exactly `AzureBastionSubnet` and is sized at `/26` (the minimum supported size); second, the web subnet is sized at `/26` (providing usable IPs), which is the smallest CIDR block that can accommodate virtual machines; third, the database subnet is sized at `/28` (providing usable IPs), which is the smallest CIDR block that can accommodate virtual machines since a `/29` would only provide usable IPs.
Step-by-Step Solution
Key Concept
Azure Virtual Network subnets reserve 5 IP addresses (the first four and the last one). Therefore, the capacity calculation must always be: Usable IPs = Total IPs - 5. Furthermore, specialized subnets like Azure Bastion have strict minimum sizes (/26) and naming requirements.