Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it as a result, these questions will not appear in the review screen.
You have an Azure subscription that contains an Azure Front Door Premium profile named AFD1 and an Azure Web Application Firewall (WAF) policy named WAF1. AFD1 is associated with WAF1.
You need to configure a rate limit for incoming requests to AFD1.
Solution: You configure a managed rule for WAF1.
Does this meet the goal?
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it as a result, these questions will not appear in the review screen.
You have an Azure subscription that contains an Azure Front Door Premium profile named AFD1 and an Azure Web Application Firewall (WAF) policy named WAF1. AFD1 is associated with WAF1.
You need to configure a rate limit for incoming requests to AFD1.
Solution: You modify the policy settings of WAF1.
Does this meet the goal?
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.
Jerilyn
3 hours agoNarcisa
13 days agoLashaunda
1 months agoGabriele
2 months agoMaurine
2 months agoTarra
3 months ago