Explore Azure App Service deployment slots Flashcards
What are deployment slots in Azure App Service?
a) Temporary storage areas for logs
b) Live apps with their own host names
c) Backup servers for disaster recovery
d) Pre-configured testing environments that can’t be swapped
b) Live apps with their own host names
What is one benefit of deploying an app to a non-production slot?
a) It reduces the number of required instances
b) It eliminates the need for a production environment
c) It allows validating changes before deploying to production
d) It prevents the app from scaling out
c) It allows validating changes before deploying to production
What happens to the previous production app after a slot swap?
a) It is deleted
b) It is moved to a backup server
c) It becomes the new staging slot
d) It remains in production alongside the new version
c) It becomes the new staging slot
What should be considered when scaling an app to a different App Service tier?
a) The app’s memory usage
b) The number of deployment slots supported by the tier
c) The app’s CPU utilization
d) The number of HTTP requests handled
b) The number of deployment slots supported by the tier
What happens during the first phase of a slot swap with preview?
a) The production slot is warmed up
b) The source slot’s instances are restarted
c) The target slot is deleted
d) All settings are removed from both slots
b) The source slot’s instances are restarted
How does App Service ensure that an application is warmed up after a swap?
a) By checking the CPU usage
b) By triggering HTTP requests to the app root
c) By deploying new instances
d) By scaling the app out
b) By triggering HTTP requests to the app root
What happens if an instance in the source slot fails to restart during a slot swap?
a) The swap operation completes with errors
b) The instance is replaced automatically
c) The swap reverts and stops
d) The operation ignores the failed instance
c) The swap reverts and stops
What is triggered if auto swap is enabled with custom warm-up?
a) Slot deletion
b) Continuous deployment
c) Application Initiation
d) Cache initialization
c) Application Initiation
What happens to the target slot during the slot swap operation?
a) It is warmed up
b) It remains online
c) It is stopped
d) It is deleted
b) It remains online
What must be true when swapping a staging slot with the production slot?
a) The production slot must be offline
b) The staging slot must be the target slot
c) The production slot must be the target slot
d) The staging slot must be swapped automatically
c) The production slot must be the target slot
Which of the following settings are not swapped during a slot swap?
a) General settings and connection strings
b) Publishing endpoints and custom domain names
c) Managed identities and app settings
d) WebJobs content and handler mappings
b) Publishing endpoints and custom domain names
How can you configure an app setting to stick to a specific slot?
a) Set the WEBSITE_OVERRIDE_PRESERVE_DEFAULT_STICKY_SLOT_SETTINGS
value to true
b) Add the setting in the Production slot only
c) Select the Deployment slot setting
checkbox in the Configuration page
d) Modify the web.config
file
c) Select the Deployment slot setting
checkbox in the Configuration page
What is the first step in manually swapping deployment slots?
a) Go to the Configuration page
b) Select the target slot from the App Service plan
c) Go to the Deployment slots page and select Swap
d) Modify the web.config
file
c) Go to the Deployment slots page and select Swap
What should you verify before performing a swap?
a) That the source slot is online
b) That production is your target slot
c) That the target slot is empty
d) That the source slot is disabled
b) That production is your target slot
What option allows you to preview how the target slot will run with the new settings before swapping?
a) Use diagnostic tools
b) Perform swap with preview checkbox
c) Restart the app service
d) Clone the source slot
b) Perform swap with preview checkbox