Question : . In Cassandra insertions or updates of two or more rows in the same partition are treated as one write operation. 1. True 2. False
Correct Answer : Get Lastest Questions and Answer : Explanation: In Cassandra, a write operation is atomic at the partition level, meaning the insertions or updates of two or more rows in the same partition are treated as one write operation. A delete operation is also atomic at the partition level.
Question : If you are using write consistency level of QUORUM with a replication factor of 1. Cassandra will replicate the write to all nodes in the cluster and wait for acknowledgement from two nodes.
2. Cassandra will replicate the write to all nodes in the cluster and wait for acknowledgement from one of the nodes.
4. Cassandra will replicate the write to all nodes in the cluster and does not wait for acknowledgement from two nodes.
Correct Answer : Get Lastest Questions and Answer : Explanation: In Cassandra, a write operation is atomic at the partition level, meaning the insertions or updates of two or more rows in the same partition are treated as one write operation. A delete operation is also atomic at the partition level.
For example, if using a write consistency level of QUORUM with a replication factor of 3, Cassandra will replicate the write to all nodes in the cluster and wait for acknowledgement from two nodes. If the write fails on one of the nodes but succeeds on the other, Cassandra reports a failure to replicate the write on that node. However, the replicated write that succeeds on the other node is not automatically rolled back.
Question : Which of the following is true ? 1. Cassandra uses client-side timestamps to determine the most recent update to a column.
2. Cassandra uses server-side timestamps to determine the most recent update to a column.
4. Cassandra uses user provided timestamps to determine the most recent update to a column.
Correct Answer : Get Lastest Questions and Answer : Explanation: Cassandra uses client-side timestamps to determine the most recent update to a column. The latest timestamp always wins when requesting data, so if multiple client sessions update the same columns in a row concurrently, the most recent update is the one seen by readers.