AZ-400 ยท Deployment strategies
Feature flags with Azure App Configuration
Feature Manager, feature filters (percentage, targeting, time window), feature management libraries, decoupling deploy from release, flag lifecycle and cleanup.
Key points
- Feature flag: deploy code switched off, release later via configuration; deploy and release are decoupled, turning off needs no redeploy.
- Flags live in Azure App Configuration (Feature manager), read via a feature management library (Microsoft.FeatureManagement in .NET).
- Filters: PercentageFilter, TimeWindowFilter, TargetingFilter (users, groups, default rollout percentage).
- Give flags owners; remove them after full rollout.
Source: https://learn.microsoft.com/en-us/azure/azure-app-configuration/feature-management-dotnet-reference
Practice questions
Which built-in feature filter enables a feature only between a start and an end date and time?
- Microsoft.Percentage
- Microsoft.TimeWindow
- Microsoft.Targeting
- Microsoft.Schedule
Show answer
Answer: B. Microsoft.TimeWindow
Microsoft.TimeWindow takes Start and End parameters. Percentage and targeting filters decide by who or how many, not when.
Which filters ship with the Microsoft.FeatureManagement package?
- PercentageFilter
- GeoFilter
- TimeWindowFilter
- BrowserFilter
- TargetingFilter
Show answer
Answer: A. PercentageFilter, C. TimeWindowFilter, E. TargetingFilter
PercentageFilter, TimeWindowFilter and TargetingFilter (plus ContextualTargetingFilter) are built in. There is no geography or browser filter out of the box; you would write a custom one.
True or false: calling AddFeatureManagement() in .NET registers the TargetingFilter automatically.
Show answer
Answer: False
False. All built-in filters except TargetingFilter are added automatically; TargetingFilter is added with WithTargeting() because it needs a targeting context accessor.
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.
