a read request immediately after a write operation might not show the latest change.
a read request immediately after a write operation shows the latest change.
a write request immediately after a read operation might cause data loss.
a read request immediately after a write operation might cause data loss.
Explanations:
“Eventually consistent” means that after a write operation, there may be a delay before all reads return the latest value. Therefore, a read immediately following a write may not show the most recent change.
This option contradicts the definition of eventual consistency, which states that immediate reads after writes do not guarantee the latest data is visible.
While concurrent write requests can lead to issues, the statement about data loss is misleading. Eventual consistency does not imply that a write request after a read causes data loss; rather, it may just not reflect the most current data.
This option suggests that a read immediately after a write could cause data loss, which is incorrect. Eventual consistency does not mean data loss; it means the data may not be up-to-date after a write until the system converges.