AZ-900 Describe Azure architecture and services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Azure App Service

  Why it's wrong here

  Azure App Service is designed for hosting dynamic web applications that require server-side processing, such as ASP.NET, Node.js, or PHP. Even if you only deploy static files, App Service still runs on an App Service Plan that allocates dedicated compute instances (VMs) 24/7, resulting in continuous charges regardless of the actual workload. Additionally, it brings unnecessary features like auto-scaling, deployment slots, and built-in authentication that are overkill for a simple static site. Choosing App Service for static content means paying for compute horsepower that never executes code, which is far more expensive than Blob Storage.

• ✓

  Azure Blob Storage static website hosting

  Why this is correct

  Azure Blob Storage static website hosting is the most cost-effective option because it uses a built-in static website endpoint that serves content directly from a blob container. There is no compute resource to provision or pay for — you only incur storage costs and minimal data transfer fees. The service automatically scales to handle traffic spikes and requires no server administration, making it ideal for HTML, CSS, and JavaScript assets. This is a serverless hosting model, so you pay for exactly what you store and deliver, not for idle processing capacity.

• ✗

  Azure Virtual Machines

  Why it's wrong here

  Azure Virtual Machines provide full control over the OS and web server, but that flexibility comes with high operational and financial costs. You must select a VM size, pay for its compute capacity even when the site receives zero traffic, and handle OS patching, security updates, and web server configuration yourself. Hosting a static website on a VM requires maintaining an entire server infrastructure just to serve pre-rendered files, which is a classic anti-pattern for cost optimization. Additionally, ensuring high availability typically demands multiple VMs, load balancers, and storage accounts, exploding both complexity and expense.

• ✗

  Azure Kubernetes Service

  Why it's wrong here

  Azure Kubernetes Service is a container orchestration platform meant for running distributed, container-based applications that need dynamic scaling, service discovery, and rolling deployments. To host a static website on AKS, you would have to package the content into a container image, run a web server inside the container, and then manage a Kubernetes cluster with at least one node VM — all while paying for the control plane and underlying infrastructure. This is vastly over-engineered for static content; the operational overhead of managing pods, deployments, and ingress controllers brings no benefit for previously built files that could be served directly from blob storage. The cost and complexity are orders of magnitude higher than a serverless storage endpoint.

Go deeper

Related to this question