You have an on-premises network and an Azure subscription. The subscription contains the following virtual network:
* Name:VNet1
* Address space: 10.10.0.0/16
* Subnet name: Subnet1
* Subnet1 address range: 10.10.0.0/16
You deploy an Azure Virtual Desktop host pool that contains 10 session hosts to Subnets.
You plan to deploy a VPN gateway to VNet1 and provide the session hosts with access to the on-premises network.
You need to ensure that you can deploy the VPN gateway.
What should you do first?
In order to deploy a VPN gateway to VNet1, you should first add a subnet named GatewaySubnet to VNet1. According to the Microsoft Official Guide AZ-140, 'You must create a gateway subnet for the virtual network that you plan to use for the gateway. The subnet must be named GatewaySubnet and it must use an address range that is large enough to accommodate the number of IP addresses that you plan to use for the gateway and its supporting resources.' Therefore, the first step to ensure that you can deploy the VPN gateway is to add a subnet named GatewaySubnet to VNet1.
You have the Azure Virtual Desktop deployment shown in the following table.
You plan to deploy a new host pool as shown in the following table.
You need to ensure that you can deploy the host pool.
What should you do?
You have an on-premises network and an Azure subscription. The subscription contains the following virtual network:
* Name:VNet1
* Address space: 10.10.0.0/16
* Subnet name: Subnet1
* Subnet1 address range: 10.10.0.0/16
You deploy an Azure Virtual Desktop host pool that contains 10 session hosts to Subnets.
You plan to deploy a VPN gateway to VNet1 and provide the session hosts with access to the on-premises network.
You need to ensure that you can deploy the VPN gateway.
What should you do first?
In order to deploy a VPN gateway to VNet1, you should first add a subnet named GatewaySubnet to VNet1. According to the Microsoft Official Guide AZ-140, 'You must create a gateway subnet for the virtual network that you plan to use for the gateway. The subnet must be named GatewaySubnet and it must use an address range that is large enough to accommodate the number of IP addresses that you plan to use for the gateway and its supporting resources.' Therefore, the first step to ensure that you can deploy the VPN gateway is to add a subnet named GatewaySubnet to VNet1.
You have an Azure Virtual Desktop deployment that contains a host pool. The pool has the following settings:
* Resource group: RG1
* Host pool name: Pool1
* Location: East US
* Host pool type: Pooled
The deployment contains the workspaces shown in the following table.
For Pool1, you plan to create a RemoteApp application group named AppGroup1.
In which workspaces can you register AppGroup1?
You have an on-premises network and an Azure subscription. The subscription contains the following virtual network:
* Name:VNet1
* Address space: 10.10.0.0/16
* Subnet name: Subnet1
* Subnet1 address range: 10.10.0.0/16
You deploy an Azure Virtual Desktop host pool that contains 10 session hosts to Subnets.
You plan to deploy a VPN gateway to VNet1 and provide the session hosts with access to the on-premises network.
You need to ensure that you can deploy the VPN gateway.
What should you do first?
In order to deploy a VPN gateway to VNet1, you should first add a subnet named GatewaySubnet to VNet1. According to the Microsoft Official Guide AZ-140, 'You must create a gateway subnet for the virtual network that you plan to use for the gateway. The subnet must be named GatewaySubnet and it must use an address range that is large enough to accommodate the number of IP addresses that you plan to use for the gateway and its supporting resources.' Therefore, the first step to ensure that you can deploy the VPN gateway is to add a subnet named GatewaySubnet to VNet1.
Currently there are no comments in this discussion, be the first to comment!