While debugging an issue for a client, we discovered that the SDAM implementation of the driver will remove a secondary from the topology if a new isMaster response of type Unknown comes back from that server, which does not follow the SDAM specification.