Environment variables and configuration in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set an environment variable in an Azure App Service.

Azure

az webapp config appsettings set --name myApp --resource-group myResourceGroup --settings [1]=production

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

AAPP_ENV

BENV_MODE

CCONFIG

DSETTINGS

Attempts:

3 left

💡 Hint

Common Mistakes

Using generic names like SETTINGS which do not specify environment

Using variable names that are not recognized by the app

The APP_ENV variable is commonly used to specify the environment type like production or development.

2fill in blank

medium

Complete the code to retrieve an environment variable in an Azure Function app using Python.

Azure

import os
connection_string = os.getenv('[1]')

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

ADATABASE_URL

BAPPINSIGHTS_INSTRUMENTATIONKEY

CFUNCTIONS_WORKER_RUNTIME

DAzureWebJobsStorage

Attempts:

3 left

💡 Hint

Common Mistakes

Using unrelated environment variables like DATABASE_URL

Confusing runtime variables with storage connection strings

AzureWebJobsStorage is the environment variable that stores the connection string for Azure Functions storage account.

3fill in blank

hard

Fix the error in the Azure CLI command to list environment variables for a web app.

Azure

az webapp config appsettings [1] --name myApp --resource-group myResourceGroup

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

Alist

Bshow

Cget

Ddisplay

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'show' which is not a valid subcommand here

Using 'get' or 'display' which are invalid commands

The correct Azure CLI command to list app settings is az webapp config appsettings list.

4fill in blank

hard

Fill both blanks to set two environment variables in an Azure App Service.

Azure

az webapp config appsettings set --name myApp --resource-group myResourceGroup --settings [1]=true [2]=us-east

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

AFEATURE_FLAG

BREGION

CDEBUG_MODE

DLOCATION

Attempts:

3 left

💡 Hint

Common Mistakes

Using DEBUG_MODE instead of FEATURE_FLAG for feature toggling

Using LOCATION instead of REGION which is more common in Azure

FEATURE_FLAG is a common name for toggling features, and REGION specifies the deployment region.

5fill in blank

hard

Fill all three blanks to create a Python dictionary from environment variables for configuration.

Azure

config = {
  'env': os.getenv('[1]'),
  'debug': os.getenv('[2]') == 'true',
  'region': os.getenv('[3]')
}

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

AAPP_ENV

BDEBUG_MODE

CREGION

DFEATURE_FLAG

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing FEATURE_FLAG with debug variable

Using wrong variable names that do not match purpose

This dictionary reads APP_ENV for environment, DEBUG_MODE for debug flag, and REGION for location.

Practice

1. What is the main purpose of using environment variables in Azure web apps?

easy

A. To write application logic inside the environment

B. To separate configuration settings from the application code

C. To store large files for the application

D. To replace the need for a database

Solution

1. Step 1: Understand environment variables role

   Environment variables hold configuration data outside the code, making apps flexible and secure.

2. Step 2: Identify correct purpose in Azure context

   Azure web apps use environment variables to keep settings separate from code, allowing easy updates without code changes.

3. Final Answer:

   To separate configuration settings from the application code -> Option B

4. Quick Check:

   Environment variables separate config from code [OK]

Hint: Think: config outside code for easy updates [OK]

Common Mistakes:

• Confusing environment variables with code logic
• Using environment variables to store large files
• Assuming environment variables replace databases

2. Which Azure CLI command correctly sets an environment variable named API_KEY with value 12345 for a web app called myapp?

easy

A. az webapp config appsettings set --name myapp --resource-group mygroup --settings API_KEY=12345

B. az webapp set env --app myapp --key API_KEY --value 12345

C. az appservice env set --app myapp --name API_KEY --value 12345

D. az webapp config set --app myapp --env API_KEY=12345

Solution

1. Step 1: Recall Azure CLI syntax for setting app settings

   The correct command uses az webapp config appsettings set with --name, --resource-group, and --settings.

2. Step 2: Match command to given options

   az webapp config appsettings set --name myapp --resource-group mygroup --settings API_KEY=12345 matches the correct syntax exactly; others use incorrect commands or flags.

3. Final Answer:

   az webapp config appsettings set --name myapp --resource-group mygroup --settings API_KEY=12345 -> Option A

4. Quick Check:

   Use az webapp config appsettings set with correct flags [OK]

Hint: Remember: 'az webapp config appsettings set' sets env vars [OK]

Common Mistakes:

• Using wrong Azure CLI commands or flags
• Omitting resource group parameter
• Confusing appsettings with environment commands

3. Given this Azure web app environment variable setup:
API_URL=https://api.example.com
What will the following Python code print?

import os
print(os.getenv('API_URL'))

medium

A. os.getenv('API_URL')

B. API_URL

C. None

D. https://api.example.com

Solution

1. Step 1: Understand os.getenv behavior

   os.getenv('API_URL') fetches the value of environment variable 'API_URL' if set.

2. Step 2: Match environment variable value

   The environment variable 'API_URL' is set to 'https://api.example.com', so the print outputs this string.

3. Final Answer:

   https://api.example.com -> Option D

4. Quick Check:

   os.getenv returns env var value [OK]

Hint: os.getenv returns the variable's value, not the name [OK]

Common Mistakes:

• Expecting the variable name instead of its value
• Assuming None if variable is set
• Confusing function call with string output

4. You tried to update an environment variable in Azure CLI but the app still uses the old value. What is the most likely cause?

medium

A. Azure CLI does not support environment variable updates

B. You used the wrong variable name in the code

C. You forgot to restart the web app after updating the variable

D. Environment variables cannot be updated once set

Solution

1. Step 1: Understand environment variable update behavior

   After updating environment variables, Azure web apps often require a restart to apply changes.

2. Step 2: Identify common mistake

   Not restarting the app causes it to keep using old cached environment values.

3. Final Answer:

   You forgot to restart the web app after updating the variable -> Option C

4. Quick Check:

   Restart app to apply env var changes [OK]

Hint: Restart app after env var changes to apply them [OK]

Common Mistakes:

• Assuming variables update instantly without restart
• Confusing variable name errors with update issues
• Thinking Azure CLI cannot update variables

5. You want to securely store a database password as an environment variable in Azure App Service. Which approach is best practice?

hard

A. Use Azure Key Vault and reference the secret in the app settings

B. Store the password directly in the app settings as plain text

C. Hardcode the password inside your application code

D. Send the password as a query parameter in URLs

Solution

1. Step 1: Identify secure storage options

   Azure Key Vault is designed to securely store secrets like passwords and keys.

2. Step 2: Understand integration with app settings

   You can reference Key Vault secrets in Azure App Service app settings, avoiding plain text storage.

3. Step 3: Evaluate other options

   Storing passwords in plain text, code, or URLs exposes security risks and is not recommended.

4. Final Answer:

   Use Azure Key Vault and reference the secret in the app settings -> Option A

5. Quick Check:

   Use Key Vault for secure secret storage [OK]

Hint: Always use Key Vault for sensitive secrets [OK]

Common Mistakes:

• Storing passwords in plain text app settings
• Hardcoding secrets in code
• Exposing secrets in URLs