Why databases back GraphQL - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do GraphQL servers often rely on databases?

GraphQL servers need to provide data to clients. Why is it common for GraphQL servers to use databases as their data source?

A Because databases automatically convert GraphQL queries into REST API calls.

B Because GraphQL can only work with SQL databases and no other data sources.

C Because GraphQL servers do not need any data source to respond to queries.

D Because databases store structured data that GraphQL queries can retrieve efficiently.

💡 Hint

Think about where data is usually stored in applications.

GraphQL servers use databases because databases hold the actual data in a structured way. GraphQL queries ask for specific data, and databases can efficiently provide that data.

❓ query_result

intermediate

What data does this GraphQL query return from the database?

Given a GraphQL query requesting user { id, name } and a database table users with columns id, name, and email, what will the query return?

GraphQL

query {
  user {
    id
    name
  }
}

A [{ "id": 1, "name": "Alice", "email": "[e-mail]" }]

B [{ "id": 1, "name": "Alice" }, { "id": 2, "name": "Bob" }]

C [{ "email": "[e-mail]" }]

D []

💡 Hint

The query only asks for id and name, not email.

The GraphQL query requests only the id and name fields. The database returns those fields for each user.

📝 Syntax

advanced

Identify the error in this GraphQL resolver accessing a database

Look at this resolver code snippet that fetches data from a database. What is the syntax error?

GraphQL

const resolvers = {
  Query: {
    user: (parent, args, context) => {
      return context.db.query('SELECT * FROM users WHERE id = $1', args.id)
    }
  }
}

A The function should be async to await the database query.

B The resolver is missing a return statement.

C The query method should use an array for parameters, like [args.id] instead of args.id.

D The context object cannot be used inside resolvers.

💡 Hint

Check how parameters are passed to parameterized queries.

Database query methods usually expect parameters as an array. Passing args.id directly is incorrect syntax.

❓ optimization

advanced

How to optimize GraphQL queries backed by databases to reduce load?

When a GraphQL query requests nested data (e.g., users and their posts), what is a common optimization to reduce database load?

A Use data loader techniques to batch and cache database requests.

B Run separate database queries for each nested field without caching.

C Fetch all data in one big query without filtering.

D Avoid using databases and hardcode data in resolvers.

💡 Hint

Think about how to avoid many repeated database calls.

Data loader batches multiple requests into one and caches results, reducing database load and improving performance.

🔧 Debug

expert

Why does this GraphQL query fail when backed by a database?

This GraphQL query requests a user by ID, but it returns null even though the user exists in the database. What is the likely cause?

GraphQL

query {
  user(id: 5) {
    id
    name
  }
}

A The resolver does not correctly use the argument 'id' to query the database.

B The user ID 5 does not exist in the database.

C GraphQL does not support arguments in queries.

D The database table is empty.

💡 Hint

Check how the resolver uses the query arguments.

If the resolver ignores or misuses the 'id' argument, the database query will not find the user, returning null.

Practice

1. Why do GraphQL APIs usually connect to databases?

easy

A. To speed up the internet connection

B. To make the app's user interface colorful

C. To store and organize the data that apps request

D. To create animations in the app

Solution

1. Step 1: Understand GraphQL's role

   GraphQL lets apps ask for specific data they need.

2. Step 2: Identify why databases are needed

   Databases store and organize data safely for GraphQL to fetch.

3. Final Answer:

   To store and organize the data that apps request -> Option C

4. Quick Check:

   GraphQL needs data storage = To store and organize the data that apps request [OK]

Hint: GraphQL fetches data; databases keep data safe [OK]

Common Mistakes:

• Thinking GraphQL creates UI effects
• Confusing data storage with internet speed
• Assuming GraphQL handles animations

2. Which of the following is the correct way to describe how GraphQL queries data from a database?

easy

A. GraphQL sends a query to the database asking for specific fields

B. GraphQL directly edits the database tables without queries

C. GraphQL stores data inside the app without using a database

D. GraphQL only works with files, not databases

Solution

1. Step 1: Understand GraphQL query behavior

   GraphQL sends queries specifying exactly which data fields it wants.

2. Step 2: Check database interaction

   Databases respond to these queries by returning requested data.

3. Final Answer:

   GraphQL sends a query to the database asking for specific fields -> Option A

4. Quick Check:

   GraphQL queries database fields = GraphQL sends a query to the database asking for specific fields [OK]

Hint: GraphQL queries, doesn't edit database directly [OK]

Common Mistakes:

• Thinking GraphQL edits database tables directly
• Believing GraphQL stores data locally only
• Assuming GraphQL works without databases

3. Given this GraphQL query:
{ user(id: 1) { name, email } }
What does the database return?

medium

A. User with id 1's name and email only

B. All users with their names and emails

C. An error because the query is incomplete

D. User with id 1's password and email

Solution

1. Step 1: Analyze the query fields

   The query asks for user with id 1, requesting only name and email fields.

2. Step 2: Understand database response

   The database returns data matching id 1 with only requested fields: name and email.

3. Final Answer:

   User with id 1's name and email only -> Option A

4. Quick Check:

   Query requests specific user fields = User with id 1's name and email only [OK]

Hint: Query fields limit data returned from database [OK]

Common Mistakes:

• Assuming all users are returned
• Expecting password field without request
• Thinking query is incomplete and errors

4. A developer wrote this GraphQL query:
{ product(id: ) { name price } }
What is the main issue?

medium

A. GraphQL does not support querying products

B. Query will return all products instead of one

C. Fields name and price are invalid

D. Missing value for id causes syntax error

Solution

1. Step 1: Check query syntax

   The id argument is empty, which is invalid syntax in GraphQL.

2. Step 2: Understand error impact

   This causes a syntax error, so the query won't run or return data.

3. Final Answer:

   Missing value for id causes syntax error -> Option D

4. Quick Check:

   Empty argument value = syntax error [OK]

Hint: Always provide values for required arguments [OK]

Common Mistakes:

• Assuming query returns all products
• Thinking fields are invalid
• Believing GraphQL can't query products

5. An app uses GraphQL to fetch user data from a database. The query requests { user(id: 5) { name, posts { title } } }. Why is the database important here?

hard

A. It creates the GraphQL query automatically

B. It stores user and post data so GraphQL can fetch nested info

C. It styles the user interface with data colors

D. It speeds up the app by skipping data storage

Solution

1. Step 1: Understand nested query

   The query asks for user info and their posts' titles, which is nested data.

2. Step 2: Role of database

   The database holds both user and post data, allowing GraphQL to retrieve nested related data.

3. Final Answer:

   It stores user and post data so GraphQL can fetch nested info -> Option B

4. Quick Check:

   Database stores nested data = It stores user and post data so GraphQL can fetch nested info [OK]

Hint: Database holds nested data GraphQL queries [OK]

Common Mistakes:

• Thinking database creates queries
• Confusing data storage with UI styling
• Assuming database skips storing data