A coding agent can modify infrastructure, app code, and data access layers in one task. How do you constrain it?

Instruction: Explain how you would limit scope when the task spans several high-blast-radius layers.

Context: Tests how the candidate diagnoses the problem, chooses the safest next step, and reasons through recovery. Explain how you would limit scope when the task spans several high-blast-radius layers.

Official answer available

Preview the opening of the answer, then unlock the full walkthrough.

I would constrain by layer and by task. If a request spans infrastructure, app code, and data access, that is usually too much authority and too much scope for one unbounded autonomous pass.

I would require explicit planning, separate review gates by...

Upgrade to view official answer

Related Questions