Examkin

Soru

Zorluk: OrtaCreate and Configure Virtual Networks and Subnets

Your company has an Azure subscription containing a virtual network named `vnet-finance-prod` with an address space of 10.100.0.0/2210.100.0.0/22. You plan to deploy the following resources:

- A pool of virtual machines in a subnet named `snet-application` that requires at least 2727 usable IP addresses.
- An Azure Bastion host to secure access to the virtual machines.
- A Virtual Network Gateway to enable hybrid connectivity with the on-premises network.

You need to configure the subnets for these resources while minimizing the address space allocated to each subnet.

Which two subnets should you create? (Select two.)

  1. AzureBastionSubnet with the address range 10.100.1.0/2610.100.1.0/26Cevap
  2. GatewaySubnet with the address range 10.100.2.0/2710.100.2.0/27Cevap
  3. C
    snet-application with the address range 10.100.3.0/2810.100.3.0/28
  4. D
    AzureBastionSubnet with the address range 10.100.1.0/2710.100.1.0/27
  5. E
    GatewaySubnet with the address range 10.100.2.0/3010.100.2.0/30

Cevap

AzureBastionSubnet with the address range 10.100.1.0/2610.100.1.0/26 and GatewaySubnet with the address range 10.100.2.0/2710.100.2.0/27
The correct subnet configurations satisfy Azure's sizing rules: the Bastion subnet must be named AzureBastionSubnet with a prefix of /26/26 or larger, and the Virtual Network Gateway subnet must be named GatewaySubnet with a prefix of /29/29 or larger. The configuration using a /26/26 prefix for the Bastion subnet and a /27/27 prefix for the Gateway subnet meets these rules.

Adım Adım Çözüm

1
Calculate the minimum subnet size for the application host pool.
The application pool requires 2727 usable IP addresses. Adding Azure's 55 reserved IP addresses yields a total requirement of 3232 addresses. This requires a subnet prefix of /27/27 (232−27=322^{32-27} = 32). A /28/28 subnet only provides 1616 addresses (1111 usable), which is insufficient.
Azure reserves the first four and the last IP address in every subnet, which must be factored into sizing calculations.
2
Determine the minimum subnet size for Azure Bastion.
The subnet for Azure Bastion must be named exactly AzureBastionSubnet and requires a prefix of /26/26 or larger.
Azure Bastion has strict prefix size limits; configuring a prefix smaller than /26/26 (such as /27/27) will cause deployment failures.
3
Determine the minimum subnet size for the Virtual Network Gateway.
The subnet for the gateway must be named exactly GatewaySubnet and requires a prefix of /29/29 or larger.
Azure Virtual Network Gateways require at least a /29/29 prefix size to support gateway instances; a /30/30 subnet is invalid.

Anahtar Kavram

Azure Virtual Network Subnet sizing constraints, reserved IP addresses, and service-specific subnet requirements (Azure Bastion and GatewaySubnet).
Bu soruyu puanla

Konular

Create and Configure Virtual Networks and Subnets