Which property of ACID transactions in a data lakehouse prevents a query from reading a partially written table?

Atomicity guarantees that a write transaction either completes entirely and becomes visible; or fails and leaves the table unchanged; preventing dirty reads of partial results. The incorrect options ("Durability — ensuring data is persisted to disk after each row write", "Consistency — ensuring all columns match their declared data types", "Isolation — ensuring concurrent readers always see the latest uncommitted changes") are distractors that don't fully capture the concept described.