Examkin

Soru

Zorluk: OrtaCreate and Configure Virtual Networks and Subnets

An administrator is designing a virtual network named `vnet-prod` in an Azure subscription. The virtual network is assigned the address space 10.100.0.0/2210.100.0.0/22. The administrator needs to configure subnets to support the following requirements:

* A subnet named `subnet-app` to host at least 2727 virtual machines.
* A subnet named `AzureBastionSubnet` to enable secure administrative access.
* A subnet named `GatewaySubnet` to support a VPN gateway.

The administrator proposes the following subnet allocations:

* `subnet-app`: 10.100.0.0/2710.100.0.0/27
* `AzureBastionSubnet`: 10.100.0.32/2710.100.0.32/27
* `GatewaySubnet`: 10.100.0.64/2910.100.0.64/29

Which subnet in the proposed configuration will cause a deployment or configuration failure due to Azure subnet size constraints?

  1. AzureBastionSubnet onlyCevap
  2. B
    subnet-app only
  3. C
    GatewaySubnet only
  4. D
    All subnets are valid because they meet host count requirements and do not overlap.

Cevap

AzureBastionSubnet only
The subnet named AzureBastionSubnet is assigned the CIDR block 10.100.0.32/2710.100.0.32/27. The Azure Bastion service requires its subnet to be named exactly AzureBastionSubnet and to have a prefix size of /26/26 or larger (e.g., /26/26, /25/25, /24/24). A /27/27 subnet is too small, which will cause the deployment of the Azure Bastion host to fail. The subnet-app is valid because a /27/27 subnet offers 3232 IPs, and subtracting the 55 reserved IPs leaves exactly 2727 usable IPs for the virtual machines. The GatewaySubnet is valid because Azure supports a GatewaySubnet prefix size as small as /29/29.

Adım Adım Çözüm

1
Analyze the capacity and sizing for `subnet-app`.
The proposed subnet size is /27/27, which provides 25=322^5 = 32 total IP addresses. Since Azure reserves 55 IP addresses per subnet, the usable IPs equal 32−5=2732 - 5 = 27. This matches the requirement to host at least 2727 virtual machines, so this subnet configuration is valid.
To verify if the proposed address block satisfies the required host count when accounting for Azure's reserved IP addresses.
2
Evaluate the platform size constraint for `AzureBastionSubnet`.
Azure Bastion has a strict requirement that its dedicated subnet (`AzureBastionSubnet`) must be configured with a prefix of /26/26 or larger. The proposed allocation of 10.100.0.32/2710.100.0.32/27 uses a /27/27 prefix, which is invalid.
To check if the subnet size meets the minimum supported prefix size mandated by the Azure Bastion service.
3
Evaluate the platform size constraint for `GatewaySubnet`.
Azure virtual network gateways support a minimum subnet size of /29/29 (or larger, such as /28/28 or /27/27). The proposed allocation of 10.100.0.64/2910.100.0.64/29 uses a /29/29 prefix, which is technically valid.
To determine if the gateway subnet configuration meets Azure virtual network gateway specifications.

Anahtar Kavram

Azure subnets reserve 55 IP addresses for internal management (the first four and the last one). Additionally, certain Azure resources require dedicated subnets with minimum size constraints. For example, Azure Bastion requires a subnet named exactly `AzureBastionSubnet` with a minimum prefix size of /26/26, whereas a `GatewaySubnet` requires a minimum prefix size of /29/29.
Tahmini Süre:1m 30s
Bu soruyu puanla

Konular

Create and Configure Virtual Networks and Subnets