Delete+insert removes stored rows whose keys occur in the incoming batch, then inserts that batch. The key and source grain matter just as they do for merge.
An overlapping correction window can reread unchanged orders safely because each incoming key replaces its earlier row. Older keys outside that window stay in the table.
A full refresh has a different scope: it rebuilds the relation from the complete model query. Use it when an approved repair or definition change must reach historical rows outside the normal window. Updating the SQL alone doesn't recompute those rows.
Replacement also leaves keys absent from its incoming SELECT in place, so a source deletion or a new exclusion rule needs a separate removal plan. The exercises run against existing tables to make that distinction visible in stored amounts, currency codes, and record counts.