What must be done on all managed hosts after the restoration of a config backup on a new console?

Question

Options

• ARestart the hostcontext service
• BRe-add all managed hosts
• CRestart the docker service
• DDelete all users

• A
  73% (46)
• B
  5% (3)
• C
  14% (9)
• D
  8% (5)

Explanation

Restarting the hostcontext service (A) is required because the restored configuration contains connection metadata (certificates, API keys, or trust relationships) that the service loaded at startup - a restart forces it to re-read and apply that restored state so managed hosts can re-establish communication with the new console. Re-adding all managed hosts (B) is unnecessary overhead; the backup already contains the host definitions, so they don't need to be registered again. Restarting the Docker service (C) would disrupt running containers and isn't required just to apply a config restore. Deleting all users (D) is destructive and irrelevant - user accounts are included in the backup and should be preserved, not wiped.

Memory tip: Think "restore → restart the host service." The hostcontext service is the bridge between the console and its managed hosts, so after swapping in a new console's config, that bridge must be rebuilt by restarting it.

No community discussion yet for this question.