How would you answer an interview scenario involving GraphQL N+1 problem?

In an interview, I would first define GraphQL N+1 problem and the problem it solves, then explain how I would batch and cache related lookups within a request using a DataLoader-style pattern, project only required fields, and inspect resolver-level query counts. I would also call out the main failure mode: adding eager loading everywhere without understanding the requested graph can replace N+1 calls with oversized joins or unnecessary data transfer. Finally, I would describe how I would test, monitor, and safely roll back or recover the solution.