Dynamic configuration updates in Microservices - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to fetch the latest configuration from the config server.

Microservices

config = config_client.[1]('service-config')

Drag options to blanks, or click blank then click option'

Aget_config

Bretrieve_config

Cfetch_config

Dload_config

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'get_config' which might be a local cache fetch, not from the server.

Using 'load_config' which implies loading from a file, not a remote server.

The method fetch_config is used to retrieve the latest configuration from the config server in this microservice setup.

2fill in blank

medium

Complete the code to subscribe to configuration changes using the event listener.

Microservices

config_client.on('[1]', update_config_handler)

Drag options to blanks, or click blank then click option'

Aconfig_reload

Bconfig_change

Cconfig_update

Dconfig_refresh

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'config_update' which is less common as an event name.

Using 'config_reload' which is an action, not an event.

The event config_change is commonly used to notify services about configuration updates.

3fill in blank

hard

Fix the error in the code to reload configuration safely.

Microservices

if config_client.[1]():
    reload_configuration()

Drag options to blanks, or click blank then click option'

Aconfig_changed

Bis_updated

Chas_update

Dhas_new_config

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'has_new_config' which is not a standard method.

Using 'is_updated' which is ambiguous.

The method config_changed correctly checks if the configuration has changed before reloading.

4fill in blank

hard

Fill both blanks to implement a cache invalidation after config update.

Microservices

def update_config_handler(event):
    config_client.[1]()
    cache.[2]()

Drag options to blanks, or click blank then click option'

Arefresh_config

Bclear_cache

Cinvalidate_cache

Dreload_config

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'refresh_config' which might not trigger a full reload.

Using 'clear_cache' which is valid but less precise than 'invalidate_cache'.

After detecting a config update, reload_config refreshes the config, and invalidate_cache clears stale cache entries.

5fill in blank

hard

Fill all three blanks to implement a safe config update with version check and notification.

Microservices

def safe_update(new_config):
    if new_config.version [1] current_config.version:
        config_client.[2](new_config)
        notify_services('[3]')

Drag options to blanks, or click blank then click option'

A>

Bupdate_config

Cconfig_updated

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' which would allow older versions to overwrite newer ones.

Using wrong event names that do not notify services properly.

The code checks if the new config version is greater than the current one, then updates the config and notifies services with the 'config_updated' event.