PrepAway - Latest Free Exam Questions & Answers

Which three steps should you perform next in sequence?

DRAG DROP
You manage an Azure Web Site in Standard mode at the following address:
contoso.azurevvebsites.net.
Your company has a new domain for the site that needs to be accessible by Secure Socket
Layer (SSL) encryption.
You need to be able to add a custom domain to the Azure Web Site and assign an SSL
certificate.
Which three steps should you perform next in sequence? To answer, move the appropriate
actions from the list of actions to the answer area and arrange them in the correct order.
More than one order of answer choices may be correct You will receive credit for any of the
correct orders you select

PrepAway - Latest Free Exam Questions & Answers

Answer:

Explanation:

34 Comments on “Which three steps should you perform next in sequence?

    1. PNN says:

      If you use DNS A records configuration, 3 steps will not work. After step 4 you will need to update your new A records as the IP will change. Best answer to accomplish this will be steps 1,2,5




      0



      0
  1. CastorTray says:

    – Create a CNAME record from http://www.contoso.com to contoso.azurewebsites.net

    – Create a new file that will redirect the site to the new URL and upload it to Azure Web Site

    – Add SSL binding for the http://www.contoso.com domain with the IP=based SSL option selected

    *******************
    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.

    Reference: Enable HTTPS for an Azure website
    URL: http://azure.microsoft.com/en-us/documentation/articles/web-sites-configure-sslcertificate/




    0



    0
  2. Arie says:

    The best answer is to first create a CNAME record, then to add the domain name as a custom domain and last add the SNI SSL binding. The advantage of using a CNAME record and a SNI SSL binding is that it does not matter if the IP address of the website changes.




    0



    0
  3. Samji says:

    According to this link: http://azure.microsoft.com/en-us/documentation/articles/web-sites-custom-domain-name/

    Step 1 – Create DNS records (A or CNAME) (which means 1 or 3 as the first answer).
    Step 2 – Which is 2 as the second answer.

    Finally – http://azure.microsoft.com/en-gb/documentation/articles/web-sites-configure-ssl-certificate/

    Step 3 – Select 4 or 5 (4 is older for legacy browsers also / 5 is for modern browser incl)

    Which means select (1, 2, 4) or (1, 2, 5)




    0



    0
  4. Tester says:

    We need to have a ssl certificate issued to http://www.contoso.com or *.contoso.com.
    Our azure website contoso.azurewebsites.net needs to become http://www.contoso.com.
    If own the domain contoso.com we have control over the DNS for that domain.

    1. Add CNAME http://www.contoso.com > contoso.azurewebsites.net
    Our DNS will resolve http://www.contoso.com as contoso.azurewebsites.net and Azure DNS will resolve contoso.azurewebsites.net to the IP address.
    (Not an A record in contoso.com DNS because if the IP changes we do have to change the A record again at contoso.com DNS and in the mean time the site is not reachable.)

    4. In order to add the SSL certificate to the website we need to add the domain to the list of domain for the website. This will enable your website to respond to http://www.contoso.com

    2. Add the SSL binding as IP-Based SSL as it’s compatible with all browsers and the scenario does not talk about multiple domains for the same IP. If you select SNI you potential disrupt users using non SNI compatible browsers.

    http://azure.microsoft.com/en-us/documentation/articles/web-sites-custom-domain-name/
    http://blogs.msdn.com/b/kaushal/archive/2013/06/04/support-for-ssl-on-windows-azure-web-sites.aspx

    Summary:
    1 – Add DNS CNAME
    4 – Add SSL
    2 – Make http://www.contoso.com available




    0



    0
  5. My2Cents says:

    YOK: You start with option 2? That is impossible because the domain record cannot be verified if it hasn’t been created.

    Samji has given the correct answers! Remember that more answers are possible.




    0



    0
  6. fred says:

    There are 2 main steps to do in this order:
    registar for custom domain
    declare SSL configuration

    Let’s start with first step following this tuto:

    https://azure.microsoft.com/en-us/documentation/articles/web-sites-custom-domain-name/
    We have to configurate on registar platform and Azure portal

    First step
    —————–

    We could hesitate between 3 and 1. But the answer is 1 (explanation later)
    We do this on the registar platform

    Step 2
    ————–

    it’s 2
    We do this in the CONFIGURE tab on the Azure management portal

    step 3
    ————

    The previous steps created the custom domain. We now add SSL
    We do this on the portal in the CONFIGURE tab (SSL binding). We have to be on Standard tier.

    Two options: 4 or 5 (see last dropbox on the portal)

    We don’t have enough informations to choose (for instance 5 is not supported by every browsers)

    So two possible answers path.

    Why not 3?
    ————————

    We would be tied to a specific IP, that is not the best option.
    More important, we would have to create an awverify record that is not a proposed step
    So, bye 3!

    Why not 6?
    —————–

    what kind of file do you want to create? What is it’s name?
    Since when changing a DNS name has an impact on every web sites inside the domain?
    What kind of configuration do you want to do in this step?

    If you have answers, that OK you may be right. But in between… bye 6!

    the only file that could impact is hosts file. But are you sure you are in the question?




    0



    0
    1. Peter says:

      Answer: 1, 2, 5
      Fred was on the right track.
      First 1 then 2
      When you bind your external domain on the preview portal to the .azurewebsites.net it states that you first have to create a CNAME with your provider that either points http://www.yourdomain.com to .azurewebsites.net, or from awverify.www.yourdomain.com to awverify..azurewebsites.net.

      Next you need to bind SSL. Why not before? Because you can’t. Your new domain name does not show in the pull-down menu for SSL binding before you have registered your new external name.
      Here have to choose between IP based SSL or SNI SSL. As you will be using the same ip-address SNI SSL is required (see https://azure.microsoft.com/en-us/documentation/articles/web-sites-configure-ssl-certificate/)

      Answer 6, I can only imagen that this is about URL rewrite in the web.config file ( but it is not mentioned properly). However, this would only be needed if the question would state that SSL needed to be enforced. But it only states that the site needs to be accessible via SSL.




      0



      0
  7. josef says:

    https://azure.microsoft.com/en-us/documentation/articles/web-sites-configure-ssl-certificate/

    1,6,4 or 5

    Note…”you will receive credit for any of the correct orders you select…”
    Means that there are different possible solutions not only one.

    issue with 5 according to the link above, since SNI is not working for older browser.
    6 because you have to alter the web.config. (perhaps “,,,,,,,,,,,,,,,,,,file name” is missing here?)

    the answer above should be wrong, since you can only assign SSL IP-based or SNI, but not both at the same time.




    0



    0
  8. rick says:

    chuck answer is actually very good, but the exam question changed recently. There are now only 5 choices available, the #4 IP-based binding was removed.

    Probably there were two good answers and Microsoft had to remove one.

    Therefore, I think the correct answer is 2,5,1.




    0



    0
  9. Bruno D'Amico says:

    Assuming that the Custom Domain Name was purchased and DNS A record is already configured to point to Azur Web Site

    Step 1 Create a CNAME record from http://www.contoso.com to contoso.aurewebsites.net (wait 48 hours for DNS to replicate record)
    Step 2 Add http://www.contoso.com to the list of domain names as a custom domain (Azure Portal)

    https://azure.microsoft.com/en-us/documentation/articles/web-sites-custom-domain-name/#create-an-awverify-record-a-records-only

    Step 3 Add SSL binding for the http://www.contoso.com domain with the IP-based SSL option selected (Azure Portal)

    https://azure.microsoft.com/en-us/documentation/articles/web-sites-configure-ssl-certificate/#3-configure-ssl-in-your-app




    1



    0
  10. Prady says:

    1 and 2 are steps 1 and 2 respectively.
    Between 4 and 5 for step 3, shouldn’t SNI (5) be the right one if we are not going with A record? Also because rick said #4 (IP based) was removed in the changed question from Microsoft?




    0



    0
  11. Dean says:

    There are two possible solutions.

    If using an IP SSL cert then you need to use the A record as it is fixed to the IP address. For A records you need to add the domain name to the custom domain list. Therefore one solution is 2,3 and 4

    If using an SNI cert you can use CNAME records. You do not need to add to the custom list. Therefore the other solution is 1 and 5.

    Step 6 is just stupid.




    0



    0
  12. Halley Headings says:

    In my opinion, aiotestking.com does a good job of covering subjects of this type. Even if sometimes deliberately contentious, the posts are in the main well-written and stimulating.

    healthierway.tumblr.com




    0



    0
  13. Pashh says:

    as per the Exam guide:
    Confguring a custom domain for a website

    Azure Websites are assigned to the azurewebsites.net domain. So, if your site name is contosoweb, then it is reachable at the URL contoso-web.azurewebsites.net.
    to confgure a custom domain for the site, such as contoso.com.
    Confguring a custom domain name requires the following steps:
    1. Obtain a custom domain from a domain registrar of your choice.
    2. Add DNS records for your domain using your domain registrar.
    3. Associate the custom domain with your Azure website

    1) If you use CNAME records, then your DNS records only indicate the custom domain and
    the Azure website URL it maps to.
    2) Associating the custom domain with the website
    After the CNAME records have been verifed, the last step is to associate your custom domain
    with your Azure Website.
    3)Confgure the SSL binding. Because you only have to be concerned with newer
    browsers, you should choose the SNI SSL option. If you had to support browsers
    older than what was specifed in the requirements, you could use IP-based SSL




    0



    0

Leave a Reply