Query depth and complexity in GraphQL - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ query_result

intermediate

What is the output of this GraphQL query?

Given the following GraphQL schema snippet:

type Author { id: ID! name: String! books: [Book!]! } type Book { id: ID! title: String! pages: Int! }

And this query:

{ author(id: "1") { name books { title pages } } }

Assuming the author with id "1" has two books: "GraphQL Basics" (100 pages) and "Advanced GraphQL" (250 pages), what will the query return?

A {"data":{"author":{"name":"Author One","books":[{"title":"GraphQL Basics","pages":100},{"title":"Advanced GraphQL","pages":250}]}}}

B {"data":{"author":{"name":"Author One","books":[{"title":"GraphQL Basics"},{"title":"Advanced GraphQL"}]}}}

C {"errors":[{"message":"Field 'pages' not found on type 'Book'"}]}

D {"data":{"author":{"name":"Author One"}}}

💡 Hint

Think about what fields are requested inside the books field.

The query requests name of the author and for each book, both title and pages. So the response includes all these fields.

🧠 Conceptual

intermediate

Which factor primarily affects GraphQL query complexity?

When designing a GraphQL API, what is the main factor that increases the complexity of a query?

A The number of fields requested and their nesting depth

B The size of the database schema

C The number of mutations in the query

D The number of clients connected simultaneously

💡 Hint

Think about what makes a query take longer to process.

Query complexity depends mainly on how many fields are requested and how deeply nested they are, because each field may require separate data fetching.

📝 Syntax

advanced

Identify the syntax error in this GraphQL query

Find the syntax error in the following GraphQL query:

{ user(id: "2") { name email posts { title content } }

A Missing quotes around the id value

B Using colon instead of equal sign in the argument

C Missing closing curly brace at the end of the query

D Using parentheses instead of braces for the posts field

💡 Hint

Check if all braces are properly closed.

The query is missing the final closing curly brace '}' which is required to close the root selection set.

❓ optimization

advanced

How to reduce GraphQL query complexity effectively?

You have a GraphQL query that fetches deeply nested data causing performance issues. Which approach best reduces query complexity?

A Increase the number of fields requested to get all data at once

B Limit the maximum depth of queries allowed by the server

C Remove all arguments from the query to simplify it

D Use multiple nested fragments to organize the query

💡 Hint

Think about server-side controls to prevent expensive queries.

Limiting query depth on the server prevents clients from requesting too deeply nested data, which reduces complexity and improves performance.

🔧 Debug

expert

Why does this GraphQL query cause a complexity error?

Given this query:

{ library { shelves { books { author { name } } } } }

The server returns an error about query complexity being too high. What is the most likely reason?

A The server does not support nested queries

B The query is missing required arguments for shelves

C The author field does not exist on books type

D The query requests multiple nested levels causing exponential data fetching

💡 Hint

Consider how nested fields multiply the amount of data fetched.

Each nested level increases the amount of data fetched. Deep nesting like shelves → books → author causes high complexity, triggering server limits.

Practice

1. What does query depth in GraphQL control?

easy

A. The maximum number of nested levels in a query

B. The total number of fields requested in a query

C. The size of the response data in bytes

D. The number of queries a client can send per minute

Solution

1. Step 1: Understand query depth meaning

   Query depth limits how many nested levels a GraphQL query can have to avoid very deep queries.

2. Step 2: Compare with other options

   Options A, C, and D describe different concepts like total fields, response size, or rate limiting, not depth.

3. Final Answer:

   The maximum number of nested levels in a query -> Option A

4. Quick Check:

   Query depth = nested levels limit [OK]

Hint: Depth means nested levels, not total fields or size [OK]

Common Mistakes:

• Confusing depth with total number of fields
• Thinking depth limits response size
• Mixing depth with request rate limits

2. Which of the following is a correct way to limit query depth in a GraphQL server?

easy

A. Disable introspection queries

B. Set a maximum response size in bytes in the schema definition

C. Limit the number of clients connected to the server

D. Use a middleware that counts nested fields and rejects queries exceeding a limit

Solution

1. Step 1: Identify how to limit query depth

   Limiting query depth is done by counting nested fields during query parsing and rejecting if too deep.

2. Step 2: Evaluate other options

   Options A, B, and C do not directly limit query depth; they affect response size, connections, or introspection.

3. Final Answer:

   Use a middleware that counts nested fields and rejects queries exceeding a limit -> Option D

4. Quick Check:

   Middleware counts depth to limit queries [OK]

Hint: Count nested fields in middleware to limit depth [OK]

Common Mistakes:

• Confusing depth limit with response size limit
• Thinking client count limits query depth
• Believing disabling introspection limits depth

3. Given this GraphQL query:

{ user { posts { comments { text } } } }

If the server limits query depth to 2, what will happen?

medium

A. The query will fail because depth is 4

B. The query will succeed and return all nested data

C. The query will return only user and posts fields

D. The query will return only user field

Solution

1. Step 1: Calculate query depth

   The query has nesting: user (level 1) -> posts (level 2) -> comments (level 3) -> text (level 4). Depth is 4.

2. Step 2: Compare with server limit

   The server limits depth to 2, but query depth is 4, so it will be rejected.

3. Final Answer:

   The query will fail because depth is 4 -> Option A

4. Quick Check:

   Query depth 4 > limit 2, so fail [OK]

Hint: Count nested braces to find depth, compare to limit [OK]

Common Mistakes:

• Counting fields instead of nesting levels
• Assuming partial data returns on depth limit
• Ignoring that depth includes all nested levels

4. You wrote a GraphQL query that exceeds the server's complexity limit and gets rejected. What is a good way to fix it?

medium

A. Add more clients to distribute the load

B. Increase the server's memory to handle complex queries

C. Reduce the number of fields requested or simplify nested queries

D. Disable query complexity checks in the server

Solution

1. Step 1: Understand query complexity

   Query complexity measures how much work the server does; reducing fields or nesting lowers complexity.

2. Step 2: Evaluate fixes

   Increasing memory or clients doesn't reduce complexity; disabling checks risks server overload.

3. Final Answer:

   Reduce the number of fields requested or simplify nested queries -> Option C

4. Quick Check:

   Lower fields/nesting to reduce complexity [OK]

Hint: Simplify query fields and nesting to lower complexity [OK]

Common Mistakes:

• Thinking hardware upgrades fix complexity limits
• Ignoring complexity and disabling checks
• Confusing client count with query complexity

5. You want to protect your GraphQL server from expensive queries. Which combined approach best balances performance and flexibility?

hard

A. Disable all limits and rely on server scaling

B. Set a query depth limit, enforce query complexity cost, and cache frequent query results

C. Only limit query depth and ignore complexity cost

D. Allow unlimited queries but limit response size

Solution

1. Step 1: Understand protection methods

   Query depth limits nesting; complexity cost limits work done; caching speeds repeated queries.

2. Step 2: Evaluate combined approach

   Using all three balances server load and user flexibility well; other options are incomplete or risky.

3. Final Answer:

   Set a query depth limit, enforce query complexity cost, and cache frequent query results -> Option B

4. Quick Check:

   Combine depth, complexity, and caching for best protection [OK]

Hint: Use depth + complexity limits plus caching for best results [OK]

Common Mistakes:

• Relying on only one limit type
• Disabling limits and trusting scaling
• Limiting response size instead of query cost