In a distributed database with replication, what are common strategies to handle network partitions while ensuring availability and consistency? A$.$ Switching to eventual consistency to allow reads and writes across partitions. B$.$ Limiting write operations to a single master node until partitions are resolved. C$.$ Using quorum$-$based reads and writes to maintain consistency across replicas. D$.$ Dropping partitions from the network until consistency is restored.