GraphQL is considered when REST cannot meet needs. Which statement aligns with this guideline?

GraphQL is considered when REST cannot meet needs. Which statement aligns with this guideline?

• A. GraphQL should replace REST in all situations.
• B. REST is never suitable for internal services.
• C. Use GraphQL when REST cannot meet complex query needs.
• D. GraphQL is ideal for static content delivery.

Answer: (C)

The idea being tested is that GraphQL is a good fit when REST falls short on complex data needs. GraphQL lets clients ask for exactly the data they want, including nested or related resources, in a single request. This flexibility is powerful when different clients require different data shapes, when you need to combine data from multiple sources, or when you want to avoid over-fetching and under-fetching that can happen with fixed REST endpoints. In practice, use GraphQL when the variety and complexity of client queries make a traditional REST surface inefficient or brittle. GraphQL isn’t a universal replacement for REST. For simple, stable endpoints with straightforward data access, REST can be simpler and easier to cache and scale. It’s also not ideal for static content delivery, where content can be served efficiently from a cache or CDN without the overhead of a GraphQL schema and resolvers. The best guidance is to choose GraphQL when the needs involve flexible, complex queries across related data, otherwise REST or other approaches may be more appropriate.

The idea being tested is that GraphQL is a good fit when REST falls short on complex data needs. GraphQL lets clients ask for exactly the data they want, including nested or related resources, in a single request. This flexibility is powerful when different clients require different data shapes, when you need to combine data from multiple sources, or when you want to avoid over-fetching and under-fetching that can happen with fixed REST endpoints. In practice, use GraphQL when the variety and complexity of client queries make a traditional REST surface inefficient or brittle.

GraphQL isn’t a universal replacement for REST. For simple, stable endpoints with straightforward data access, REST can be simpler and easier to cache and scale. It’s also not ideal for static content delivery, where content can be served efficiently from a cache or CDN without the overhead of a GraphQL schema and resolvers. The best guidance is to choose GraphQL when the needs involve flexible, complex queries across related data, otherwise REST or other approaches may be more appropriate.