How should you configure WebApp1? To answer, select the appropriate options in the answer area. To enable WebApp1 to handle requests for the website: To point client connections to WebApp1:

Question

Explanation

This simulation tests your ability to configure a web application to serve a custom domain, requiring both server-side hostname binding and DNS-level redirection to route client traffic correctly.

Approach. To enable WebApp1 to handle requests for the website, you must add a custom domain (hostname binding) to the web app - in Azure App Service this is done via the 'Custom domains' blade, which tells the app service to accept HTTP requests for that domain name. To point client connections to WebApp1, you must create a DNS record (typically a CNAME record mapping your custom domain to the app's default hostname, e.g., webapp1.azurewebsites.net, or an A record pointing to its public IP) so that DNS resolves the domain to WebApp1's endpoint. Both steps are required: the DNS record routes traffic to the server, and the hostname binding tells the server which app to serve for that domain.

Concept tested. Custom domain configuration for a web application - specifically the two-part process of (1) server-side hostname/domain binding so the app accepts requests for a custom domain, and (2) DNS record configuration (CNAME or A record) so client traffic is directed to the correct web app endpoint.

Reference. Microsoft Learn - Configure a custom domain name in Azure App Service: https://learn.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-custom-domain

No community discussion yet for this question.