A dashboard needs to show job statuses that change every few seconds, and a chat panel. Someone proposes one WebSocket for both. Talk me through the choice.

Answer it out loud before you open anything. The value of the flags below is in comparing them to what you actually said.

The situation behind the question

An internal ops tool. It is behind a corporate proxy at some customer sites, deployed behind a load balancer, and users keep it open in a background tab all day.

What it is really testing

Whether the candidate chooses a transport from the traffic shape and the operational environment, rather than from "WebSockets are the real-time solution". The two features have different directionality, and the deployment details in the scenario decide as much as the features do.

Where the mechanism is taught