Correct Answer: Mark the connection string as a 'slot setting' (sticky setting) in the App Service configuration
Slot settings (sticky settings) are configuration values that do not move with a deployment slot swap. Each slot retains its own value for that setting, making it ideal for connect...
Correct Answer
Mark the connection string as a 'slot setting' (sticky setting) in the App Service configuration
Why This Answer Is Correct
Slot settings (sticky settings) are configuration values that do not move with a deployment slot swap. Each slot retains its own value for that setting, making it ideal for connection strings that differ between staging (pointing to test DB) and production (pointing to prod DB).
This question evaluates your knowledge of Azure App Service — a core concept tested in Microsoft Certified: Azure Developer Associate (AZ-204). Understanding Azure App Service is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
You are deploying a web application to Azure App Service. Your team uses slot deployments. After deploying a new version to the staging slot and running smoke tests, you swap staging to production. Users report the app is slow for the first few minutes after the swap. What feature eliminates this cold-start issue?
Your team deploys a new version of a web application to Azure App Service using deployment slots. After deploying to the staging slot and running smoke tests, you perform a slot swap to production. Users report a brief period where some requests returned a 500 error during the swap. What caused this, and how should you fix it?
Your web application hosted on Azure App Service needs to connect to an Azure SQL Database without storing the database connection string (including password) in any configuration file or environment variable. The solution must work without any code changes to the connection string format. Which feature achieves this?
You are hosting a REST API on Azure App Service. To comply with corporate security standards, the API must only accept requests from a single external partner company's static public IP address. The solution must run at the platform level to prevent invalid traffic from consuming compute resources in your App Service plan. How should you configure this?