How do you use a spike to de-risk a story?

This tests your ability to use agile spikes for targeted de-risking, not just vague research. A great answer defines the specific question the spike will answer (e.g., 'Can API X handle 500 RPS?'), proposes a strict time-box, and lists concrete deliverables. These deliverables are knowledge—a decision, a throwaway prototype, or a refined estimate for the actual feature story—not production code. A red flag is treating a spike as a mini-feature or a ticket for 'just figuring it out' without a clear goal or deliverable.