Why mutations modify data in GraphQL - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Mutations in GraphQL

Why do mutations exist in GraphQL?

A To modify or create data on the server

B To only fetch data without changes

C To define the schema structure

D To handle client-side caching

💡 Hint

Think about what changes data on the server.

Mutations are designed to change data on the server, such as creating, updating, or deleting records. Queries only fetch data without modifying it.

❓ query_result

intermediate

Mutation Result Output

Given this mutation:

mutation { addBook(title: "New Book", author: "Jane") { id title author } }

What is the expected output if the mutation succeeds?

A {"error":"Cannot fetch data"}

B {"data":{"addBook":null}}

C {"data":{"addBook":{"id":"123","title":"New Book","author":"Jane"}}}

D {"data":{"books":[{"title":"New Book"}]}}

💡 Hint

Mutations return the changed data as specified in the selection set.

When a mutation succeeds, it returns the fields requested inside the mutation's selection set. Here, it returns the new book's id, title, and author.

📝 Syntax

advanced

Identify the Syntax Error in Mutation

Which option contains a syntax error in this mutation?

mutation { updateUser(id: "1", name: "Alice") { id name } }

A mutation { updateUser(id: "1", name: "Alice") { id, name } }

B mutation { updateUser(id: 1, name: "Alice") { id name } }

C mutation { updateUser(id: "1", name: "Alice") { id name } }

D mutation { updateUser(id: "1" name: "Alice") { id name } }

💡 Hint

Look for missing punctuation between arguments.

Option D is missing a comma between arguments, causing a syntax error. All other options are syntactically valid.

❓ optimization

advanced

Optimizing Mutation Response Size

You want to reduce the data returned by a mutation to improve performance. Which mutation selection set is best?

A mutation { deletePost(id: "5") { id content } }

B mutation { deletePost(id: "5") { id } }

C mutation { deletePost(id: "5") { id title } }

D mutation { deletePost(id: "5") { id title content author { id name } } }

💡 Hint

Only request the fields you need.

Requesting only the id field returns the smallest response, reducing data transfer and improving performance.

🔧 Debug

expert

Why Does This Mutation Not Modify Data?

A mutation is sent:

mutation { updateEmail(id: "10", email: "[e-mail]") { id email } }

But the email does not change in the database. What is the most likely reason?

A The mutation resolver does not update the database correctly

B The mutation name is invalid and causes a syntax error

C The query is missing a selection set

D The client did not send the mutation request

💡 Hint

Check the server-side code that handles the mutation.

If the mutation runs without error but data does not change, the resolver likely does not perform the update operation properly.

Practice

1. What is the main purpose of a mutation in GraphQL?

easy

A. To modify data by adding, updating, or deleting it

B. To only fetch data without changes

C. To define the schema structure

D. To create a new query type

Solution

1. Step 1: Understand the role of mutations

   Mutations are designed to change data, unlike queries which only fetch data.

2. Step 2: Identify the correct purpose

   Since mutations add, update, or delete data, their main purpose is to modify data.

3. Final Answer:

   To modify data by adding, updating, or deleting it -> Option A

4. Quick Check:

   Mutation = Modify data [OK]

Hint: Mutations always change data, queries only read data [OK]

Common Mistakes:

• Confusing mutations with queries
• Thinking mutations only fetch data
• Believing mutations define schema only

2. Which of the following is the correct way to start a mutation operation in GraphQL?

easy

A. modify { updateUser(id: 1) { name } }

B. query { updateUser(id: 1) { name } }

C. update { updateUser(id: 1) { name } }

D. mutation { updateUser(id: 1) { name } }

Solution

1. Step 1: Identify the keyword for mutations

   GraphQL uses the keyword mutation to start mutation operations.

2. Step 2: Check the options

   Only mutation { updateUser(id: 1) { name } } uses the correct mutation keyword to start the operation.

3. Final Answer:

   mutation { updateUser(id: 1) { name } } -> Option D

4. Quick Check:

   Mutation keyword = mutation [OK]

Hint: Mutations always start with the 'mutation' keyword [OK]

Common Mistakes:

• Using 'query' instead of 'mutation'
• Using non-existent keywords like 'update' or 'modify'
• Omitting the mutation keyword

3. Given the mutation below, what will be the result if the user with id 2 exists?

mutation {
  updateUser(id: 2, input: {name: "Alice"}) {
    id
    name
  }
}

medium

A. Syntax error due to missing input type

B. { "data": { "updateUser": null } }

C. { "data": { "updateUser": { "id": 2, "name": "Alice" } } }

D. No change, returns old user data

Solution

1. Step 1: Understand mutation behavior

   The mutation updates user with id 2, changing the name to "Alice".

2. Step 2: Predict the returned data

   The mutation returns the updated user data with id and new name.

3. Final Answer:

   { "data": { "updateUser": { "id": 2, "name": "Alice" } } } -> Option C

4. Quick Check:

   Mutation updates and returns new data [OK]

Hint: Mutations return updated data if successful [OK]

Common Mistakes:

• Assuming mutation returns null on success
• Thinking mutation causes syntax error here
• Believing mutation returns old data without changes

4. Identify the error in this mutation:

mutation {
  addUser(name: "Bob")
  {
    id
    name
  }
}

medium

A. Mutation keyword is incorrect

B. Missing input argument object for addUser

C. Curly braces are misplaced

D. No error, mutation is correct

Solution

1. Step 1: Check mutation input format

   Mutations usually require input as an object, e.g., addUser(input: {name: "Bob"}).

2. Step 2: Identify missing input argument

   The mutation lacks the input argument object, causing an error.

3. Final Answer:

   Missing input argument object for addUser -> Option B

4. Quick Check:

   Input argument missing = error [OK]

Hint: Mutations need input objects for data changes [OK]

Common Mistakes:

• Forgetting to wrap inputs in an object
• Misplacing curly braces
• Confusing mutation keyword

5. You want to delete a user and then immediately fetch the updated user list in one mutation operation. Which approach correctly uses mutations to achieve this?

hard

A. Use a single mutation with two fields: deleteUser and users to delete and fetch updated list

B. Use a query to delete the user and a mutation to fetch the list

C. Use two separate mutations, one for deleting and one for fetching users

D. Use a mutation to delete the user and a query to fetch the updated list separately

Solution

1. Step 1: Understand mutation capabilities

   GraphQL mutations can include multiple fields to perform several operations in one request.

2. Step 2: Identify correct approach

   Using a single mutation with deleteUser and users fields allows deleting and fetching updated data atomically.

3. Final Answer:

   Use a single mutation with two fields: deleteUser and users to delete and fetch updated list -> Option A

4. Quick Check:

   Single mutation can do multiple related operations [OK]

Hint: Combine delete and fetch in one mutation for atomic update [OK]

Common Mistakes:

• Trying to delete with a query
• Splitting operations into separate requests unnecessarily
• Using mutation only for delete without fetching updated data