An organization hosts a web application on an Azure App Service named `hr-prod-app` that runs on a Standard (S1) App Service plan. You need to implement a new deployment slot named `hr-stage-app` to test code updates. To perform canary testing under production load, you must direct of incoming user traffic to the staging slot. Which two actions should you perform? (Select TWO.)
- Add a deployment slot named `hr-stage-app` to the `hr-prod-app` App Service.Answer
- From the Deployment slots blade of `hr-prod-app`, configure the Traffic % setting of the `hr-stage-app` slot to .Answer
- CScale up the App Service plan for `hr-prod-app` to the Premium V3 (P1v3) pricing tier.
- DCreate a Network Security Group (NSG) and configure inbound security rules with custom priority values to distribute traffic.
Answer
To implement the deployment slot and canary testing, you must add the deployment slot named `hr-stage-app` to the App Service, and then on the Deployment slots blade of `hr-prod-app`, configure the Traffic % setting of the `hr-stage-app` slot to .
To host the staging environment and route of production traffic to it, you must first create the deployment slot named `hr-stage-app` in the App Service. Since the App Service is running on a Standard (S1) plan, it natively supports up to deployment slots. Second, you use the built-in Testing in production feature on the Deployment slots blade of the production app (`hr-prod-app`) to set the Traffic % of the staging slot to . This redirects of incoming requests to the staging slot automatically.
Step-by-Step Solution
Key Concept
Azure App Service deployment slots and native traffic routing (testing in production) allow administrators to deploy code to non-production slots and route a specified percentage of production traffic to them without upgrading to Premium tiers if already on Standard.
Estimated Time:2m 0s