Your company plans to deploy a new Azure virtual network named `VNet-Core` in an Azure sub… — Microsoft Azure Administrator (AZ-104)

Your company plans to deploy a new Azure virtual network named `VNet-Core` in an Azure subscription. The virtual network will be assigned the address space ` $172.16.0.0/22$ .

You need to configure the following three subnets within `VNet-Core`:
- A subnet for a VPN gateway named `GatewaySubnet`.
- A subnet for Azure Bastion named `AzureBastionSubnet`.
- A subnet named `Subnet-App` that must support at least $58$ virtual machines.

Which two of the following subnet configurations should you implement? (Select two.)

A
`GatewaySubnet` using the address range ` $172.16.0.0/30$ `
B
`AzureBastionSubnet` using the address range ` $172.16.1.0/27$ `
C
`Subnet-App` using the address range ` $172.16.2.0/27$ `
`Subnet-App` using the address range ` $172.16.2.0/26$ `Cevap
`AzureBastionSubnet` using the address range ` $172.16.3.0/26$ `Cevap

Cevap

The correct subnet configurations are Subnet-App using the address range 172.16.2.0/26 and AzureBastionSubnet using the address range 172.16.3.0/26.

The correct configurations are the workload subnet Subnet-App using the 172.16.2.0/26 address space and the AzureBastionSubnet using the 172.16.3.0/26 address space. Subnet-App requires 58 usable IP addresses. A /26 subnet provides 64 total addresses, leaving 59 usable after Azure's 5 reserved IP addresses are subtracted, which is sufficient. AzureBastionSubnet requires a prefix of at least /26, which is satisfied by 172.16.3.0/26.

Adım Adım Çözüm

Calculate the minimum prefix size required for Subnet-App to support at least

58

virtual machines.

/26

prefix is required.

Azure reserves

5

IP addresses in every subnet (the first four and the last one). For

58

virtual machines, the subnet must have a total capacity of at least

58 + 5 = 63

IP addresses. A

/27

subnet provides only

32

total addresses (

32 - 5 = 27

usable), whereas a

/26

subnet provides

64

total addresses (

64 - 5 = 59

usable), which meets the requirement.

Determine the prefix size requirement for AzureBastionSubnet.

A prefix size of

/26

or larger is required.

Azure Bastion requires a dedicated subnet named exactly `AzureBastionSubnet` with a prefix size of at least

/26

(e.g.,

/26

/25

, etc.) to accommodate its scale-out instances. A prefix of

/27

is invalid.

Determine the prefix size requirement for GatewaySubnet.

A prefix size of

/29

or larger is required.

The VPN Gateway requires a subnet named exactly `GatewaySubnet` with a prefix size of at least

/29

. A prefix of

/30

is invalid and has zero usable IP addresses after accounting for the

5

reserved IPs.

Verify that the chosen correct subnet address ranges do not overlap and fit within the VNet address space.

The subnet ranges `172.16.2.0/26` and `172.16.3.0/26` do not overlap and both reside within the `172.16.0.0/22` address space.

The `172.16.0.0/22` address space covers `172.16.0.0` through `172.16.3.255`. The subnets `172.16.2.0/26` (covering `172.16.2.0` to `172.16.2.63`) and `172.16.3.0/26` (covering `172.16.3.0` to `172.16.3.63`) are distinct and valid.

Anahtar Kavram

Azure virtual networks reserve five IP addresses in every subnet (first four and the last one). Dedicated subnets like GatewaySubnet (minimum /29) and AzureBastionSubnet (minimum /26) have strict prefix size constraints.

Tahmini Süre:2m 30s

Soru

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Konular