Aha! I thought you might want details !!! OK so this is a "high level" diagram of the communication lines
"Coordinator leader election" and "Overlord leader election" is through Zookeeper. If ZK is down, then Druid will be unable to elect new leaders to control ingestion and to publish new data.
"Segment load/drop protocol between Coordinator and Historical" is those purple lines below: while the Coordinator will know that new data is available, it will not be able to tell Historicals to load the data - and it will not be able to rebalance the cluster, either.
"Segment "publishing" protocol from Historical" refers to that "OK" message that ingestion jobs get when data has been ingested, saying that it is safe. Therefore, ingestion will start to degrade.
"Overlord and MiddleManager task management" is, as you might expect, everything to do with the Overlord conducting its ingestion effectively. It will be unable to issue new tasks, for example.
Meanwhile, the broker will still have the timeline of data in memory - it will know where data is in the "last good state" - so querying will continue to work, notwithstanding those issues with ingestion above.
I hope this helps?