Skip to main content

Technical Lab: Provision an App Service plan

Questions​

Question 1 — Multiple Choice​

You need to host a web application on Azure App Service that must automatically scale based on demand, support up to 20 instances, and allow configuration of custom autoscale rules. Which App Service plan tier meets these requirements?

A) Free (F1) B) Basic (B1) C) Standard (S1) D) Shared (D1)

Question 2 — Technical Scenario​

A team has deployed three web applications on a single Basic B2 tier App Service plan. The three applications share the computational resources of this plan. The team notices that one of the applications consumes much more CPU than the others, degrading the performance of the other two.

What is the correct approach to isolate the applications' performance without creating a separate App Service plan for each one?

A) Increase the number of workers in the current plan via manual scale-out configuration. B) Move the applications to different tiers within the same plan. C) Separate the high-consumption application to a dedicated App Service plan in the same Resource Group. D) Enable the "App Isolation" feature available in the Basic tier.

Question 3 — True or False​

An App Service plan in the Free (F1) tier and one in the Shared (D1) tier both run applications on virtual machine instances dedicated exclusively to the subscriber, differing only in the amount of available CPU and memory resources.

True or False?

Question 4 — Technical Scenario​

A developer runs the following command to create an App Service plan:

az appservice plan create \
  --name meu-plano \
  --resource-group meu-rg \
  --sku B1 \
  --is-linux

Next, they try to deploy a Web App previously created on a Windows App Service plan in the same Resource Group, associating it with this new plan. The operation fails.

What is the most likely cause of the failure?

A) The B1 tier is not compatible with already created applications; a new Web App must be created from scratch. B) A Linux App Service plan cannot be in the same Resource Group as a Windows plan. C) The --is-linux flag requires the tier to be Standard or higher. D) A Web App created on a Windows plan cannot be migrated to a Linux plan.

Question 5 — Multiple Choice​

When comparing the pricing tier options of an App Service plan, which characteristic exclusively differentiates the Isolated (I1) tier from the Premium (P1v3) and Standard (S1) tiers?

A) Support for deployment slots for staging and production environments. B) Running the application in a completely isolated network environment (Azure App Service Environment). C) Ability to scale horizontally to more than 10 instances. D) Support for custom domains with SSL certificates.

Answer Key and Explanations​

Answer Key — Question 1​

Answer: C

The Standard tier is the first that offers native autoscale support with rules based on metrics (CPU, memory, request queue) and allows scaling up to 10 native instances, with expansion possibilities. The Free and Shared tiers do not allow scale-out. The Basic tier allows manual scale-out but does not support automatic autoscale with custom rules.

The main misconception represented by the distractors is confusing "manual scale-out" (available in Basic) with "rule-based autoscale" (exclusive to Standard and higher). Choosing B1 would result in absence of automatic scaling, requiring manual intervention even under load spikes.

Answer Key — Question 2​

Answer: C

In App Service, all applications within the same plan share the CPU and memory resources of that plan. There is no mechanism for isolation or resource prioritization between applications within the same plan. The only real solution is to move the problematic application to a separate plan.

Alternative A is incorrect because scaling the plan increases total resources but does not isolate consumption between applications. Alternative B is invalid since all applications in a plan must use the same tier. Alternative D describes a non-existent feature in the Basic tier.

Answer Key — Question 3​

Answer: False

In the Free and Shared tiers, applications run on instances shared with other subscribers (multitenant). There are no dedicated VMs. Instance dedication starts only from the Basic tier. The difference between Free and Shared lies in daily CPU limits and the possibility of using custom domains (available only in Shared).

This is a critical point for security and performance: applications in Free and Shared are on shared infrastructure, which implies noisy neighbors and absence of uptime SLA.

Answer Key — Question 4​

Answer: D

In Azure App Service, the operating system (Windows or Linux) is an immutable property of the Web App. An application created on a Windows plan cannot be associated with a Linux plan, as the runtime and execution model are incompatible. This limitation is independent of the tier or Resource Group.

Alternative B is a common misconception but incorrect: Windows and Linux plans can coexist in the same Resource Group. Alternative C is also false; the --is-linux flag is valid in any tier that supports Linux, including B1. Choosing option B would lead to unnecessary resource reorganization without solving the real problem.

Answer Key — Question 5​

Answer: B

The Isolated tier is the only one that runs applications within an Azure App Service Environment (ASE), which is dedicated infrastructure deployed within a customer's Virtual Network. This provides complete network isolation, dedicated inbound and outbound IP addresses, and compliance with strict regulatory requirements.

Alternatives A, C, and D describe features also available in Standard and Premium tiers, therefore they do not exclusively differentiate Isolated. The main conceptual error of the distractors is associating scale or SSL with isolation, when the real differentiator of the Isolated tier is the dedicated network topology via ASE.