AZ-104 Question #384: Real Exam Question with Answer & Explanation

Question

Hotspot Question You have an Azure web app named App1 that has two deployment slots named Production and Staging. Each slot has the unique settings shown in the following table. You perform a slot swap. What are the configurations of the Production slot after the swap? To answer, select the appropriate options in the answer area. NOTE: Each correction is worth one point. Answer:

Options

• __typehotspot
• variantdropdown

Explanation

The correct interaction involves selecting 'On' for Web sockets and 'App1-prod.contoso.com' for the Custom domain name, reflecting how application configuration settings typically swap with content while custom domains remain bound to their respective slots.

Approach. To determine the configurations of the Production slot after a swap, we need to understand how Azure App Service deployment slot swaps affect different settings. The core principle is that most application settings and configuration (unless explicitly marked as 'slot setting') swap with the content, while slot-specific configurations (like custom domains) remain with the slot.

1. Web sockets: This is a general application setting. Unless explicitly marked as a 'slot setting' (which is not the default for Web Sockets), such settings swap with the application content. The question implies a 'table' of unique settings was provided (though not shown), but the correct answer is 'On'. This means that before the swap, the application version residing in the Staging slot had 'Web sockets: On'. When this application is swapped into the Production slot, it brings its 'Web sockets: On' setting with it. Therefore, after the swap, the Production slot's Web sockets setting will be 'On'.

2. Custom domain name: Custom domain names are always tied to the specific deployment slot and do not swap with the application content. The domain App1-prod.contoso.com will always point to the Production slot, regardless of which application version is currently deployed there. Similarly, App1-staging.contoso.com will always point to the Staging slot. Therefore, after the swap, the Production slot will retain its original custom domain name: App1-prod.contoso.com.

Common mistakes.

• common_mistake. A common mistake is to assume that all settings are 'slot sticky' and remain with their original slot. If one were to assume Web sockets were slot-sticky, and if the original Production slot had Web sockets 'Off', then one might incorrectly select 'Off' after the swap. This is wrong because Web sockets configuration typically swaps with the application content. Another common mistake is believing that custom domain names swap with the application content, leading one to incorrectly select App1-staging.contoso.com for the Production slot after the swap. This is incorrect because custom domains are bound to the slot itself and do not change during a content swap.

Concept tested. The underlying technical concept being tested is the behavior of Azure App Service deployment slot swaps, specifically differentiating between 'slot-specific' (sticky) settings and 'content-swapped' settings. This includes understanding that custom domains are slot-specific, while general application settings like Web sockets typically swap with the deployed application content.

No community discussion yet for this question.