You have an Azure App Service web app named app-portal-prod that currently runs on the Basic B1 App Service plan. You need to implement a deployment slot named staging for testing. The staging slot must use a staging database, and the production slot must use a production database. These connection strings must remain with their respective slots after a slot swap operation. Which two actions should you perform? (Select two.)
- Scale up the App Service plan to the Standard S1 pricing tier.Answer
- Configure the connection strings in both slots and select the 'Deployment slot setting' option for each.Answer
- CScale up the App Service plan to the Basic B2 pricing tier.
- DConfigure autoscale rules for the web app with identical scale-in and scale-out thresholds of 80% CPU utilization.
Answer
Scale up the App Service plan to the Standard S1 pricing tier, and configure the connection strings in both slots and select the 'Deployment slot setting' option for each.
To use deployment slots, the App Service web app must run on a Standard, Premium, or Isolated App Service plan. Since the web app currently runs on a Basic B1 plan, scaling up to the Standard S1 tier is required to enable this capability. Additionally, by default, connection strings are swapped when a slot swap occurs. To ensure the production slot always points to the production database and the staging slot always points to the staging database, you must configure the connection strings in both slots as 'Deployment slot settings', which makes them sticky to the slot and prevents them from being swapped.
Step-by-Step Solution
Key Concept
Deployment slots require a Standard tier or higher App Service plan, and settings like connection strings must be explicitly configured as 'Deployment slot settings' to prevent them from being swapped.