Correct Answer: Configure Access Restrictions in the App Service Networking settings, adding an Allow rule for the partner's CIDR IP range and a default Deny rule for all other traffic.
Access Restrictions in Azure App Service operate at the front-end load balancer level (before the traffic hits your dedicated worker instances). This blocks unauthorized requests a...
Correct Answer
Configure Access Restrictions in the App Service Networking settings, adding an Allow rule for the partner's CIDR IP range and a default Deny rule for all other traffic.
Why This Answer Is Correct
Access Restrictions in Azure App Service operate at the front-end load balancer level (before the traffic hits your dedicated worker instances). This blocks unauthorized requests at the platform layer, protecting your compute resource/worker CPU from being consumed by invalid traffic.
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 Azure App Service web app stores connection strings for a database. You need to ensure the connection string value is different between your staging and production deployment slots. Which approach is correct?
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?