Application settings and connection strings in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Azure App Service Application Settings

In Azure App Service, what is the primary purpose of application settings?

A To define the scaling rules for the app service

B To store the source code of the application

C To manage user access permissions to the app service

D To store configuration values that override settings in the app's code or config files at runtime

💡 Hint

Think about how you can change app behavior without changing code.

Application settings in Azure App Service allow you to override configuration values at runtime without modifying the app's code or configuration files.

❓ Configuration

intermediate

Correctly Configuring a Connection String in Azure App Service

You want to add a SQL Database connection string to your Azure App Service. Which of the following is the correct way to add it so that your app can access it securely?

A Hardcode the connection string inside your app's source code

B Add the connection string under 'Connection strings' in the Azure portal with the correct name and type, so it is injected as environment variables

C Store the connection string in a public blob storage and read it at runtime

D Add the connection string as a regular application setting without specifying the type

💡 Hint

Consider how Azure App Service manages connection strings differently from regular app settings.

Connection strings added under the 'Connection strings' section in Azure App Service are automatically injected as environment variables with the correct prefix and type, making them secure and easy to use.

❓ Architecture

advanced

Designing Secure Application Settings for Multi-Environment Deployment

You have a web app deployed in development, staging, and production environments. You want to manage application settings and connection strings securely and avoid accidental exposure or overwriting. Which approach best meets this requirement?

A Store all secrets directly in the app's code and deploy the same code to all environments

B Use the same application settings and connection strings for all environments to simplify management

C Use Azure App Service application settings and connection strings per environment, and store secrets in Azure Key Vault referenced by managed identity

D Use environment variables on your local machine and copy them manually to each environment

💡 Hint

Think about security and environment isolation best practices.

Using environment-specific app settings combined with Azure Key Vault and managed identities ensures secrets are stored securely and environments are isolated.

❓ service_behavior

advanced

Effect of Changing Application Settings at Runtime

After updating an application setting in Azure App Service via the portal, what happens immediately to the running application?

A The app service automatically restarts the app to apply the new settings

B The app continues running without any change until manually restarted

C The app crashes and stops running until fixed

D The app settings update only after redeploying the app

💡 Hint

Consider how Azure applies configuration changes to running apps.

When application settings are changed in Azure App Service, the platform restarts the app automatically to apply the new configuration.

❓ security

expert

Preventing Exposure of Sensitive Connection Strings in Logs

Your Azure App Service logs show connection strings in plain text, which is a security risk. What is the best way to prevent this exposure while keeping the app functional?

A Use Azure Key Vault references in application settings and configure the app to not log environment variables

B Remove all connection strings from the app and hardcode them in the source code

C Disable all logging in the app service to avoid logging sensitive data

D Store connection strings in a public GitHub repository for transparency

💡 Hint

Think about secure secret management and logging best practices.

Using Azure Key Vault references keeps secrets out of logs, and configuring the app to avoid logging environment variables prevents accidental exposure.

Practice

1. What is the main purpose of using Application settings in an Azure App Service?

easy

A. To store configuration values separately from the app code

B. To write application code directly in the Azure portal

C. To deploy the app to multiple regions automatically

D. To monitor app performance metrics

Solution

1. Step 1: Understand what application settings are

   Application settings hold configuration values like API keys or feature flags outside the app code.

2. Step 2: Identify the benefit of separation

   Separating settings allows changing them without redeploying or modifying the app code.

3. Final Answer:

   To store configuration values separately from the app code -> Option A

4. Quick Check:

   Application settings separate config from code [OK]

Hint: Settings keep config outside code for easy updates [OK]

Common Mistakes:

• Confusing settings with code deployment
• Thinking settings are for monitoring
• Assuming settings are for writing code

2. Which Azure CLI command correctly sets an application setting named MySetting with value Value123 for an App Service named MyApp?

easy

A. az webapp config appsettings set --name MyApp --resource-group MyGroup --settings MySetting=Value123

B. az webapp create appsettings add --name MyApp --settings MySetting=Value123

C. az appservice config set --app MyApp --setting MySetting=Value123

D. az webapp config connection-string set --name MyApp --settings MySetting=Value123

Solution

1. Step 1: Identify the correct Azure CLI command for app settings

   The command to set app settings is az webapp config appsettings set with parameters for app name, resource group, and settings.

2. Step 2: Check the syntax for setting a key-value pair

   The settings parameter uses key=value format, here MySetting=Value123.

3. Final Answer:

   az webapp config appsettings set --name MyApp --resource-group MyGroup --settings MySetting=Value123 -> Option A

4. Quick Check:

   Use az webapp config appsettings set with key=value [OK]

Hint: Use 'az webapp config appsettings set' with key=value [OK]

Common Mistakes:

• Using wrong command verbs like create or add
• Confusing app settings with connection strings
• Missing resource group parameter

3. Given this Azure CLI command output after setting a connection string:

{"id": "/subscriptions/123/resourceGroups/MyGroup/providers/Microsoft.Web/sites/MyApp/config/connectionstrings", "name": "MyApp", "connectionStrings": [{"name": "DbConn", "connectionString": "Server=myserver;Database=mydb;", "type": "SQLAzure"}]}

What will the app receive when accessing the connection string DbConn?

medium

A. An empty string because connection strings are not set this way

B. An error because the connection string type is missing

C. The string 'Server=myserver;Database=mydb;' as the connection string value

D. The connection string encrypted and unreadable

Solution

1. Step 1: Understand the connection string format in Azure

   The output shows a connection string named 'DbConn' with a valid connection string value and type 'SQLAzure'.

2. Step 2: Determine what the app receives

   The app reads the connection string value as plain text 'Server=myserver;Database=mydb;' to connect to the database.

3. Final Answer:

   The string 'Server=myserver;Database=mydb;' as the connection string value -> Option C

4. Quick Check:

   Connection strings provide plain text values to apps [OK]

Hint: Connection strings deliver plain text values to apps [OK]

Common Mistakes:

• Assuming connection strings are encrypted automatically
• Thinking type field is mandatory for usage
• Believing connection strings are empty if not set in code

4. You run this Azure CLI command to update an app setting:
az webapp config appsettings set --name MyApp --resource-group MyGroup --settings MySetting
But it fails with an error. What is the likely cause?

medium

A. The resource group name is incorrect

B. The setting value is missing after the key 'MySetting'

C. The app name 'MyApp' does not exist

D. The command should use 'appsettings add' instead of 'set'

Solution

1. Step 1: Check the command syntax for setting app settings

   The --settings parameter requires key=value pairs, but only 'MySetting' (key) is provided without a value.

2. Step 2: Identify the error cause

   Missing value after the key causes the command to fail due to invalid syntax.

3. Final Answer:

   The setting value is missing after the key 'MySetting' -> Option B

4. Quick Check:

   App settings need key=value pairs [OK]

Hint: Always provide key=value pairs for app settings [OK]

Common Mistakes:

• Omitting the value after the key
• Assuming 'set' is wrong command
• Ignoring error messages about syntax

5. You want to securely update a database connection string in your Azure App Service without restarting the app. Which approach is best?

hard

A. Edit the connection string directly in the app code and redeploy

B. Set the connection string as an environment variable in your local machine

C. Store the connection string in a public GitHub repo and pull it at runtime

D. Use Azure CLI to update the connection string via az webapp config connection-string set and enable slot settings

Solution

1. Step 1: Understand secure connection string management

   Updating connection strings via Azure CLI keeps secrets out of code and allows live updates.

2. Step 2: Use slot settings to avoid app restarts

   Enabling slot settings for connection strings prevents app restarts and keeps settings sticky to deployment slots.

3. Final Answer:

   Use Azure CLI to update the connection string via az webapp config connection-string set and enable slot settings -> Option D

4. Quick Check:

   Use CLI and slot settings for secure live updates [OK]

Hint: Update connection strings via CLI with slot settings [OK]

Common Mistakes:

• Changing connection strings in code causing redeploy
• Exposing secrets in public repos
• Setting local env vars which don't affect Azure app