Config server pattern in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary benefit of using a Config Server in microservices?

Consider a system with multiple microservices. What is the main advantage of introducing a Config Server pattern?

A Centralizes configuration management, allowing dynamic updates without redeploying services.

B Improves database query performance by caching configuration data locally.

C Automatically scales microservices based on configuration changes.

D Encrypts all network traffic between microservices to enhance security.

💡 Hint

Think about how configuration changes are managed across many services.

The Config Server pattern centralizes configuration so that all microservices can fetch their settings from one place. This allows updates without redeploying each service.

❓ Architecture

intermediate

Which component is essential in a Config Server architecture to notify microservices of configuration changes?

In a Config Server pattern, how do microservices learn about configuration updates without polling continuously?

A A database trigger that updates service code automatically.

B A load balancer that redirects traffic to updated services.

C A message broker or event bus that pushes change notifications to services.

D A firewall that blocks outdated configuration requests.

💡 Hint

Think about how systems communicate asynchronously to inform about changes.

Using a message broker or event bus allows the Config Server to push notifications to microservices, so they can reload configuration without polling.

❓ scaling

advanced

How does a Config Server pattern help scale microservices efficiently?

When the number of microservices grows rapidly, what role does the Config Server play in scaling configuration management?

A It reduces configuration duplication by serving a single source of truth, minimizing overhead during scaling.

B It automatically provisions new microservices with default configurations without human intervention.

C It caches all configurations locally on each microservice to avoid network calls entirely.

D It replaces the need for service discovery by embedding configuration in DNS records.

💡 Hint

Consider how managing many copies of configuration can become inefficient.

The Config Server provides a centralized source of configuration, preventing duplication and easing management as microservices scale.

❓ tradeoff

advanced

What is a potential drawback of using a Config Server pattern in microservices?

While Config Server centralizes configuration, what is a common tradeoff or risk introduced by this pattern?

A It forces all microservices to use the same programming language.

B It creates a single point of failure if the Config Server is not highly available.

C It requires each microservice to maintain its own local configuration copy permanently.

D It eliminates the need for environment-specific configurations.

💡 Hint

Think about what happens if the central configuration source becomes unreachable.

If the Config Server is down, microservices may fail to retrieve or refresh configurations, causing outages unless redundancy is implemented.

❓ estimation

expert

Estimate the approximate number of configuration requests per minute to a Config Server in a system with 500 microservices, each refreshing config every 5 minutes.

Assuming each of the 500 microservices requests configuration from the Config Server exactly once every 5 minutes, how many requests per minute does the Config Server handle?

A 2500 requests per minute

B 50 requests per minute

C 500 requests per minute

D 100 requests per minute

💡 Hint

Calculate total requests per 5 minutes, then divide by 5 to get per minute.

500 microservices * 1 request per 5 minutes = 500 requests per 5 minutes. Dividing by 5 gives 100 requests per minute.