AZ-305 Practice Question 98: App Configuration Feature Flags Key Vault

Microsoft Azure Solutions Architect Expert (AZ-305) · Test 10 · question 8 of 10

Infrastructure Solutionseasy

A development team runs the same web application in three environments (dev, test and production) across several App Service instances. They want to turn features on or off for specific environments without redeploying code, keep all non-secret settings in one centrally managed store, and keep secrets such as connection strings out of that store while still letting the application resolve them by reference at startup. Which combination should you include in the design?

Select one answer
Show answer and explanation

Answer:

  • D. Use Azure App Configuration to manage feature flags, and store connection strings in Azure Key Vault, referenced from App Configuration using Key Vault references

Azure App Configuration provides centralized feature flag management with per-environment values that the application picks up without a redeploy. A Key Vault reference stored in App Configuration holds the secret's URI rather than its value, so the application resolves the reference through the App Configuration provider at startup while the actual secret stays only in Key Vault, satisfying both the centralization and the secret-isolation requirements.

Option A is wrong because per-instance application settings are not centrally managed across environments and store secrets in plain application settings rather than a dedicated secret store. Option B is wrong because Key Vault is built to store secrets, not feature flags, and mixing the two loses the feature management tooling that App Configuration provides. Option C is wrong because hardcoding connection strings in code exposes secrets in source control and still requires a redeploy to change them, which the requirement rules out.

Reference: Tutorial: Use Key Vault References in an ASP.NET Core App

Practice Test 10 ›

Study guides for AZ-305