Task 5
You need to ensure that requests for wwwjelecloud.com from any of your Azure virtual networks resolve to frontdoor1.azurefd.net.
Here are the steps and explanations for ensuring that requests for wwwjelecloud.com from any of your Azure virtual networks resolve to frontdoor1.azurefd.net:
Create a CNAME record with the following information1:
Source domain name: wwwjelecloud.com
Destination domain name: frontdoor1.azurefd.net
Save your changes and wait for the DNS propagation to take effect1.
Task 11
You are preparing to connect your on-premises network to VNET4 by using a Site-to-Site VPN. The on-premises endpoint of the VPN will be created on a firewall named Firewall 1.
The on-premises network has the following configurations:
* Internal address range: 10.10.0.0/16.
* Firewall 1 internal IP address: 10.10.1.1.
* Firewall1 public IP address: 131.107.50.60.
BGP is NOT used.
You need to create the object that will provide the IP addressing configuration of the on-premises network to the Site-to-Site VPN. You do NOT need to create a virtual network gateway to complete this task.
Here are the steps and explanations for creating the object that will provide the IP addressing configuration of the on-premises network to the Site-to-Site VPN:
On theCreate local network gatewaypage, enter or select the following information and accept the defaults for the remaining settings:
Name: Type a unique name for your local network gateway.
IP address: Type the public IP address of your VPN device, which is 131.107.50.60 in this case.
Address space: Type the internal address range of your on-premises network, which is 10.10.0.0/16 in this case.
Subscription: Select your subscription name.
Resource group: Select your resource group name.
Location: Select the same region as your virtual network.
SelectReview + createand then selectCreateto create your local network gateway2.
Task 5
You need to ensure that requests for wwwjelecloud.com from any of your Azure virtual networks resolve to frontdoor1.azurefd.net.
Here are the steps and explanations for ensuring that requests for wwwjelecloud.com from any of your Azure virtual networks resolve to frontdoor1.azurefd.net:
Create a CNAME record with the following information1:
Source domain name: wwwjelecloud.com
Destination domain name: frontdoor1.azurefd.net
Save your changes and wait for the DNS propagation to take effect1.
Task 11
You are preparing to connect your on-premises network to VNET4 by using a Site-to-Site VPN. The on-premises endpoint of the VPN will be created on a firewall named Firewall 1.
The on-premises network has the following configurations:
* Internal address range: 10.10.0.0/16.
* Firewall 1 internal IP address: 10.10.1.1.
* Firewall1 public IP address: 131.107.50.60.
BGP is NOT used.
You need to create the object that will provide the IP addressing configuration of the on-premises network to the Site-to-Site VPN. You do NOT need to create a virtual network gateway to complete this task.
Here are the steps and explanations for creating the object that will provide the IP addressing configuration of the on-premises network to the Site-to-Site VPN:
On theCreate local network gatewaypage, enter or select the following information and accept the defaults for the remaining settings:
Name: Type a unique name for your local network gateway.
IP address: Type the public IP address of your VPN device, which is 131.107.50.60 in this case.
Address space: Type the internal address range of your on-premises network, which is 10.10.0.0/16 in this case.
Subscription: Select your subscription name.
Resource group: Select your resource group name.
Location: Select the same region as your virtual network.
SelectReview + createand then selectCreateto create your local network gateway2.
You have an Azure subscription that contains a virtual network named VNet1. VNet1 contains a subnet named Subnet1
You deploy an instance of Azure Application Gateway v2 named AppGw1 to Subnet1. You create a network security group (NSG) named NSG1 and link NSG1 to Subnet1.
You need to ensure that AppGw1 will only load balance traffic that originates from VNet1. The solution must minimize the impact on the functionality of AppGw1.
What should you add to NSG1?
Gabriele
24 days agoMaurine
25 days agoTarra
1 months ago