Examkin

Soru

Zorluk: OrtaCreate and Configure Virtual Networks and Subnets

Your company has an Azure subscription that contains a virtual network named `vnet-finance`. The virtual network is configured with the address space 192.168.32.0/22192.168.32.0/22. Currently, `vnet-finance` contains a subnet named `Subnet-Web` that uses the address range 192.168.32.0/24192.168.32.0/24. You need to configure two new subnets to support the deployment of an Azure Bastion host and an Azure VPN Gateway. Which two of the following subnets can you create in `vnet-finance` to support these deployments? (Select two.)

  1. AzureBastionSubnet with the address range 192.168.34.0/26192.168.34.0/26Cevap
  2. GatewaySubnet with the address range 192.168.33.0/27192.168.33.0/27Cevap
  3. C
    AzureBastionSubnet with the address range 192.168.33.128/27192.168.33.128/27
  4. D
    GatewaySubnet with the address range 192.168.32.192/28192.168.32.192/28

Cevap

The correct subnets are the AzureBastionSubnet with the range 192.168.34.0/26 and the GatewaySubnet with the range 192.168.33.0/27.
The correct subnets are AzureBastionSubnet with range 192.168.34.0/26192.168.34.0/26 and GatewaySubnet with range 192.168.33.0/27192.168.33.0/27. The Azure Bastion subnet is valid because it is named exactly 'AzureBastionSubnet', has a prefix of at least /26/26, and is in an unallocated portion of the VNet. The VPN Gateway subnet is valid because it is named exactly 'GatewaySubnet', has a prefix of /29/29 or larger, and is also in an unallocated portion of the VNet.

Adım Adım Çözüm

1
Determine the available address ranges in the virtual network.
The VNet has the address range 192.168.32.0/22192.168.32.0/22 (spans 192.168.32.0192.168.32.0 to 192.168.35.255192.168.35.255). The existing Subnet-Web occupies 192.168.32.0/24192.168.32.0/24 (spans 192.168.32.0192.168.32.0 to 192.168.32.255192.168.32.255). This leaves 192.168.33.0/24192.168.33.0/24, 192.168.34.0/24192.168.34.0/24, and 192.168.35.0/24192.168.35.0/24 completely unallocated.
This establishes the boundaries of free IP blocks to avoid overlapping subnet definitions.
2
Verify the subnet naming and sizing requirements for Azure Bastion.
Azure Bastion requires a dedicated subnet named exactly 'AzureBastionSubnet' and must be configured with a prefix size of /26/26 or larger. The option specifying AzureBastionSubnet with the range 192.168.34.0/26192.168.34.0/26 meets these criteria.
Azure Bastion requires at least a /26/26 address space for internal routing and scaling purposes.
3
Verify the subnet naming and sizing requirements for the Azure VPN Gateway.
The VPN Gateway requires a dedicated subnet named exactly 'GatewaySubnet' and must be configured with a prefix size of /29/29 or larger (Microsoft recommends /27/27 or /28/28). The option specifying GatewaySubnet with the range 192.168.33.0/27192.168.33.0/27 meets these requirements.
A dedicated GatewaySubnet is required to host the gateway instances and route hybrid connectivity traffic.

Anahtar Kavram

Azure virtual networks require dedicated, specifically named subnets with precise sizing constraints for native services like Azure Bastion (minimum /26 named AzureBastionSubnet) and VPN Gateway (minimum /29 named GatewaySubnet). All subnets inside a virtual network must have non-overlapping ranges.
Bu soruyu puanla

Konular

Create and Configure Virtual Networks and Subnets