Cassandra easy
In a Cassandra Keyspace, what does a 'Replication Factor of 3' specifically guarantee for your data redundancy?
- A Every table in the keyspace is split into 3 distinct shards to improve read performance.
- B Exactly three distinct copies of every data record are maintained on three different nodes in the cluster.
- C The cluster will automatically replicate all data to 3 different geographical regions every night.
- D Each row is physically written 3 times to the same hard drive to prevent disk sector failure.
Answer: B. Exactly three distinct copies of every data record are maintained on three different nodes in the cluster.
RF=3 is a production standard for 'High Availability'. If one node (or even two in some configurations) crashes, you still have a healthy copy of the data on the remaining node(s), ensuring both durability and service continuity.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- Unlike a Leader-Follower architecture (like MySQL or Redis), how does Cassandra maintain high availability within its node cluster?
- Cassandra Query Language (CQL) looks similar to SQL. What is a fundamental SQL feature that CQL does NOT support to ensure distributed performance?
- What is the critical architectural function of the 'Partition Key' in a Cassandra table?
- Apache Cassandra is fundamentally designed as which architectural category of NoSQL database?
- An extreme financial trading application requires 'Batch' sync for the Commit Log. What is the fundamental throughput limitation introduced by this setting?
- In a cluster with high 'Mutation' (Write) frequency, why is the `Row Cache` almost universally disabled by experts?