BrainyBeeBrainyBee
ExploreBlogStart Studying
HomeDesigning Microsoft Azure Infrastructure Solutions (AZ-305)Quick Note — Recommend an Application Configuration Management Solution
LO Quick Note840 words

Quick Note — Recommend an Application Configuration Management Solution

AZ-305 › Unit 4: Design infrastructure solutions › Design an application architecture › Recommend an application configuration management solution

Quick Note — Recommend an Application Configuration Management Solution

A payments team rolls out a "5% discount" promotion at 09:0009{:}0009:00 on Black Friday. The discount is meant to expire at 17:0017{:}0017:00. Three engineers are needed to coordinate the change: one to update the appsettings.json in source control, one to redeploy four services in two regions, one to verify the change took effect everywhere. The deployment takes 22 minutes; by 09:3009{:}3009:30 traffic has spiked and the team is too busy to safely redeploy if anything needs adjusting. At 17:0017{:}0017:00 the same dance repeats, this time without the luxury of a low-load window. The fix is one architectural change: move all promotion configuration into Azure App Configuration with feature flags.…

Retrieval target

Objective
Recommend an Application Configuration Management Solution
Mode
Closed-book recall
Target time
5 minutes
Escalation
Open the full lesson after a miss

Decision anchors

PromptCompact answer
Azure App ConfigurationA managed centralised configuration store for application settings — key/value pairs with optional labels (e.g., Prod, Dev), feature flags, and JSON / XML / text content types. SDKs for .NET, Java, Python, JS auto-refresh on change. Replaces scattered appsettings.json per environment. Two tiers: Free (limited keys, no replication) and Standard (10K keys / store, geo-replication, 99.9% SLA).
App Configuration LabelAn optional secondary index on a key — same key can have different values per label (e.g., DB:ConnectionString with labels Prod, Dev, Test). Clients fetch values by (key, label). Replaces having three separate stores per env. Empty label = default. Recommended pattern: one store, label per environment, fetched at boot by the app's ASPNETCORE_ENVIRONMENT-equivalent var.
Feature flagA toggle stored in App Configuration that controls whether a code path is active at runtime. The Microsoft.FeatureManagement SDK reads the flag and gates code with if (await featureManager.IsEnabledAsync("NewCheckout")). Supports percentage rollout (gradual exposure), targeting (per-user, per-group), and time-window filters. Used to decouple deploy from release.
Key Vault reference (App Configuration)A special key in App Configuration whose value is a URI pointing at a Key Vault secret (@Microsoft.KeyVault(SecretUri=https://kv.vault.azure.net/secrets/db-pwd/)). The SDK resolves the reference using the app's managed identity at fetch time. The actual secret stays in Key Vault — App Configuration only carries the pointer.…

Read the answers once, then cover the right-hand column and reconstruct each one from the prompt. A useful answer names the requirement, the recommended control or service boundary, and the nearest alternative it rejects. If you can only recognize the answer after seeing it, retrieval is not yet secure.

Turn recall into an architecture answer

For recommend an application configuration management solution, state: choose X because constraints A and B apply; reject Y because it fails C; validate with evidence D.

Ninety-second explanation

Without notes, explain:

  1. What requirement signals this learning objective rather than a neighbouring one?
  2. Which two solution families are most likely to be compared?
  3. Which hard constraint eliminates the strongest distractor?
  4. What identity, network, data, or failure boundary must appear in the design?
  5. Which operational test would prove the recommendation works?

Then compare your explanation with the full lesson. Record the missing decision rule—not merely the missed product name—in your error log.

Loading flashcards…

When to open the full lesson

Open the curriculum-linked lesson when you cannot explain a comparison, when a scenario depends on a numeric limit or SKU feature, or when the service is on a retirement path. Use current Microsoft Learn documentation for availability, limits, pricing, naming, and migration milestones; the quick note is intentionally compact.

Source and freshness

Derived from the linked AZ-305 lesson and retrieval deck, grounded in both attached course sources. Reviewed 2026-08-02. Current Microsoft documentation controls changing product contracts.

All Designing Microsoft Azure Infrastructure Solutions (AZ-305) Study Resources

Related Notes

  • Recommend an Application Configuration Management Solution — Lesson4,001 words
  • AZ-305 Exam Map and Design Decision Playbook652 words
  • Unit 1 Capstone — Design identity, governance, and monitoring solutions668 words
  • Unit 1 Roadmap — Design identity, governance, and monitoring solutions639 words
  • Cram Sheet — Design authentication and authorization solutions632 words
  • Design Authentication and Authorization Solutions — Lesson4,263 words
  • Design Studio — Design authentication and authorization solutions734 words
  • Quick Note — Recommend an Authentication Solution758 words
  • Recommend an Authentication Solution — Lesson4,868 words
  • Quick Note — Recommend an Identity Management Solution796 words
  • Recommend an Identity Management Solution — Lesson5,982 words
  • Quick Note — Recommend a Solution for Authorizing Access to Azure Resources745 words

Ready to study Designing Microsoft Azure Infrastructure Solutions (AZ-305)?

Practice tests, flashcards, and all study notes — free, no sign-up.

Start Studying

Ready to study Designing Microsoft Azure Infrastructure Solutions (AZ-305)?

Practice tests, flashcards, and all study notes — free, no sign-up needed.

Start Studying — Free
Designing Microsoft Azure Infrastructure Solutions (AZ-305) ResourcesExplore All HivesBlogHome

© 2026 BrainyBee. Free AI-powered exam prep.

Recommend an Application Configuration Management Solution — quick retrieval

Card 1 of 4

Front of flashcard 1 of 4

Azure App Configuration

easy

A managed centralised configuration store for application settings — key/value pairs with optional labels (e.g., Prod, Dev), feature flags, and JSON / XML / text content types. SDKs for .NET, Java, Python, JS auto-refresh on change. Replaces scattered appsettings.json per environment. Two tiers: Free (limited keys, no replication) and Standard (10K keys / store, geo-replication, 99.9%99.9\%99.9% SLA).

app-configuration

Recommend an Application Configuration Management Solution — quick retrieval

Card 1

Front

Azure App Configuration

Back

A managed centralised configuration store for application settings — key/value pairs with optional labels (e.g., Prod, Dev), feature flags, and JSON / XML / text content types. SDKs for .NET, Java, Python, JS auto-refresh on change. Replaces scattered appsettings.json per environment. Two tiers: Free (limited keys, no replication) and Standard (10K keys / store, geo-replication, 99.9%99.9\%99.9% SLA).

Card 2

Front

App Configuration Label

Back

An optional secondary index on a key — same key can have different values per label (e.g., DB:ConnectionString with labels Prod, Dev, Test). Clients fetch values by (key, label). Replaces having three separate stores per env. Empty label = default. Recommended pattern: one store, label per environment, fetched at boot by the app's ASPNETCORE_ENVIRONMENT-equivalent var.

Card 3

Front

Feature flag

Back

A toggle stored in App Configuration that controls whether a code path is active at runtime. The Microsoft.FeatureManagement SDK reads the flag and gates code with if (await featureManager.IsEnabledAsync("NewCheckout")). Supports percentage rollout (gradual exposure), targeting (per-user, per-group), and time-window filters. Used to decouple deploy from release.

Card 4

Front

Key Vault reference (App Configuration)

Back

A special key in App Configuration whose value is a URI pointing at a Key Vault secret (@Microsoft.KeyVault(SecretUri=https://kv.vault.azure.net/secrets/db-pwd/)). The SDK resolves the reference using the app's managed identity at fetch time. The actual secret stays in Key Vault — App Configuration only carries the pointer.…

Recommend an Application Configuration Management Solution — quick retrieval

Card 1

Front

Azure App Configuration

Back

A managed centralised configuration store for application settings — key/value pairs with optional labels (e.g., Prod, Dev), feature flags, and JSON / XML / text content types. SDKs for .NET, Java, Python, JS auto-refresh on change. Replaces scattered appsettings.json per environment. Two tiers: Free (limited keys, no replication) and Standard (10K keys / store, geo-replication, 99.9%99.9\%99.9% SLA).

Card 2

Front

App Configuration Label

Back

An optional secondary index on a key — same key can have different values per label (e.g., DB:ConnectionString with labels Prod, Dev, Test). Clients fetch values by (key, label). Replaces having three separate stores per env. Empty label = default. Recommended pattern: one store, label per environment, fetched at boot by the app's ASPNETCORE_ENVIRONMENT-equivalent var.

Card 3

Front

Feature flag

Back

A toggle stored in App Configuration that controls whether a code path is active at runtime. The Microsoft.FeatureManagement SDK reads the flag and gates code with if (await featureManager.IsEnabledAsync("NewCheckout")). Supports percentage rollout (gradual exposure), targeting (per-user, per-group), and time-window filters. Used to decouple deploy from release.

Card 4

Front

Key Vault reference (App Configuration)

Back

A special key in App Configuration whose value is a URI pointing at a Key Vault secret (@Microsoft.KeyVault(SecretUri=https://kv.vault.azure.net/secrets/db-pwd/)). The SDK resolves the reference using the app's managed identity at fetch time. The actual secret stays in Key Vault — App Configuration only carries the pointer.…