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 are developing a web app named mywebapp1
Mywebapp1 uses the address myapp1.azurewebsites.net.
You protect mywebapp1 by implementing an Azure Web Application Firewall (WAF)
The traffic to mywebapp1 is routed through an Azure Application Gateway instance that is also used by other web apps.
You want to secure all traffic to mywebapp1 by using SSL.
Solution: You open the Azure Application Gateway's HTTP setting and set the Override backend path option to mywebapp1.azurewebsites.net.
You then add an authentication certificate for mywebapp1.azurewebsites.net.
Does this meet the goal?
Click on the arrows to vote for the correct answer
A. B.B.
In case of end to end SSL, trusted Azure services such as Azure App service web apps do not require whitelisting the backends in the application gateway.
Therefore, there is no need to add any authentication certificates.
https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-web-app-overviewThe proposed solution does not meet the goal of securing all traffic to mywebapp1 by using SSL.
Setting the "Override backend path" option to mywebapp1.azurewebsites.net only overrides the backend path for requests that are sent to the backend pool. It does not configure SSL for the traffic that is routed through the Azure Application Gateway.
To secure traffic to mywebapp1 by using SSL, you need to configure SSL termination on the Azure Application Gateway. This involves creating an HTTPS listener, uploading an SSL certificate, and configuring the backend pool to use HTTPS.
Therefore, the correct answer is B. No.