AZ-305 · Question #249
Case Study 3 - Contoso Existing Environment: Technical Environment The on-premises network contains a single Active Directory domain named contoso.com. Contoso has a single Azure subscription…
The correct answer is C. deployment slots. When you deploy your web app, web app on Linux, mobile back end, or API app to Azure App Service, you can use a separate deployment slot instead of the default production slot when you're running in the Standard, Premium, or Isolated App Service plan tier. Deployment slots are…
Question
Options
- Athe Azure App Configuration service
- Ban Azure Container Registry instance
- Cdeployment slots
- DContinuous Integration/Continuous Deployment (CI/CD) sources
How the community answered
(37 responses)- A8% (3)
- B16% (6)
- C73% (27)
- D3% (1)
Explanation
When you deploy your web app, web app on Linux, mobile back end, or API app to Azure App Service, you can use a separate deployment slot instead of the default production slot when you're running in the Standard, Premium, or Isolated App Service plan tier. Deployment slots are live apps with their own host names. App content and configurations elements can be swapped between two deployment slots, including the production slot. Deploying your application to a non-production slot has the following benefits: * You can validate app changes in a staging deployment slot before swapping it with the production slot. * Deploying an app to a slot first and swapping it into production makes sure that all instances of the slot are warmed up before being swapped into production. This eliminates downtime when you deploy your app. * After a swap, the slot with previously staged app now has the previous production app. If the changes swapped into the production slot aren't as you expect, you can perform the same swap immediately to get your "last known good site" back. https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots
Topics
Community Discussion
No community discussion yet for this question.