Feature toggles in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of feature toggles in microservices?

Feature toggles are widely used in microservices architectures. What is their main purpose?

A To increase the database storage capacity for microservices

B To monitor network traffic between microservices

C To manage user authentication and authorization

D To enable or disable features dynamically without redeploying services

💡 Hint

Think about how feature toggles help developers control features during runtime.

Feature toggles allow teams to turn features on or off dynamically, enabling safer deployments and testing without redeploying code.

❓ Architecture

intermediate

Which component is best suited to centrally manage feature toggles in a microservices system?

In a microservices architecture, where should feature toggle states be stored and managed for consistency?

A In local files on each microservice's server

B In a centralized configuration service accessible by all microservices

C Hardcoded inside each microservice's source code

D Only in the client application that consumes the microservices

💡 Hint

Consider how to keep toggle states consistent and easily changeable across many services.

A centralized configuration service ensures all microservices read the same toggle states, enabling consistent behavior and easier updates.

❓ scaling

advanced

How to design feature toggles to minimize performance impact in a high-traffic microservices system?

You have many microservices receiving thousands of requests per second. How should feature toggles be designed to avoid slowing down the system?

A Cache toggle states locally in each microservice with periodic refresh from central store

B Query the central toggle store synchronously on every request

C Store toggles only in a database and query it directly for each request

D Disable feature toggles during peak traffic to improve speed

💡 Hint

Think about reducing network calls and latency for each request.

Caching toggle states locally reduces network overhead and latency, while periodic refresh keeps toggles up to date without impacting performance.

❓ tradeoff

advanced

What is a key tradeoff when using feature toggles for long-term code management?

Feature toggles help deploy features safely, but what is a common downside if toggles remain in code too long?

A Code complexity increases, making maintenance harder

B System automatically becomes slower over time

C Feature toggles cause database corruption

D Toggles prevent any new features from being added

💡 Hint

Consider how many toggles affect code readability and testing.

Keeping many toggles in code increases complexity and technical debt, making the system harder to maintain and test.

❓ estimation

expert

Estimate the storage size needed for feature toggle states in a microservices system with 1000 toggles and 50 microservices.

Each toggle state is stored as a boolean flag per microservice. Assuming each boolean uses 1 byte, estimate the total storage size in kilobytes (KB) needed to store all toggle states centrally.

A Approximately 500 KB

B Approximately 1000 KB

C Approximately 50 KB

D Approximately 20 KB

💡 Hint

Calculate total bytes as toggles × microservices × bytes per toggle, then convert to KB (1 KB = 1024 bytes).

1000 toggles × 50 microservices × 1 byte = 50,000 bytes ≈ 48.8 KB, rounded to approximately 50 KB.