Developing Solutions for Microsoft Azure (AZ-204) Practice Exam

What configuration setting remains specific to a particular deployment slot after a swap?

1. WebJobs content

2. Application settings

3. Publishing profiles

4. Connection strings

The correct answer is: Connection strings

The correct answer focuses on connection strings remaining specific to a particular deployment slot after a swap. In Azure App Service, when you configure your application, you can set up deployment slots for purposes such as staging, testing, or production. Each slot can have its own unique settings and configurations. Connection strings, which are used to connect your application to databases and storage services, can be specified to remain tied to a particular slot. This means that when a swap occurs between slots (for instance, swapping a staging slot with production), the connection strings specified for the staging slot do not get swapped to the production slot. Instead, the production connection strings remain intact in the production environment, ensuring that the application continues to operate without disruption due to changes in the database or service connections. In contrast, other configurations such as application settings may be marked as sticky to the slot they were created in but can be configured to swap as needed—depending on the intended use case. WebJobs content is an extension point for running background applications and can also be swapped along with the application itself. Publishing profiles, which manage the deployment mechanisms and settings, are not specific to a deployment slot and are generally shared across all slots. Thus, connection strings are the only configuration setting that inherently maintain