How would you answer an interview scenario involving error boundaries and resilient UI in React?

For an interview scenario involving error boundaries and resilient UI, I would first clarify the business goal, scale, constraints, and the failure or quality attribute the interviewer wants to explore. Error boundaries catch rendering errors in descendant React trees and render a fallback UI instead of allowing the entire application surface to fail. In this scenario, if one analytics widget can fail because of third-party data, wrap that widget area in an error boundary so the rest of the dashboard remains usable. For production, place boundaries around important route or feature areas, log useful diagnostics, provide a retry or navigation option, and still handle API and event errors explicitly. I would then explain the main alternatives and tradeoffs, identify likely failure modes, and describe how I would validate the solution through testing, observability, security controls, and recovery or rollback planning.