Exam AZ-900 topic 1 question 7 discussion

Please read the requirements: Many are not noting here the load balancing fact. The web apps will use custom domains. (Basic, Shared and standard Support custom domain) The web apps each require 10 GB of storage. (basic and standard support this) The web apps must each run in dedicated compute instances.(basic support 3 instance max where standard support 10max) Load balancing between instances must be included. (free, shared and basic dont support load balancing. standard and above tier only support load balancing/autosacling) Costs must be minimized. Standard is less costier than premimum and isolated. I hope this is clear to chose the correct answer as STANDARD. https://azure.microsoft.com/en-us/pricing/details/app-service/windows/

the Answer is Standard : Standard tier support Custom Domains, Disk Space of 50GB wich is more than enough for the requested plan, and as long as they want to run each web app in a dedicated instance, that means we need 10 dedicated instances for the 10 web apps with a load-balancing service between them, the basic plan only support up to 3 dedicated instances. Finally the Standard plan has the lowest cost compared to Premuim and Isolated pricing tiers.

Key Points from Requirements: ✅ Custom domains → Requires at least Basic ✅ 10 GB x 10 apps storage = 100GB → Standard ✅ Dedicated compute instances → Basic or Standard ✅ Load balancing → Only Standard or Premium tiers ✅ Minimize cost → Choose the cheapest that meets requirements = Standard 👉 Answer: Standard (A)

The correct answer is A. Standard ✅ Here’s why the Standard tier is the best fit: 🔍 Requirements Breakdown - Custom Domains: Supported by Basic and Standard, but not Free or Shared - 10 GB Storage per App: Basic offers 10 GB total per plan—not per app—while Standard provides 50 GB per plan, which is more scalable - Dedicated Compute Instances: Only Basic and Standard tiers offer dedicated compute; Free and Shared use shared infrastructure - Load Balancing: Included in the Standard tier by default; Basic does not include built-in load balancing - Cost Minimization: While Basic is cheaper, it fails to meet all requirements. Standard is the lowest-cost tier that satisfies every condition So even though Basic might seem tempting for cost reasons, it falls short on storage and load balancing. Standard is the most cost-effective option that ticks every box.

Let’s go through the requirements one by one and match them with the Azure App Service pricing tiers. ✅ A. Standard ✅ Custom domains ✅ 10+ GB storage ✅ Dedicated compute instances ✅ Load balancing included 💰 Lowest-cost tier that includes all of the above ✔️ Correct Choice

|Support| Feature| Response | |-------|---------|----------| | Basic(free)| Docummentation |-| |Developer|dev/test environment|>8hrs| |Standard|Production workload|<1hr| |Professional Direct|Architecture, engineering, deployment plan|<1hr| |Premier|Onsite support, Review|Immediate|

Standard plan no longer exists. Standard should be replaced by Premium

You should choose the Basic App Service plan (B1). Custom domains: supported on Basic and above 10 GB storage: Basic provides 10 GB per instance Dedicated compute: Basic runs on dedicated VMs Built-in load-balancing: you can scale out to multiple B1 instances Lowest cost: Basic is the cheapest tier meeting all of the above Thus the Basic tier is your minimum-cost, requirements-compliant choice.

The Basic plan does not provide enough storage per app and lacks dedicated compute instances, making Standard the most suitable choice

Standard is mandatory because of the load balancing requirement Basic would work if not for load balancing (saves ~50% cost) Shared exists but is useless for your scenario (it's essentially "Free+")

O padrao sempre é o mais barato, e tem o balanceamento de cargas

Standard is mandatory because of the load balancing requirement Basic would work if not for load balancing (saves ~50% cost) Shared exists but is useless for your scenario (it's essentially "Free+")

A. Standard Explanation: Let's analyze the requirements against each plan: Requirement Free Shared Basic Standard Custom Domains ❌ No ✅ Yes ✅ Yes ✅ Yes 10 GB Storage per App ❌ No ❌ No ✅ Yes ✅ Yes Dedicated Compute Instances ❌ No ❌ No ✅ Yes ✅ Yes Load Balancing Included ❌ No ❌ No ❌ No ✅ Yes Minimized Costs ✅ Free ✅ Low ✅ Moderate ❌ Higher (but required for features) Reasoning: Free and Shared Plans do not support dedicated compute instances. Basic Plan supports dedicated compute instances and custom domains but does not include load balancing. Standard Plan supports all the required features, including load balancing, making it the best choice.

Correct answer should be A. Standard. The reason seems to be explicit here https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-app-service-limits. Analyzing the request: - web apps will use custom domain (Standard ✅, Basic ✅, Free ❌, Shared ✅) so we exclude already 'Free' - web apps each require 10 GB of storage (Standard ->50 GB ✅, Basic -> 10 GB ✅, Shared -> 1GB ❌) - Each must run in dedicated compute instances (ONLY Standard supports 10 dedicated instances) so STANDARD is the response.

The Standard service plan is designed for running production workloads. Pricing is based on the size and number of instances you run. Built-in network load balancing support automatically distributes traffic across instances. The Basic service plan is designed for apps that have lower traffic requirements, and don't need advanced auto scale and traffic management features. Pricing is based on the size and number of instances you run. Built-in network load balancing support automatically distributes traffic across instances.

basic plan doesnt support load balancing

Explanation: Custom Domains: Both the Basic and Standard tiers support custom domains, a requirement for web apps. Storage Requirements: Each web app requires 10 GB of storage. The Standard tier provides up to 50 GB of storage, accommodating all 10 apps (10 GB × 10 = 100 GB total requirement). The Basic tier also offers 10 GB per instance, but it has limitations on scaling and instances. Dedicated Compute Instances: Both Basic and Standard tiers provide dedicated compute instances, ensuring that the web apps are not running on shared resources. Load Balancing: Load balancing between instances is included in the Standard tier but not in the Basic tier. This makes the Standard tier more suitable for production workloads requiring such features. Cost Minimization: While the Basic tier is cheaper than the Standard tier, it does not meet all the requirements (e.g., load balancing). The Standard tier provides a balance between cost and features necessary for production-grade hosting