intermediateREST API Design118 of 469
How would you prevent an API response from accidentally exposing fields added to an entity later?
Tests whether you default to explicit DTOs/response projections instead of serializing entities directly, since a new entity field otherwise gets exposed automatically the moment someone adds it, with no compile-time warning.
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a response