AZ-400 Practice Question: Design and implement build and release pipelines
Which TWO tools can be used to manage feature flags in Azure DevOps pipelines?
⚠ Common exam trap
Many candidates confuse Azure App Configuration's feature flag capability with Azure Policy or Azure Monitor, assuming any Azure service with 'configuration' or 'monitoring' in its name can manage feature flags, but only App Configuration and third-party tools like LaunchDarkly are designed for this purpose.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
LaunchDarkly.
LaunchDarkly is a third-party feature management platform that integrates with Azure DevOps pipelines to control feature flag rollouts, targeting, and experimentation. It allows teams to toggle features on/off without redeploying code, making it a valid tool for managing feature flags in pipeline-driven deployments.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Azure Policy.
Why it's wrong here
Azure Policy is an Azure service that enforces organizational governance, compliance, and resource-level rules (e.g., tagging, allowed locations). It does not provide runtime feature flag evaluation or targeted rollout controls, so it cannot be used to manage feature flags.
- ✓
LaunchDarkly.
Why this is correct
LaunchDarkly is a widely adopted third-party feature management platform that supports feature flags, gradual rollouts, A/B testing, and real-time targeting across applications. It integrates with Azure DevOps for release pipelines, making it a valid tool for managing feature flags in Azure-hosted applications.
- ✓
Azure App Configuration.
Why this is correct
Azure App Configuration includes a built-in feature manager that lets you define and toggle feature flags, control percentage rollouts, and use filters for conditional activation. Because it is first-party in Azure, it is the primary native Azure service for feature flag management.
- ✗
Azure Monitor.
Why it's wrong here
Azure Monitor is a monitoring and diagnostics service that collects telemetry, metrics, and logs, and helps detect and troubleshoot application issues. It does not expose a mechanism to define or toggle feature flags, so it is unrelated to feature flag management.
- ✗
Azure Key Vault.
Why it's wrong here
Azure Key Vault is designed to safeguard cryptographic keys, secrets, and certificates, and provides controlled access to those sensitive items. It has no feature flag evaluation logic or rollout targeting capabilities, and using it for feature flags would be an inappropriate and insecure pattern.
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Feature
A feature is a distinct unit of functionality that delivers value to the user, often managed and tracked throughout the software development lifecycle.
Key term
Feature flag
A feature flag is a software development technique that allows developers to turn features on or off without deploying new code, enabling safer releases and testing.
About these practice questions
One of 823 original AZ-400 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.