Which four steps should you perform in sequence?

DRAG DROP
You manage an application hosted on cloud services. The development team creates a new version of the
application. The updated application has been packaged and stored in an Azure Storage account.
You have the following requirements:
 Deploy the latest version of the application to production with the least amount
of downtime.
 Ensure that the updated application can be tested prior to deploying to the
Production site.
 Ensure that the original version of the application can be restored until the new
version is verified.
Which four steps should you perform in sequence? To answer, move the appropriate actions from the list
of actions to the answer area and arrange them in the correct order.

DRAG DROP
You manage an application hosted on cloud services. The development team creates a new version of the
application. The updated application has been packaged and stored in an Azure Storage account.
You have the following requirements:
 Deploy the latest version of the application to production with the least amount
of downtime.
 Ensure that the updated application can be tested prior to deploying to the
Production site.
 Ensure that the original version of the application can be restored until the new
version is verified.
Which four steps should you perform in sequence? To answer, move the appropriate actions from the list
of actions to the answer area and arrange them in the correct order.

Answer: See the explanation

Explanation:
Box 1: Create a new cloud service.
Box 2: Provide the URL to the development team.
Box 3: Deploy the new package to the Staging slot.
Box 4: Perform VIP SWAP
* Cloud Services provides more control and improved access to service instances than the Azure Web
Sites feature, with a cost for each role approximately the same as when using Web Sites Reserved mode.
Applications can be staged for final testing before release.
* Azure Cloud Services provides both a staging and a production area for roles you deploy; you can deploy
an application to either a staging or a production environment within the same Cloud Service. A common
scenario is to deploy first to the staging environment and then, at the appropriate time, move the new
version to the production environment. The only difference is in the URL you use to access them.
* The operations staff can deploy a new version of the application to the staging deployment slot, perform
some final tests, and then swap the production and staging slots to make the new version of the
application available to users.
Moving to Microsoft Azure Cloud ServicesURL: http://msdn.microsoft.com/en-us/library/ff803371.aspx



Leave a Reply 5

Your email address will not be published. Required fields are marked *


to easy

to easy

Could be right, but, the application is already hosted on a Cloud Service, so not sure why you would need to create another cloud service. Just need to create a Staging slot on the current Cloud Service, no option to do that in the ?

thus
Create Cloud Service (Not sure why you would do it again, but need to be 4 )
Deploy New package in the staging slot
Give URL to the Developers
Perform VIP swap

greg

greg

@ to easy; How could you deploy the new package as a Developer without knowing the URL 🙂

Create Cloud Service (Not sure why you would do it again, but need to be 4 )
Give URL to the Developers
Deploy New package in the staging slot
Perform VIP swap

rubenm

rubenm

You are managing the app, not developing.

I think you have to share the url with develop team for testing the app before deploy in pro(it’s a requirement), so…

ccasado

ccasado

1. Deploy to the staging of the existing cloud service
(in this point you can check / Test) It can be tested by anyone, better if not development (users or QA)

2. Provide URL to dev team (bad practice. check should be done by someone else). (I have to put 4 options(

3. Perform VIP Swap

4. Deallocate.