You are planning the deployment of a new virtual network named `vnet-corporate` in an Azur… — Microsoft Azure Administrator (AZ-104)

You are planning the deployment of a new virtual network named `vnet-corporate` in an Azure subscription. The virtual network is configured with the address space $172.16.0.0/22$ . You must create subnets within the virtual network to meet the following requirements:
- Deploy Azure Bastion to allow secure administrative access to virtual machines.
- Create a subnet named `snet-web` that supports at least $60$ usable host IP addresses.
- Create a subnet named `snet-db` that supports at least $28$ usable host IP addresses.

You need to configure the subnet names and IP address prefixes to satisfy these requirements while minimizing address waste. Which subnet configuration should you use?

A
AzureBastionSubnet: $172.16.0.0/27$ ; snet-web: $172.16.0.128/25$ ; snet-db: $172.16.1.0/26$
AzureBastionSubnet: $172.16.0.0/26$ ; snet-web: $172.16.0.128/25$ ; snet-db: $172.16.1.0/26$ Cevap
C
snet-bastion: $172.16.0.0/26$ ; snet-web: $172.16.0.128/25$ ; snet-db: $172.16.1.0/26$
D
AzureBastionSubnet: $172.16.0.0/26$ ; snet-web: $172.16.0.64/26$ ; snet-db: $172.16.0.128/27$

Cevap

The configuration allocating AzureBastionSubnet as

172.16.0.0/26

, snet-web as

172.16.0.128/25

, and snet-db as

172.16.1.0/26

is correct because it satisfies the name and size requirements for Azure Bastion, accounts for the

5

reserved IP addresses in Azure subnets, and avoids subnet overlaps.

The correct configuration uses the exact name `AzureBastionSubnet` with a

/26

prefix, satisfying Azure Bastion requirements. It allocates a

/25

prefix for `snet-web` (providing

123

usable IPs, which is the smallest prefix satisfying the

60

host requirement) and a

/26

prefix for `snet-db` (providing

59

usable IPs, which is the smallest prefix satisfying the

28

host requirement) without overlapping any address ranges.

Adım Adım Çözüm

Determine Azure Bastion subnet constraints.

The subnet must be named exactly `AzureBastionSubnet` and have a prefix of

/26

or larger (minimum

64

IP addresses).

Azure enforces strict naming and sizing constraints on the Bastion subnet for deployment validation.

Calculate the prefix size for `snet-web` to support at least

60

usable host IPs.

/25

prefix is required.

Azure reserves

5

IP addresses per subnet (the first

4

and the last

1

). A

/26

prefix provides

64

total addresses, which leaves

64 - 5 = 59

usable host IPs (insufficient). A

/25

prefix provides

128

total addresses, leaving

128 - 5 = 123

usable host IPs, which meets the

60

hosts requirement.

Calculate the prefix size for `snet-db` to support at least

28

usable host IPs.

/26

prefix is required.

/27

prefix provides

32

total addresses, which leaves

32 - 5 = 27

usable host IPs (insufficient). A

/26

prefix provides

64

total addresses, leaving

64 - 5 = 59

usable host IPs, which meets the

28

hosts requirement.

Select and lay out non-overlapping ranges within

172.16.0.0/22

AzureBastionSubnet at

172.16.0.0/26

, snet-web at

172.16.0.128/25

, and snet-db at

172.16.1.0/26

This layout fits cleanly within the virtual network's address space without overlaps (AzureBastionSubnet spans

172.16.0.0

172.16.0.63

; snet-web spans

172.16.0.128

172.16.0.255

; snet-db spans

172.16.1.0

172.16.1.63

Anahtar Kavram

Azure virtual network subnets require specific planning for reserved addresses (first four and last one) and service-specific subnets (such as Azure Bastion requiring exactly AzureBastionSubnet with a minimum size of /26).

Tahmini Süre:1m 30s

Soru

Cevap

Adım Adım Çözüm

Anahtar Kavram

Sık Yapılan Hatalar

Konular