Environment-based configuration in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use environment-based configuration in microservices?

In a microservices system, why is environment-based configuration important?

A It removes the need for any configuration management tools.

B It allows each microservice to have different settings for development, testing, and production without changing code.

C It forces all microservices to share the same configuration regardless of environment.

D It makes microservices slower because they must read config files every time they run.

💡 Hint

Think about how settings like database URLs or API keys change between environments.

Environment-based configuration lets microservices adapt to different environments by changing settings without code changes. This supports safer deployments and easier testing.

❓ Architecture

intermediate

Best practice for storing environment configs in microservices

Which approach is best for storing environment-specific configuration in a microservices architecture?

A Hardcode all configs inside the microservice source code for consistency.

B Keep configs in a shared database that all microservices query on every request.

C Store configs in environment variables injected into each service container at runtime.

D Use local config files inside each microservice image that never change.

💡 Hint

Consider security, flexibility, and ease of updates without rebuilding images.

Environment variables injected at runtime allow secure, flexible config changes without rebuilding or redeploying microservices.

❓ scaling

advanced

Scaling environment configuration management for many microservices

You have 50 microservices deployed across multiple environments. What is the best way to manage environment-based configuration at scale?

A Store configs in a shared file system accessed by all microservices.

B Manually update environment variables on each microservice host for every environment.

C Embed all configs inside each microservice image to avoid external dependencies.

D Use a centralized configuration service that microservices query at startup or on config change events.

💡 Hint

Think about automation, consistency, and reducing manual errors.

A centralized config service provides a single source of truth, simplifies updates, and supports dynamic config changes at scale.

❓ tradeoff

advanced

Tradeoff of using environment variables vs config files in microservices

What is a key tradeoff when choosing environment variables over config files for environment-based configuration in microservices?

A Environment variables are easier to inject but harder to version control compared to config files.

B Config files are always more secure than environment variables.

C Environment variables require rebuilding the microservice image for every change.

D Config files cannot be encrypted while environment variables can.

💡 Hint

Consider how changes are tracked and managed in source control.

Environment variables are injected at runtime and not stored in source control, making versioning harder. Config files can be versioned but may require more management.

❓ estimation

expert

Estimating configuration update impact in a microservices system

You have 100 microservices deployed in production. You plan to update a shared environment variable used by 60 of them. How many microservices will need to be restarted or reloaded to apply the new config?

A 60 microservices need restart or reload to pick up the new environment variable.

B All 100 microservices need restart because environment variables are global.

C None need restart because environment variables update automatically at runtime.

D Only 1 microservice needs restart since it can broadcast the change.

💡 Hint

Think about how environment variables are loaded by processes.

Environment variables are loaded when a process starts. To apply changes, each affected microservice must restart or reload config.