Azure App Service Zone-Redundant Redundancy
You have an Azure subscription that contains an Azure App Service app named App1 in a Standard App Service plan. App1 is accessed directly from the internet by using the following URL: https://app1.contoso.com. The Azure region that hosts App1 supports availability zones for App Service apps. You need to recommend a redundancy solution for App1. The solution must meet the following requirements: • Ensure that App1 is available if two availability zones fail. • Minimize administrative effort. • Minimize costs. What should you recommend?
Community Insight
The core concept tested is identifying that Premium v3 is the most cost-effective tier supporting Availability Zones. The common trap is selecting ASE v3, which offers higher isolation but violates the 'minimize costs' requirement due to its high base infrastructure fee.
This question explores how to achieve high availability for an Azure App Service app using Availability Zones while minimizing cost and administrative effort. The correct solution is to upgrade the existing plan to Premium v3, which natively supports zone-redundant deployments.
Learners often select Option D (ASE v3) because it provides strong isolation and zone redundancy. However, ASE v3 is significantly more expensive than Premium v3 and requires redeployment, making it the wrong choice when cost and administrative effort are prioritized.
Community Discussion (2 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option C is the correct recommendation because the Premium v3 tier of the Azure App Service Plan explicitly supports Availability Zones. Upgrading from Standard to Premium v3 allows you to enable zone redundancy without changing the deployment model or incurring the massive fixed costs associated with ASE. This meets all requirements: it ensures availability across zones, minimizes administrative effort by keeping the same app structure, and minimizes costs compared to ASE.Why the Other Options Are Wrong
Option A is incorrect because scaling out within a single region does not guarantee protection against zone failures unless zone redundancy is explicitly configured and supported by the tier; Standard plans do not support this. Option B involves creating a new plan and redeploying, which adds unnecessary administrative effort compared to simply upgrading the existing plan's tier (Option C). Option D (ASE v3) provides zone redundancy but is the most expensive option listed, violating the 'minimize costs' requirement.Community Comment Notes
Commenters like gpais note that while both Premium v3 and ASE v3 support zones, ASE carries a massive base infrastructure fee. Another commenter, Ras1364, points out that although ASE satisfies technical availability, it fails the exam logic regarding cost and administrative effort constraints.Exam Strategy
When evaluating cloud architecture options, always map the explicit constraints (like 'minimize cost') to the pricing models of the services. Remember that newer tiers (like Premium v3) often bring enterprise features (like AZ support) to simpler deployment models before requiring complex environments like ASE.
Frequently Asked Questions
Does Standard App Service support Availability Zones?
No, only Premium v2, Premium v3, and Enterprise tiers support Availability Zones for App Service apps.
Why not use ASE v3 for better isolation?
While ASE v3 offers isolation and zone redundancy, its high base cost violates the 'minimize costs' constraint in the scenario.
Related Analysis
Practice All AZ-305 Questions
Access 95 questions with complete answers and detailed explanations.
View Full AZ-305 Practice Test →