Microservices - Configuration and Secrets Management
A microservice continues to use old configuration values after deployment despite updates. What is the most probable reason?
A microservice continues to use old configuration values after deployment despite updates. What is the most probable reason?
medium📝 Analysis Q6 of 15
Step-by-Step Solution
Solution:
Step 1: Understand config update behavior
When config changes, microservices often need to reload or refresh config to apply updates.Step 2: Analyze options
The service did not reload or refresh its configuration after deployment correctly identifies that failure to reload config causes old values to persist. The configuration file was deleted accidentally would cause failure to load config, not old values. The microservice code has a syntax error preventing config loading is unrelated to config updates. The network connection to the config server is too fast is nonsensical.Final Answer:
The service did not reload or refresh its configuration after deployment -> Option AQuick Check:
Config updates require reload or refresh [OK]
Quick Trick: Config changes need reload to take effect [OK]
Common Mistakes:
- Assuming config updates apply automatically without reload
- Blaming network speed for config issues
- Confusing config file deletion with stale config usage
Master "Configuration and Secrets Management" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes