You have an Azure App Service web app named WebApp1 that is hosted on a Standard (S1) App Service plan. WebApp1 has a production slot and a deployment slot named Staging. You need to configure the deployment slots to meet the following requirements:
- The database connection string must always point to the production database for the production slot, and to the staging database for the Staging slot, even after a slot swap is performed.
- A subset of users must be automatically routed to the Staging slot without requiring manual URL changes or custom cookies.
Which two configuration actions should you perform? (Select two.)
- Select the Deployment slot setting option for the database connection string in both slots.Cevap
- In the Deployment slots blade of the web app, set the Traffic % value of the Staging slot to a non-zero percentage.Cevap
- CConfigure the database connection string as a standard App Setting without selecting the Deployment slot setting option.
- DUpgrade the App Service plan to the Premium (P1v3) tier to enable slot traffic routing.
- ECreate a custom path-based routing rule in an Azure Application Gateway to distribute traffic between the slots.
Cevap
To meet the requirements, you must select the Deployment slot setting option for the database connection string in both slots, and set the Traffic % value of the Staging slot to a non-zero percentage in the Deployment slots blade of the web app.
Selecting the Deployment slot setting option ensures that the connection string remains with its respective slot and does not swap during a deployment slot swap. Setting the Traffic % value of the Staging slot to a non-zero percentage utilizes the native App Service routing capability to automatically distribute a percentage of production traffic to the Staging slot.
Adım Adım Çözüm
Anahtar Kavram
Azure App Service deployment slot settings (sticky settings) and slot traffic routing
Tahmini Süre:1m 30s