Feature Flags in Microservices — Concept Check
Questions on Feature Flags in Microservices. Feature flags decouple deployment from release; toggle features per environment or user segment without redeploying, enabling dark launches and A/B tests.
Questions in this quiz
7 questions on Feature Flags in Microservices — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A feature flag is enabled for 10% of users in a microservice. What is this an example of?
- AKill switch
- BDark launch
- CGradual rollout
- DA/B testing
2.A service uses feature flags to enable a new checkout flow for only 1% of users. What is this practice called?
- ADark launch
- BA/B testing
- CKill switch
- DGradual rollout
3.Which of the following allows you to switch feature flag providers without changing application code?
- ASpring Cloud Config
- BEnvironment variables
- CKubernetes ConfigMap
- DOpenFeature SDK
4.In Spring Boot, how can you toggle a feature flag without redeploying the application?
- ARewriting application code
- BKubernetes ConfigMap reload
- CChanging source code
- DRestarting the server
5.A team wants to disable a problematic feature immediately without code rollback. What should they use?
- AGradual rollout
- BA/B testing
- CDark launch
- DKill switch
6.A developer believes feature flags can only be used for on/off toggles. What is a more advanced use?
- AHard-coded logic
- BManual user updates
- CPercentage-based rollouts
- DStatic configuration
7.Which platform is NOT a feature flag provider?
- ALaunchDarkly
- BSpring Cloud Config
- CFlagsmith
- DUnleash