Releases, Migrations, and Config

1. What is the recommended practice for applying database migrations during a release?

Run migrations manually from a developer laptop Automatically at app start Emit a migration artifact and apply it before the new app version goes live Use auto-migration on test servers

2. Which of the following statements is true about configuration management for different environments?

All configurations are the same across environments Connection strings can be hardcoded in the source code Secrets should be stored in Azure Key Vault and injected at deploy time Environment variables are not used for configuration

3. Why is it important to write migrations to be backward compatible?

To save storage on the server To ensure no need for a rollback of the schema during application rollback To speed up deployment times To avoid using variable groups

4. What is the function of a feature flag system in application releases?

To roll out all new features simultaneously To allow for delayed deployment of features to selected programs To automate the migration process To store sensitive configuration data

Continue: Monitoring and Operations → Review this lesson Retake quiz