A parks booking service needs a small, precise change in one handler with unique surrounding text. Which built-in fits?
Select an answer to reveal the explanation.
Short Explanation
Unique string in a single parks handler? Edit is the precision screwdriver—tiny twist, no teardown of the whole shed.
Full Explanation
For a small, precise change in one handler when surrounding text is unique, Edit is the appropriate built-in. A parks booking service tweak—validation message, status transition, or fee flag—should use Edit keyed to unique anchors rather than broad rewrites.
Why the correct option works: Edit applies targeted modifications when unique text matches identify the change site. That minimizes diff size, review risk, and chance of disturbing unrelated booking paths. Unique anchors make the operation reliable and fast.
Why the other three fail by concept: Glob rewriting binary assets unrelated to the handler is the wrong tool and wrong target. Grep exclusively never applies a modification—search alone does not ship the fix. Bash overwriting the entire repository from a distant backup is grossly disproportionate and dangerous for a one-handler change.
Exam caveat: if anchors are not unique, fall back to Read+Write (as in related items); uniqueness is the precondition that makes Edit best. Operational check: confirm a unique anchor string in the parks handler, apply Edit, run the focused test or Grep for regressions, and keep the diff limited to that handler. Parks booking handlers sit on revenue and reservation correctness paths, so minimizing blast radius matters: Edit with unique anchors produces a reviewable one-site diff. If uniqueness is doubtful, stop and switch to Read then Write rather than forcing a risky multi-match Edit.