App Service plans and pricing tiers in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the pricing tier for an Azure App Service plan.

Azure

az appservice plan create --name myPlan --resource-group myResourceGroup --sku [1]

Drag options to blanks, or click blank then click option'

AB1

BFree

CStandard

DPremiumV2

Attempts:

3 left

💡 Hint

Common Mistakes

Using full tier names instead of SKU codes.

Using unsupported SKU codes.

The pricing tier is specified using the SKU code like 'B1' for Basic tier.

2fill in blank

medium

Complete the code to create an App Service plan with the correct pricing tier for production workloads.

Azure

az appservice plan create --name prodPlan --resource-group prodGroup --sku [1]

Drag options to blanks, or click blank then click option'

AB1

BF1

CD1

DS1

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Free or Basic tiers for production.

Using deprecated SKU codes.

The Standard tier 'S1' is suitable for production workloads.

3fill in blank

hard

Fix the error in the command to create an App Service plan with the PremiumV2 tier.

Azure

az appservice plan create --name premiumPlan --resource-group rg1 --sku [1]

Drag options to blanks, or click blank then click option'

APremium

BP1v2

CPremiumV2

DP2

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'PremiumV2' as SKU instead of 'P1v2'.

Using 'Premium' which is invalid SKU.

The correct SKU code for PremiumV2 tier is 'P1v2'.

4fill in blank

hard

Fill both blanks to create an App Service plan with the correct SKU and specify the operating system as Linux.

Azure

az appservice plan create --name linuxPlan --resource-group rgLinux --sku [1] --is-linux [2]

Drag options to blanks, or click blank then click option'

AB1

Btrue

Cfalse

DS1

Attempts:

3 left

💡 Hint

Common Mistakes

Setting '--is-linux' to false for Linux plans.

Using incorrect SKU codes.

Use 'B1' for Basic tier and '--is-linux true' to specify Linux OS.

5fill in blank

hard

Fill all three blanks to create a PremiumV3 tier App Service plan with 3 instances and enable zone redundancy.

Azure

az appservice plan create --name stdPlan --resource-group rgStd --sku [1] --number-of-workers [2] --zone-redundant [3]

Drag options to blanks, or click blank then click option'

AP1v3

B3

Ctrue

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong SKU codes.

Setting zone redundancy to false when needed.

Use 'P1v3' for PremiumV3 tier, set 3 instances, and enable zone redundancy with 'true'.

Practice

1. What does an Azure App Service plan primarily define for your web app?

easy

A. The amount of computing resources like CPU and memory allocated

B. The programming language your app uses

C. The number of users who can access your app

D. The database type your app connects to

Solution

1. Step 1: Understand the role of an App Service plan

   An App Service plan defines the compute resources such as CPU, memory, and storage that your app will use.

2. Step 2: Differentiate from other app settings

   It does not control programming language, user count, or database type, which are separate configurations.

3. Final Answer:

   The amount of computing resources like CPU and memory allocated -> Option A

4. Quick Check:

   App Service plan = compute resources [OK]

Hint: App Service plan = resources your app runs on [OK]

Common Mistakes:

• Confusing App Service plan with app code or database
• Thinking it controls user access limits
• Assuming it sets programming language

2. Which of the following is the correct way to specify a Standard pricing tier in an Azure App Service plan using Azure CLI?

easy

A. az appservice plan create --name MyPlan --resource-group MyGroup --plan-tier Standard

B. az appservice plan create --name MyPlan --resource-group MyGroup --sku Standard

C. az appservice plan create --name MyPlan --resource-group MyGroup --pricing-tier Standard

D. az appservice plan create --name MyPlan --resource-group MyGroup --tier Standard

Solution

1. Step 1: Recall Azure CLI syntax for App Service plan creation

   The correct parameter to specify pricing tier is '--sku' followed by the tier name like 'Standard'.

2. Step 2: Verify other options

   Options using '--tier', '--pricing-tier', or '--plan-tier' are invalid parameters and will cause errors.

3. Final Answer:

   az appservice plan create --name MyPlan --resource-group MyGroup --sku Standard -> Option B

4. Quick Check:

   Use --sku to set pricing tier [OK]

Hint: Use --sku to set tier in Azure CLI [OK]

Common Mistakes:

• Using incorrect parameter names like --tier or --pricing-tier
• Confusing plan name with tier parameter
• Omitting the resource group

3. Given an App Service plan with pricing tier set to 'Basic', what will happen if you try to enable autoscaling for your app?

medium

A. Autoscaling is enabled by default on Basic tier

B. Autoscaling will work because Basic tier supports it

C. Autoscaling will work only during business hours

D. Autoscaling will fail because Basic tier does not support autoscale

Solution

1. Step 1: Understand autoscaling support by pricing tiers

   Autoscaling is supported starting from the Standard tier and above, not in Basic tier.

2. Step 2: Apply this to the Basic tier scenario

   Since Basic tier lacks autoscale support, attempts to enable it will fail or be blocked.

3. Final Answer:

   Autoscaling will fail because Basic tier does not support autoscale -> Option D

4. Quick Check:

   Basic tier = no autoscale support [OK]

Hint: Autoscale needs Standard or higher tier [OK]

Common Mistakes:

• Assuming Basic tier supports autoscale
• Thinking autoscale is automatic on all tiers
• Confusing Basic with Standard tier features

4. You created an App Service plan with the SKU 'F1' but your app is not accessible publicly. What is the most likely cause?

medium

A. You must assign a custom domain to make it public

B. F1 tier does not support public access by default

C. F1 is a Free tier and may have limited outbound network access

D. F1 tier requires manual SSL configuration before public access

Solution

1. Step 1: Understand the Free (F1) tier limitations

   The Free tier (F1) has restrictions including limited outbound network access and possible cold start delays.

2. Step 2: Relate these limits to app accessibility

   Limited network access can cause the app to be unreachable or slow, but public access is allowed.

3. Final Answer:

   F1 is a Free tier and may have limited outbound network access -> Option C

4. Quick Check:

   F1 tier = limited network, possible access issues [OK]

Hint: Free tier has network limits causing access issues [OK]

Common Mistakes:

• Thinking Free tier blocks public access
• Assuming custom domain is required for public access
• Believing SSL setup is mandatory for access

5. You need to host a production web app with high traffic, custom domains, SSL, autoscaling, and daily backups. Which App Service plan pricing tier should you choose?

hard

A. Standard (S1)

B. Basic (B1)

C. Free (F1)

D. Shared (D1)

Solution

1. Step 1: Identify required features for production app

   High traffic, custom domains, SSL, autoscaling, and backups require a tier with advanced features.

2. Step 2: Match features to pricing tiers

   Standard tier supports autoscaling, custom domains, SSL, and backups. Basic lacks autoscaling and some features. Free and Shared tiers are limited.

3. Final Answer:

   Standard (S1) -> Option A

4. Quick Check:

   Production needs Standard tier features [OK]

Hint: Standard tier supports autoscale and backups [OK]

Common Mistakes:

• Choosing Free or Shared for production needs
• Assuming Basic supports autoscale
• Ignoring backup requirements