You administer an Azure Web Site named contoso. The development team has
implemented changes to the website that need to be validated.
You need to validate and deploy the changes with minimum downtime to users.
What should you do first?
A.
Create a new Linked Resource.
B.
Configure Remote Debugging on contoso.
C.
Create a new website named contosoStaging.
D.
Create a deployment slot named contosoStaging.
E.
Back up the contoso website to a deployment slot.
Explanation:
http://msdn.microsoft.com/en-us/library/vstudio/ht9h2dk8(v=vs.100).aspx
I think the answer maybe C
http://azure.microsoft.com/en-gb/documentation/articles/web-sites-staged-publishing/
0
0
I think it’s D
When you deploy your application to Azure Websites, you can deploy to a separate deployment slot instead of the default production slot, which are actually live sites with their own hostnames.
Furthermore, you can swap the sites and site configurations between two deployment slots, including the production slot. Deploying your application to a deployment slot has the following benefits:
* You can validate website changes in a staging deployment slot before swapping it with the production slot.
* After a swap, the slot with previously staged site now has the previous production site. If the changes swapped into the production slot are not as you expected, you can perform the same swap immediately to get your “last known good site” back.
* Deploying a site to a slot first and swapping it into production ensures that all instances of the slot are warmed up before being swapped into production. This eliminates downtime when you deploy your site. The traffic redirection is seamless, and no requests are dropped as a result of swap operations.
Reference: Staged Deployment on Microsoft Azure Websites
1
0
Sorry I meant D! 🙂
0
0
isnt it D??
0
0
+1 for D
0
0
Correct Answer is B
You never create a staging slot, it’s already created by default, you only need to choose to deploy in it. Since there is no such option to deploy in staging and test and do a VIP swap, the best answer is B.
0
0
This questions is relevant to Web Apps NOT Cloud Services.
Web apps can have multiple deployment slots. Cloud Services ONLY have Staging and Production.
0
0
Ans = D
0
0
A staging slot is not available by default see also:
https://azure.microsoft.com/en-in/documentation/articles/web-sites-staged-publishing/
First step is to add a staging Slot.
0
0
To create a deployment slot using the Azure PowerShell cmdlets, use the New-AzureWebsite
cmdlet and provide the name of the existing website in the Name parameter, and the name
of the new deployment slot in the Slot parameter. The following is an example.
$wsQASlot = “QA”
New-AzureWebsite -Location $wsLocation -Name $wsName -Slot $wsQASlot
So you can create a Deployment Slot
0
0
D = Create a deployment slot
0
0
Correct. D.
0
0
Always a huge fan of linking to bloggers that I really like but dont get a great deal of link love from.
0
0
For sure it’s option D
0
0