How would you answer an interview scenario involving RESTful resource design in Web API?

I would model the API around resources rather than controller actions. For example, GET /customers/{id}, GET /customers/{id}/orders, POST /orders, and PATCH /orders/{id} use HTTP methods to express the operation. I would define clear request and response DTOs, standard status codes, validation behavior, pagination for collections, consistent error contracts, and idempotency where retries may occur.