Your company has an Azure subscription that contains a virtual network named `VNet1` in th… — Microsoft Azure Administrator (AZ-104)

Your company has an Azure subscription that contains a virtual network named `VNet1` in the East US region. `VNet1` is configured with the address space of ` $10.10.0.0/16$ `. You plan to deploy the following resources to `VNet1`:

- An Azure Bastion host to provide secure administrative access to your virtual machines.
- A web application tier that requires at least ` $27$ ` usable IP addresses.

You need to configure the subnets for these resources while minimizing the allocated address space for each subnet. Which two of the following subnet configurations should you recommend? (Select two.)

`AzureBastionSubnet` with an address space of ` $10.10.1.0/26$ `Answer
`subnet-web` with an address space of ` $10.10.2.0/27$ `Answer
C
`BastionSubnet` with an address space of ` $10.10.1.0/26$ `
D
`AzureBastionSubnet` with an address space of ` $10.10.1.0/27$ `
E
`subnet-web` with an address space of ` $10.10.2.0/28$ `

Answer

To support the requirements while minimizing address space, you must configure `AzureBastionSubnet` with an address space of `

10.10.1.0/26

` and `subnet-web` with an address space of `

10.10.2.0/27

The correct configurations are to use the naming convention `AzureBastionSubnet` with a minimum prefix of `

/26

` for Azure Bastion, and `subnet-web` with a `

/27

` prefix for the web application. A `

/27

` subnet allocates `

32

` total addresses, which yields exactly the required `

27

` usable addresses after deducting the `

5

` addresses reserved by Azure. This satisfies the host requirement while minimizing address space waste.

Step-by-Step Solution

Determine the constraints for the Azure Bastion subnet.

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

/26

` or larger.

Azure Bastion has strict naming and minimum prefix requirements for deployment.

Calculate the host capacity needed for the web application tier, accounting for Azure-reserved IPs.

Azure reserves `

5

` IP addresses in every subnet. Therefore, to get `

27

` usable IP addresses, the subnet must have a total size of at least `

27 + 5 = 32

` IP addresses.

Azure reserves the first four and the last IP address of any subnet for its internal services.

Map the required IP capacity to the smallest CIDR subnet mask.

A `

/27

` subnet mask provides exactly `

32

` addresses, satisfying the requirement.

A smaller subnet like `

/28

` only offers `

16

` total addresses (which means `

11

` usable), which is insufficient.

Key Concept

Azure-specific subnet constraints require accounting for five reserved IP addresses per subnet and specific naming and minimum size prefixes for platform services like Azure Bastion.

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics