Bird
0
0

Why is over-fetching considered inefficient in GraphQL compared to REST APIs?

hard📝 Conceptual Q10 of 15
GraphQL - Basics and Philosophy
Why is over-fetching considered inefficient in GraphQL compared to REST APIs?
ABecause GraphQL allows clients to specify exactly what data they want, so extra data is avoidable
BBecause GraphQL always fetches all data regardless of query
CBecause REST APIs never over-fetch data
DBecause GraphQL queries are slower than REST requests
Step-by-Step Solution
Solution:

  1. Step 1: Understand GraphQL flexibility

    GraphQL lets clients specify exactly which fields they want.

  2. Step 2: Compare with over-fetching impact

    Over-fetching is inefficient because it requests more data than needed, which GraphQL can avoid.

  3. Final Answer:

    Because GraphQL allows clients to specify exactly what data they want, so extra data is avoidable -> Option A

  4. Quick Check:

    GraphQL precise queries reduce over-fetching [OK]
Quick Trick: GraphQL avoids over-fetching by letting clients choose fields [OK]
Common Mistakes:
  • Thinking GraphQL always fetches all data
  • Believing REST APIs never over-fetch
  • Confusing query speed with data amount

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More GraphQL Quizzes
GraphQL Basics and Philosophy - Single endpoint architecture - Quiz 4medium GraphQL Basics and Philosophy - GraphQL vs REST comparison - Quiz 15hard Mutations - Mutation syntax - Quiz 14medium Queries - Nested field queries - Quiz 15hard Resolvers - Context argument - Quiz 12easy Resolvers - Parent (root) argument - Quiz 12easy Schema Definition Language (SDL) - List types - Quiz 2easy Schema Definition Language (SDL) - Object types - Quiz 15hard Schema Definition Language (SDL) - Type definitions - Quiz 10hard Type Relationships - Bidirectional relationships - Quiz 14medium