How would you answer an interview scenario involving REST API design?

In an interview, I would first define REST API design and the problem it solves, then explain how I would use resource-oriented routes, correct HTTP methods, meaningful status codes, stable contracts, validation, pagination for collections, and documented error responses. I would also call out the main failure mode: designing action-heavy endpoints such as /GetCustomer or returning inconsistent payloads for similar outcomes makes clients tightly coupled and harder to maintain. Finally, I would describe how I would test, monitor, and safely roll back or recover the solution.