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 configure regional virtual network integration for the staging slot to connect to a virtual network named VNet1. The production slot does not have virtual network integration configured. You perform a slot swap between the staging slot and the production slot. What is the status of the virtual network integration for the slots after the swap?
- The staging slot remains integrated with VNet1, and the production slot has no virtual network integration.Cevap
- BThe production slot becomes integrated with VNet1, and the staging slot has no virtual network integration.
- CBoth the production slot and the staging slot become integrated with VNet1.
- DThe slot swap fails because regional virtual network integration must be configured on both slots before a swap can occur.
Cevap
The staging slot remains integrated with VNet1, and the production slot has no virtual network integration.
Virtual network integration is a slot-specific (sticky) setting in Azure App Service. When you perform a slot swap, slot-specific settings do not change their assignment. Therefore, the staging slot retains its integration with VNet1, and the production slot remains without any virtual network integration.
Adım Adım Çözüm
Anahtar Kavram
Understanding which Azure App Service settings are sticky to the slot and do not swap during a slot swap operation.
Tahmini Süre:1m 30s