Creating a web app in Azure - Practice Exercises

Challenge - 5 Problems

❓ Architecture

intermediate

Choosing the right Azure App Service plan for a web app

You want to deploy a web app on Azure that needs to handle sudden traffic spikes and requires automatic scaling. Which Azure App Service plan should you choose?

A Free plan with limited CPU and memory, no auto-scaling

B Basic plan with manual scaling only

C Standard plan with auto-scaling and load balancing

D Shared plan with limited resources and no SLA

💡 Hint

Consider plans that support automatic scaling and load balancing for traffic spikes.

The Standard plan supports auto-scaling and load balancing, which is essential for handling sudden traffic spikes. Free and Shared plans have limited resources and no SLA, and Basic plan requires manual scaling.

❓ Configuration

intermediate

Configuring environment variables for an Azure web app

You want to securely store and access a database connection string in your Azure web app without hardcoding it in your code. Where should you configure this connection string?

A In a text file uploaded to the web app's root directory

B Directly inside the source code as a constant string

C In the Azure Storage Blob container

D In the web app's Application Settings under Configuration in Azure Portal

💡 Hint

Think about secure and manageable ways to store sensitive configuration data in Azure.

Application Settings in the Azure Portal allow you to store environment variables securely and access them in your app code without hardcoding. Storing in source code or text files is insecure. Azure Blob Storage is for file storage, not config.

❓ service_behavior

advanced

Understanding deployment slots behavior in Azure App Service

You have two deployment slots: production and staging. You deploy a new version to staging and want to swap it with production. What happens to the app settings marked as 'slot setting' during the swap?

A Slot settings remain with their respective slots and do not swap

B Slot settings swap along with the code and content

C Slot settings are deleted during the swap

D Slot settings are merged between slots after the swap

💡 Hint

Consider how slot settings are designed to keep environment-specific configurations isolated.

Slot settings are configuration values that stick to their deployment slot and do not move during a swap. This allows environment-specific settings to remain consistent.

❓ security

advanced

Securing Azure web app with Managed Identity

You want your Azure web app to access an Azure SQL Database securely without storing credentials in the app code or configuration. What is the best way to achieve this?

A Enable a system-assigned Managed Identity for the web app and grant it access to the database

B Store the database username and password in Application Settings

C Use a shared access signature (SAS) token in the app code

D Create a service principal and hardcode its credentials in the app

💡 Hint

Think about Azure features that allow apps to authenticate securely without secrets.

Managed Identity allows the web app to authenticate to Azure SQL Database securely without storing credentials. Other options involve storing secrets or hardcoding credentials, which is less secure.

✅ Best Practice

expert

Optimizing cost and performance for a global Azure web app

You have a web app serving users worldwide. You want to reduce latency and optimize costs while maintaining high availability. Which architecture should you implement?

A Deploy the web app in a single Azure region with Standard plan and use Azure CDN for static content

B Deploy multiple instances of the web app in multiple Azure regions with Traffic Manager and use auto-scaling in each region

C Deploy the web app in multiple regions but disable auto-scaling to save costs

D Deploy the web app in a single region with Premium plan and rely on Azure Front Door for global routing

💡 Hint

Consider global distribution, load balancing, and scaling features for performance and cost.

Deploying multiple instances in multiple regions with Traffic Manager provides global load balancing and failover. Auto-scaling in each region ensures performance and cost optimization. Single region deployments increase latency for distant users.

Practice

1. What is the main purpose of creating a web app in Azure?

easy

A. To create databases for applications

B. To store large amounts of data securely

C. To manage virtual machines

D. To make your website or service available online

Solution

1. Step 1: Understand the purpose of a web app

   A web app hosts websites or services so users can access them online.

2. Step 2: Compare options

   Options relate to storage, virtual machines, and databases, not web hosting.

3. Final Answer:

   To make your website or service available online -> Option D

4. Quick Check:

   Web app purpose = online availability [OK]

Hint: Web apps host websites or services online [OK]

Common Mistakes:

• Confusing web apps with databases
• Thinking web apps manage virtual machines
• Assuming web apps store data only

2. Which Azure CLI command correctly creates a web app named myapp123 in resource group mygroup with plan myplan?

easy

A. az webapp create --name myapp123 --resource-group mygroup --plan myplan

B. az webapp new --app myapp123 --group mygroup --plan myplan

C. az create webapp --name myapp123 --group mygroup --plan myplan

D. az webapp deploy --name myapp123 --resource-group mygroup --plan myplan

Solution

1. Step 1: Identify the correct Azure CLI syntax

   The correct command to create a web app is az webapp create with options --name, --resource-group, and --plan.

2. Step 2: Check each option

   az webapp create --name myapp123 --resource-group mygroup --plan myplan matches the correct syntax. Other options use incorrect subcommands like 'new', invalid syntax such as 'az create webapp', or 'deploy' which is for deployment not creation.

3. Final Answer:

   az webapp create --name myapp123 --resource-group mygroup --plan myplan -> Option A

4. Quick Check:

   Correct CLI command = az webapp create --name myapp123 --resource-group mygroup --plan myplan [OK]

Hint: Use 'az webapp create' with --name, --resource-group, --plan [OK]

Common Mistakes:

• Using 'az webapp new' instead of 'create'
• Mixing up option names like --app or --group
• Using 'deploy' instead of 'create'

3. What will happen if you run this command?

az webapp create --name myapp123 --resource-group mygroup --plan myplan

Assuming mygroup and myplan exist and myapp123 is unique.

medium

A. A new resource group named mygroup is created automatically

B. The command fails because the app name is not unique

C. A new web app named myapp123 is created in mygroup using myplan

D. The app service plan myplan is deleted

Solution

1. Step 1: Understand command prerequisites

   The command creates a web app if the resource group and plan exist and the app name is unique.

2. Step 2: Analyze the command effect

   Since all conditions are met, the web app named myapp123 is created in mygroup using myplan.

3. Final Answer:

   A new web app named myapp123 is created in mygroup using myplan -> Option C

4. Quick Check:

   Valid inputs create web app = A new web app named myapp123 is created in mygroup using myplan [OK]

Hint: Valid group, plan, unique name = web app created [OK]

Common Mistakes:

• Assuming resource group auto-creation
• Thinking app service plan is deleted
• Believing app name uniqueness is not required

4. You run this command but get an error:

az webapp create --name myapp123 --resource-group mygroup --plan myplan

What is the most likely cause?

medium

A. The app service plan myplan does not exist

B. The app name myapp123 is already taken

C. The resource group mygroup is missing

D. The Azure CLI is not installed

Solution

1. Step 1: Check prerequisites for the command

   The resource group and app service plan must exist before creating a web app.

2. Step 2: Identify the most common error

   If the resource group exists but the plan does not, the command fails with an error about the plan.

3. Final Answer:

   The app service plan myplan does not exist -> Option A

4. Quick Check:

   Missing plan causes error = The app service plan myplan does not exist [OK]

Hint: Check if app service plan exists before creating web app [OK]

Common Mistakes:

• Assuming resource group auto-creates
• Ignoring app name uniqueness errors
• Not verifying Azure CLI installation

5. You want to create a web app with a unique name myapp123 in resource group mygroup. The app service plan myplan is in the EastUS region. Which command correctly creates the web app ensuring it uses the same region?

hard

A. az webapp create --name myapp123 --resource-group mygroup --plan myplan --location EastUS

B. az webapp create --name myapp123 --resource-group mygroup --plan myplan

C. az webapp create --name myapp123 --resource-group mygroup --plan myplan --location WestUS

D. az webapp create --name myapp123 --resource-group mygroup --plan myplan --sku B1

Solution

1. Step 1: Understand app service plan location

   The web app inherits the region from the app service plan; specifying location is not needed.

2. Step 2: Analyze command options

   az webapp create --name myapp123 --resource-group mygroup --plan myplan uses the existing plan without location override, ensuring the web app is in EastUS. Adding --location when --plan is specified is invalid and causes errors. Adding --sku B1 is unnecessary and invalid for web app creation.

3. Final Answer:

   az webapp create --name myapp123 --resource-group mygroup --plan myplan -> Option B

4. Quick Check:

   Web app location = app service plan location [OK]

Hint: Web app location follows app service plan location; no need to specify [OK]

Common Mistakes:

• Adding --location causing conflicts
• Assuming location must be specified again
• Changing SKU without need