Why error handling differs from REST in GraphQL - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does GraphQL error handling differ from REST?

In REST APIs, errors are usually indicated by HTTP status codes. How does GraphQL handle errors differently?

A GraphQL returns errors only in HTTP headers, not in the response body.

B GraphQL uses HTTP status codes like 404 or 500 to indicate errors, similar to REST.

C GraphQL always returns HTTP 200 status and includes errors inside the response body under an 'errors' field.

D GraphQL does not provide any error information in the response.

💡 Hint

Think about how GraphQL separates transport status from query execution results.

GraphQL typically returns HTTP 200 status even if there are errors in the query. The errors are included inside the response body under an 'errors' field. This differs from REST where HTTP status codes indicate success or failure.

❓ query_result

intermediate

Identify the GraphQL error response structure

Given a GraphQL query that requests a user by ID but the user does not exist, which response shows the correct error handling?

GraphQL

{ user(id: "123") { name email } }

A { "data": { "user": null }, "errors": [{ "message": "User not found", "path": ["user"] }] }

B { "error": "User not found", "status": 404 }

C { "data": null, "status": 404 }

D { "data": { "user": { "name": "", "email": "" } } }

💡 Hint

Look for the 'errors' field inside the response body.

GraphQL responses include an 'errors' array alongside 'data'. Even if the user is not found, the HTTP status is 200, and the error details are inside the 'errors' field.

📝 Syntax

advanced

Which GraphQL error response is syntactically valid?

Select the syntactically valid GraphQL error response JSON for a failed query.

A { "data": null, "errors": [{ "message": "Invalid query" }] }

B { data: null, errors: [{ message: "Invalid query" }] }

C { "data": null, "errors": { "message": "Invalid query" } }

D { "data": null, "errors": [{ message: "Invalid query" }] }

💡 Hint

Remember JSON requires double quotes around keys and string values.

Option A is valid JSON with double quotes around keys and string values. Options A and D lack quotes around keys, and C uses an object instead of an array for 'errors'.

❓ optimization

advanced

Optimizing error handling in GraphQL responses

Which approach best optimizes error handling in GraphQL to avoid sending unnecessary data when a critical error occurs?

A Always return full data even if errors occur to keep response size consistent.

B Return null for 'data' and include detailed error messages in the 'errors' array.

C Return partial data with errors and let the client handle missing fields.

D Use HTTP status codes to indicate errors and omit the 'errors' field.

💡 Hint

Consider how to clearly communicate critical failures without confusing partial data.

Returning null for 'data' with detailed errors clearly signals a critical failure. Partial data with errors can confuse clients, and HTTP status codes are not reliable for GraphQL errors.

🔧 Debug

expert

Why does this GraphQL client fail to detect errors?

A client sends a GraphQL query and checks HTTP status code to detect errors. It ignores the response body. Why might this approach fail?

A Because the client must parse XML responses to find errors.

B Because the client should check HTTP headers for error details instead.

C Because GraphQL never returns errors in the response body, only status codes.

D Because GraphQL returns HTTP 200 status even when there are errors inside the response body.

💡 Hint

Think about how GraphQL separates transport success from query success.

GraphQL uses HTTP 200 status for all responses, including those with errors. Errors are inside the response body, so checking only HTTP status misses them.

Practice

1. In GraphQL, how are errors handled differently compared to REST APIs?

easy

A. GraphQL returns data and errors together in one response.

B. GraphQL stops execution and returns only errors without data.

C. GraphQL returns errors as HTTP status codes only.

D. GraphQL does not provide any error details to the client.

Solution

1. Step 1: Understand REST error handling

   REST APIs usually return errors as HTTP status codes and no data when an error occurs.

2. Step 2: Understand GraphQL error handling

   GraphQL returns both data and errors together in one response, allowing partial data delivery.

3. Final Answer:

   GraphQL returns data and errors together in one response. -> Option A

4. Quick Check:

   GraphQL response = data + errors [OK]

Hint: Remember GraphQL sends data and errors together [OK]

Common Mistakes:

• Thinking GraphQL only returns errors without data
• Confusing HTTP status codes with GraphQL error handling
• Assuming GraphQL hides error details

2. Which part of a GraphQL response contains error details?

easy

A. The data field

B. The HTTP status code

C. The errors field

D. The extensions field only

Solution

1. Step 1: Identify error location in GraphQL response

   GraphQL responses include an errors field that lists error messages and details.

2. Step 2: Differentiate from other fields

   The data field contains the requested data, HTTP status codes are not used for errors, and extensions may have extra info but not main errors.

3. Final Answer:

   The errors field -> Option C

4. Quick Check:

   Error details = errors field [OK]

Hint: Errors are always in the 'errors' field [OK]

Common Mistakes:

• Looking for errors in the data field
• Relying on HTTP status codes for errors
• Confusing extensions with errors

3. Given this GraphQL response:

{"data": {"user": null}, "errors": [{"message": "User not found", "path": ["user"]}]}

What does this response mean?

medium

A. The user exists but has no data.

B. The query failed completely and no data is returned.

C. The server returned a syntax error in the query.

D. Partial data is returned; user field is null due to an error.

Solution

1. Step 1: Analyze the data field

   The data field shows "user": null, meaning no user data was returned.

2. Step 2: Analyze the errors field

   The errors field shows "User not found" with path ["user"], indicating an error related to the user field.

3. Final Answer:

   Partial data is returned; user field is null due to an error. -> Option D

4. Quick Check:

   Partial data + error path = null field [OK]

Hint: Null data with errors means partial failure [OK]

Common Mistakes:

• Assuming no data means full failure
• Ignoring the errors field
• Thinking user exists without data

4. You receive this GraphQL response:

{"data": {"post": {"title": "Hello World"}}, "errors": [{"message": "Author not found", "path": ["post", "author"]}]}

What is the likely issue?

medium

A. The post data is returned but author field caused an error.

B. The server returned no data at all.

C. The entire query failed due to syntax error.

D. The author field is missing from the query.

Solution

1. Step 1: Check the data field

   The data field contains post with a title, so some data is returned.

2. Step 2: Check the errors field

   The error message "Author not found" with path ["post", "author"] shows the error is specific to the author field inside post.

3. Final Answer:

   The post data is returned but author field caused an error. -> Option A

4. Quick Check:

   Data present + error path = partial error [OK]

Hint: Error path shows which field failed [OK]

Common Mistakes:

• Assuming full query failure
• Ignoring error path details
• Thinking missing field means query error

5. Why does GraphQL include the error path in its error messages?

hard

A. To replace HTTP status codes for error classification.

B. To indicate the exact field causing the error for better client handling.

C. To hide sensitive server information from clients.

D. To provide a list of all fields in the query.

Solution

1. Step 1: Understand the purpose of error path

   The path shows the exact location in the query where the error happened.

2. Step 2: Understand client benefit

   This helps clients know which part of the data failed and handle partial data properly.

3. Final Answer:

   To indicate the exact field causing the error for better client handling. -> Option B

4. Quick Check:

   Error path = pinpoint error location [OK]

Hint: Error path points to problem field [OK]

Common Mistakes:

• Thinking path replaces HTTP status codes
• Assuming path hides server info
• Confusing path with full query fields