Environment configuration in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use environment variables in microservices?

In a microservices system, why is it best practice to use environment variables for configuration?

A They allow each service to have different settings without changing code.

B They force all services to share the same configuration values.

C They automatically encrypt sensitive data without extra setup.

D They make the code run faster by caching configuration.

💡 Hint

Think about how you can change settings without touching the code.

Environment variables let each microservice have its own settings, like database URLs or API keys, without changing the code. This helps keep code clean and flexible.

❓ Architecture

intermediate

Centralized configuration management in microservices

Which architecture best supports managing environment configurations centrally for many microservices?

A Use a centralized config server that microservices query at startup or runtime.

B Each microservice reads its own local config file stored inside its container.

C Hardcode all configuration values in the microservices source code.

D Store configuration in a shared database that microservices update frequently.

💡 Hint

Think about a single place to update configs that all services can access.

A centralized config server allows all microservices to fetch their configuration from one place, making updates easier and consistent across services.

❓ scaling

advanced

Scaling environment configuration for hundreds of microservices

You have hundreds of microservices deployed across multiple environments (dev, staging, prod). What is the best approach to scale environment configuration management?

A Store all environment variables in each service’s container image to avoid external dependencies.

B Use a hierarchical configuration system with environment-specific overrides and a centralized config store.

C Manually update environment variables on each server hosting the microservices.

D Use a single flat configuration file shared by all microservices regardless of environment.

💡 Hint

Consider how to manage differences between environments and many services efficiently.

A hierarchical config system lets you define common settings and override them per environment. Combined with a centralized store, it scales well for many services and environments.

❓ tradeoff

advanced

Tradeoffs of storing secrets in environment variables

What is a key tradeoff when storing sensitive secrets (like API keys) in environment variables for microservices?

A They automatically rotate secrets without manual intervention.

B Environment variables are encrypted by default, so no extra security is needed.

C They cannot be changed without rebuilding the microservice container image.

D They are easy to use but can be exposed if the host system is compromised or logs environment data.

💡 Hint

Think about what happens if someone gains access to the server or logs.

Environment variables are convenient but not encrypted by default. If the host or logs are accessed by attackers, secrets can be exposed, so additional secret management is recommended.

❓ estimation

expert

Estimating configuration update impact in a microservices system

You have 200 microservices using a centralized config server. You plan to update a common environment variable used by 150 services. What is the best estimate of the impact on the system?

A All services will lose connectivity temporarily during the update.

B All 200 services will restart automatically to apply the new config immediately.

C Only the 150 services using the variable need to reload or restart to apply the change.

D No services will be affected until the centralized config server is restarted.

💡 Hint

Consider which services actually use the changed variable and how config updates propagate.

Only services that use the updated environment variable need to reload or restart to apply the change. Others remain unaffected, minimizing impact.