Correct Answer: A The app must be running in the Standard, Premium, or Isolated tier in order for you to enable multiple deployment slots. If the app isn't already in the Standard, Premium, or Isolated tier, you receive a message that indicates the supported tiers for enabling staged publishing. At this point, you have the option to select Upgrade and go to the Scale tab of your app before continuing. Scale up: Get more CPU, memory, disk space, and extra features like dedicated virtual machines (VMs), custom domains and certificates, staging slots, autoscaling, and more. Scale out: Increase the number of VM instances that run your app. You can scale out to as many as 30 instances Reference: https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots https://docs.microsoft.com/en-us/azure/app-service/manage-scale-up

correct . For more read https://docs.microsoft.com/en-us/azure/app-service/manage-scale-up

To be able to create staging slots, your App Service plan must be running in the Standard, Premium, or Isolated tier. The Free and Shared (Basic) tiers do not support slots. Therefore, you need to scale up the App Service plan to a tier that supports deployment slots. The correct answer is: A. From Plan1, scale up the App Service plan.

correct

A) "From Plan1, scale up the App Service Plan" "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. " - https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots

A. is the right answer. From Plan1, scale up the App Service plan

A) "From Plan1, scale up the App Service Plan" "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. " - https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots

Correct Answer: A

A is correct

A is correct app must be running in the Standard, Premium, or Isolated tier in order for you to enable multiple deployment slots that you can use to test app in dev environment before deploy to production

A. From Plan1, scale up the App Service plan

A is correct, need to use Standard or higher.

Correct Answer

this question was there on 16/03/2022 with same question and passed with 900 percent

Scale up: Get more CPU, memory, disk space, and extra features like dedicated virtual machines (VMs), custom domains and certificates, ""staging slots"", autoscaling, and more. You scale up by changing the pricing tier of the App Service plan that your app belongs to.

https://docs.microsoft.com/en-us/azure/app-service/manage-scale-up

Changing your App Service plan (scale up) Your App Service plan can be scaled up and down at any time. It is as simple as changing the pricing tier of the plan. You can choose a lower pricing tier at first and scale up later when you need more App Service features. For example, you can start testing your web app in a Free App Service plan and pay nothing. When you want to add your custom DNS name to the web app, just scale your plan up to the Shared tier. Later, when you want to create an SSL binding, scale your plan up to Basic tier. When you want to have staging environments, scale up to Standard tier. When you need more cores, memory, or storage, scale up to a bigger VM size in the same tier. The same works in the reverse. When you feel you no longer need the capabilities or features of a higher tier, you can scale down to a lower tier, which saves you money.