Public works must schedule OPTIMIZE and VACUUM without colliding with peak hydrant-inspection ingest. What planning approach fits?

Public works must schedule OPTIMIZE and VACUUM without colliding with peak hydrant-inspection ingest, so the fitting approach is to schedule those Delta maintenance windows outside peak ingest hours. OPTIMIZE and VACUUM compete for cluster and storage I/O; running them during heavy hydrant-inspection landings lengthens ingest and maintenance alike and risks SLA misses for civic field operations. Scheduling OPTIMIZE and VACUUM in a concurrent window outside hydrant-inspection ingest peaks fails because it forces the two maintenance jobs to compete for cluster and storage I/O with each other, lengthening both and complicating monitoring and retries, so they need separate off-peak windows. Scheduling OPTIMIZE and VACUUM with 24-hour retention outside hydrant-inspection ingest peaks fails because VACUUM with only 24-hour retention can delete data files still needed by concurrent readers and time travel and risks data loss, violating the 7-day default safeguard even when timed off-peak. Scheduling OPTIMIZE and VACUUM on checkpoint files outside hydrant-inspection ingest peaks fails because OPTIMIZE and VACUUM must target Delta tables, not Structured Streaming checkpoint files, and cleaning checkpoints corrupts recovery state even when timed off-peak. Exam caveat: DP-750 Delta maintenance planning emphasizes off-peak windows that avoid ingest collision. Operational check: chart hydrant-inspection ingest peak hours, schedule OPTIMIZE and VACUUM in the trough, monitor job duration overlap, and adjust the window if ingest and maintenance still contend.