When Acceleration for Data Connections is enabled, Tableau Next temporarily caches external-source data in Data 360 to reduce runtime latency and improve query performance. Two refresh approaches are available: Full Refresh and Incremental Refresh. Salesforce explicitly states that an incremental refresh processes records that have been added or changed since the previous refresh but does not update deleted data. Therefore, records removed from the source can remain present in the accelerated cache even after several incremental refresh cycles.

This explains why the 15-minute frequency does not solve the issue. Frequency controls how often incremental processing occurs; it does not change what the incremental algorithm processes. Option A incorrectly attributes the behavior to ordinary cache latency. Option C is also too broad because acceleration itself supports deletion synchronization when a Full Refresh is used. A full refresh removes the existing cached dataset and replaces it with the current source dataset.

Reference/Topics: Data Setup -> Data Connections -> Acceleration -> Full versus Incremental Refresh -> Cache Refresh Method.

===========================================================================