[Solved] What is wrong with this dynamic config listener code? config = {"level": "info"} function listenConfig() { configService.... What is wrong with this dynamic config listener code? | Microservices

Microservices - Configuration and Secrets Management

What is wrong with this dynamic config listener code?

config = {"level": "info"}
function listenConfig() {
  configService.onUpdate = (newConfig) => {
    config = newConfig
  }
}
listenConfig()
configService.triggerUpdate({"level": "debug"})
print(config["level"])

AMissing initial config load

BOverwriting onUpdate instead of adding listener

CIncorrect print syntax

DNo error, code works fine

Step-by-Step Solution

Solution:

Step 1: Analyze event listener assignment
Assigning onUpdate directly overwrites existing listeners, losing others.
Step 2: Correct approach
Should use addEventListener or similar to add without overwriting.
Final Answer:
Overwriting onUpdate instead of adding listener -> Option B
Quick Check:
Use addListener to avoid overwriting handlers [OK]

Quick Trick: Add listeners, don't overwrite event handlers [OK]

Common Mistakes:

Assuming direct assignment adds listener
Ignoring initial config load importance
Thinking print syntax causes error

Master "Configuration and Secrets Management" in Microservices

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Arch Try Challenge Design Recall Scale

More Microservices Quizzes

What is wrong with this dynamic config listener code?

Step 1: Analyze event listener assignment

Step 2: Correct approach

Final Answer:

Quick Check:

Want More Practice?