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.