Parks venue names change overnight and a full SFT cycle will not finish before morning events. What should staff apply?
Select an answer to reveal the explanation.
Short Explanation
Venue renamed at midnight? Slap on a tiny PEFT patch—like correcting a flyer with a sticker—instead of reprinting the whole parks encyclopedia before sunrise.
Full Explanation
When parks venue names change overnight and a full SFT cycle will not finish before morning events, staff should apply a tiny PEFT patch that updates venue names without full supervised fine-tuning. A small adapter (or soft-prompt patch) can absorb rename pairs quickly, ship under change control, and leave the broader events model intact—like correcting a flyer with a sticker instead of reprinting the parks encyclopedia before sunrise.
A from-scratch pretrain on the entire parks archive fails by concept and schedule: pretraining cannot finish overnight and is wildly disproportionate to a rename. Deletion of the events model until the next budget year fails residents who need tonight’s venue guidance. Manual SMS to every resident with no model update path fails as an unscalable one-off that leaves the model stale for every subsequent channel (web, IVR, chat).
Exam caveat: PEFT rename patches still need a quick validation list of old→new venue strings so you do not partially update aliases. Operational check: train the micro-adapter on rename pairs, score a fixed venue-name probe before morning doors, confirm old names no longer win, and keep the patch detachable if a rename was entered wrong.