200-901 Software Development and Design Practice Question
Which THREE of the following are characteristics of GraphQL compared to REST? (Choose three.)
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Typically uses a single endpoint.
Option A is correct because GraphQL exposes a single endpoint (commonly /graphql) through which all queries and mutations are sent, unlike REST's resource-specific URLs. Option B is correct because GraphQL APIs are defined by a strongly typed schema using the Schema Definition Language, specifying types, fields, and operations that enable validation and introspection. Option C is correct because GraphQL clients send queries declaring precisely the fields they need, so the server returns exactly that shape of data. Option D is not a GraphQL characteristic; over-fetching is a well-known REST problem that GraphQL is designed to avoid. Option E describes REST, where distinct endpoints map to different resources, whereas GraphQL uses one endpoint.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Typically uses a single endpoint.
Why this is correct
GraphQL exposes one URL, usually `/graphql`, over which clients POST queries, mutations and subscriptions. This satisfies the stem's comparison with REST, where each resource maps to its own endpoint. A single endpoint lets clients request exactly the fields they need, avoiding REST's multiple round trips and over-fetching.
- ✓
Strongly typed schema.
Why this is correct
GraphQL APIs are defined by a strongly typed schema specifying types, fields and their nullability, enabling validation and introspection. REST has no equivalent enforced contract, relying instead on documentation, so this typing is a distinguishing characteristic.
- ✓
Client specifies exactly what data it needs.
Why this is correct
GraphQL exposes a single endpoint where the client's query document declares the precise fields and nested relationships required, so the server returns only those. REST instead returns fixed resource representations, causing over-fetching or under-fetching. This client-driven selection satisfies the stem's comparison characteristic.
- ✗
Over-fetching of data is common.
Why it's wrong here
Over-fetching is a REST weakness that GraphQL resolves: clients declare exactly the fields they need in a single query, so surplus data is not returned. It is tempting because REST endpoints commonly return fixed payloads, but that is the problem GraphQL was designed to eliminate.
- ✗
Multiple endpoints for different resources.
Why it's wrong here
Multiple endpoints per resource is REST's model, where each URI exposes one resource; GraphQL exposes a single endpoint that resolves many resources through one schema. It is tempting because REST APIs are commonly organised this way, but the question asks for GraphQL characteristics.
Go deeper
Related to this question
About these practice questions
This 200-901 question is part of Courseiva's 975-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 200-901 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-901 exam.