You manage an Azure web app in standard service tier at the following address: contoso.azurewebsites.net
Your company has a new domain for the site named www.contoso.com that must be accessible by secure
socket layer(SSL) encryption.
You need to add a custom domain to the Azure web app and assign an SSL certificate.
Which three actions should you perform? Each correct answer presents part of the solution.
A.
Add SSL binding for the www.contosco.com domain with the IP-based SSL option selected.
B.
Create a CNAME record from www.contoso.com to contoso.azurewebsites.net.
C.
Create a new file that will redirect the site to the new URL and upload it to the Azure Web site.
D.
Add SSL binding for the www.contoso.com domain with the server Name indication (SNL)SSL option
selected.
E.
Add www.contoso.com to the list of domain names as a custom domain.
Explanation:
Step 1: When adding a CNAME record, you must set the Host Name field to the sub-domain you wish to use.
For example, www. You must set the Address field to the .azurewebsites.netdomain name of your Azure
Website. For example, contoso.azurwebsites.net.
* Step 2: Modify the service definition and configuration files
Your application must be configured to use the certificate, and an HTTPS endpoint must be added. As a result,
the service definition and service configuration files need to be updated.
* Step 3:
IP based SSL associates a certificate with a domain name by mapping the dedicated public IP address of the
server to the domain name. This requires each domain name (contoso.com,
fabricam.com, etc.) associated with your service to have a dedicated IP address. This is the traditional method
of associating SSL certificates with a web server.
https://docs.microsoft.com/en-us/azure/app-service-web/app-service-web-tutorial-custom-ssl
SNI-based SSL – Multiple SNI-based SSL bindings may be added. This option allows multiple SSL certificates to secure multiple domains on the same IP address. Most modern browsers (including Internet Explorer, Chrome, Firefox, and Opera) support SNI (find more comprehensive browser support information at Server Name Indication).
IP-based SSL – Only one IP-based SSL binding may be added. This option allows only one SSL certificate to secure a dedicated public IP address. To secure multiple domains, you must secure them all using the same SSL certificate. This is the traditional option for SSL binding.
0
0
It’s B+D+E right?
0
0
I agree Mickey. There’s a simular question where you have to specify the correct order aswell. After a lot of discussion in the comments the community votes on:
B. Create a CNAME record from http://www.contoso.com to contoso.azurewebsites.net.
E. Add http://www.contoso.com to the list of domain names as a custom domain.
D. Add SSL binding for the http://www.contoso.com domain with the server Name indication (SNL)SSL option selected.
1
0
Yes im all over B+D+E
done it 100s of time in work
0
0
I would go with A+B+E
1
1
Me too, there is no reason to use SNI for a single domain.
0
2
Free and shared service plans do not support SSL at all.
Basic and greater support two custom SSL options, SNI-based (Server Name Indication) and IP-based (requires dedicated IP address).
If you bind an IP-based cert the App will be assigned a static IP address for SSL termination (I assume Azure does this at the load balancer). If you add a second SSL domain you will get charged for the extra IP with IP-based, for SNI additional domains are free. SNI is not supported by older browers/OSs however.
Update CNAME and add custom domain.
https://docs.microsoft.com/en-us/Azure/app-service/app-service-web-tutorial-custom-domain
Bind IP-based SSL cert.
https://docs.microsoft.com/en-gb/azure/app-service/app-service-web-tutorial-custom-ssl
A+B+E
1
1
Besides, SOME new 243Q 70-533 dumps for your reference:
https://drive.google.com/open?id=0B-ob6L_QjGLpfnV3MVl6X3pXOWw1Z3YtQUpJRVRiTkNkbGNFbVBNRXhjSkw3bWk1WHdYcW8
Best Regards!
0
0