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

Staged Deployment on Microsoft Azure Websites