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.
Answer: See the explanation
Note:
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, simply click the
SWAP button and Azure immediately makes your staging environment the live onenTo Swap Deployment Slots
URL: http://azure.microsoft.com/en-us/documentation/articles/web-sites-staged-publishing/#Swap
This contradicts the answer to the SAME question here:
http://www.aiotestking.com/microsoft/which-four-steps-should-you-perform-next-in-sequence/
point contoso-staging to test db
fix issues in contoso-staging
point contoso-staging to prod-db
swap contoso-staging to contoso
So which is it??
well if you assume the formerly-production website was pointing to the production database before it was swapped out with the faulty staging version, then when it is swapped back into production once again, it will still point to the prod Db.
This negates the first line of the solution given here.
The steps Jedi refers to are correct.