Microservices - Configuration and Secrets Management
A microservice uses environment variables for config but still reads old values after update. What should be checked?
A microservice uses environment variables for config but still reads old values after update. What should be checked?
medium📝 Analysis Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Understand env var update behavior
Environment variables are read at process start; changes require restart to take effect.Step 2: Identify likely cause
If service not restarted, it keeps old env var values in memory.Final Answer:
Whether the service was restarted after env var change -> Option BQuick Check:
Env var changes need restart to apply [OK]
Quick Trick: Restart service after env var changes [OK]
Common Mistakes:
- Assuming env vars update live without restart
- Confusing config file presence with env vars
- Ignoring service restart requirement
Master "Configuration and Secrets Management" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes