AZ-305 ยท Application architecture design
Azure App Configuration: central settings and feature flags
Azure App Configuration (key-values, labels, feature flags, Key Vault references, snapshots) versus app settings, with managed identity access.
Key points
- Azure App Configuration: central settings for many apps and environments, with history and dynamic refresh.
- Labels: one key, different values per environment (dev, prod).
- Feature flags: switch features at runtime without redeploying.
- Key Vault references: store only the secret URI; the app reads Key Vault.
- Snapshots: immutable set of key-values for a release.
- Access: managed identity plus a data role, no connection strings.
Source: https://learn.microsoft.com/en-us/cli/azure/appconfig/kv?view=azure-cli-latest
Practice questions
In Azure App Configuration, what lets the same key hold a different value for development and production?
- A tag
- A snapshot
- A label
- A content type
Show answer
Answer: C. A label
A label is an attribute on a key-value; the same key can exist once per label (for example dev and prod), and the app selects the label it needs. Tags only describe key-values, a snapshot freezes a set of them, and content type describes the value format.
Which are reasons to choose Azure App Configuration over App Service app settings?
- One store shared by many applications and services
- Feature flags that change behavior without redeploying
- Immutable snapshots of a set of key-values
- It becomes the place to store secrets instead of Key Vault
- It removes the cost of a separate resource
Show answer
Answer: A. One store shared by many applications and services, B. Feature flags that change behavior without redeploying, C. Immutable snapshots of a set of key-values
App Configuration centralizes settings for many apps in one store, supports feature flags that switch behavior at runtime, and can freeze a release's configuration in an immutable snapshot. It does not replace Key Vault for secrets (it references them), and App Service app settings are already available without an extra resource, so cost is not the reason.
When you add a Key Vault reference to Azure App Configuration, the secret value is copied into the App Configuration store.
Show answer
Answer: False
False. A Key Vault reference stores only the identifier (URI) of the Key Vault object. The application resolves it and reads the value from Key Vault, so the identity running the app needs read access to the secret in Key Vault as well.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
