DRAG DROP
You administer an Azure Web Site named contosoweb that uses a production database. You deploy changes
to contosoweb from a deployment slot named contosoweb-staging.
You discover issues in contosoweb that are affecting customer data.
You need to resolve the issues in contosoweb while ensuring minimum downtime for users.
You swap contosoweb to contosoweb-staging.
Which four 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.
Select and Place:
Answer: 
Explanation:
Step 1: Make sure old production database is online.
Step 2: Set up staging database with the test database.
Step 3: Fix issues with test database.
Step 4: Once you have deployed and tested your new version on the staging environment, first point, then click
the SWAP button and Azure immediately makes your staging environment the live onehttp://azure.microsoft.com/en-us/documentation/articles/web-sites-staged-publishing/#Swap
The answer to this question is as confusing as hell. I thought the connection strings are swapped over?
Yes, because this is Microsoft, good at confusing people. Go to AWS if you want to play better Cloud.
They are swapped (by default), hence the reason they need to be changed. You swapped the “live” broken site into staging to fix. This kept the connection string pointing to the production database. You don’t test against your production database so this is swapped to the “test” database.
Same when you put it back after the issue is resolved and tested.
https://docs.microsoft.com/en-gb/azure/app-service/web-sites-staged-publishing#configuration-for-deployment-slots