Create mutation pattern in GraphQL - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a GraphQL mutation named addUser.

GraphQL

type Mutation {
  addUser(name: String!): [1]
}

Drag options to blanks, or click blank then click option'

AString

BQuery

CUser

DBoolean

Attempts:

3 left

💡 Hint

Common Mistakes

Returning Query instead of the object type.

Returning String or Boolean which are not the user type.

The mutation should return the User type after adding a user.

2fill in blank

medium

Complete the mutation argument to require an email of type String.

GraphQL

type Mutation {
  addUser(name: String!, email: [1]): User
}

Drag options to blanks, or click blank then click option'

AString!

BInt

CString

DBoolean

Attempts:

3 left

💡 Hint

Common Mistakes

Using String without ! which makes the argument optional.

Using wrong types like Int or Boolean.

The exclamation mark ! means the email argument is required.

3fill in blank

hard

Fix the error in the mutation return type to correctly return a list of users.

GraphQL

type Mutation {
  addUsers(names: [String!]!): [1]
}

Drag options to blanks, or click blank then click option'

A[User]

BUser

C[User!]

D[User]!

Attempts:

3 left

💡 Hint

Common Mistakes

Returning just User instead of a list.

Using [User] without ! which allows null list.

The mutation returns a non-null list of User objects, so [User]! is correct.

4fill in blank

hard

Fill both blanks to complete the mutation resolver signature in JavaScript.

GraphQL

const resolvers = {
  Mutation: {
    addUser: ([1], [2]) => {
      // resolver code
    }
  }
};

Drag options to blanks, or click blank then click option'

Aparent

Bargs

Ccontext

Dinfo

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping parent and args positions.

Using context or info as first or second argument.

The first argument is usually parent, the second is args containing input data.

5fill in blank

hard

Fill all three blanks to complete the mutation resolver that returns the created user.

GraphQL

const resolvers = {
  Mutation: {
    addUser: (parent, [1]) => {
      const newUser = { name: [2].name, email: [3].email };
      // save newUser to database
      return newUser;
    }
  }
};

Drag options to blanks, or click blank then click option'

Aargs

Bparent

Dcontext

Attempts:

3 left

💡 Hint

Common Mistakes

Using parent instead of args to access input.

Using context which is not the input argument.

The resolver uses args to access input fields name and email.

Practice

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

easy

A. To optimize query performance

B. To create, update, or delete data in the database

C. To define the schema types

D. To fetch data without changing it

Solution

1. Step 1: Understand GraphQL operation types

   GraphQL has queries for reading data and mutations for changing data.

2. Step 2: Identify mutation role

   Mutations are used to create, update, or delete data in the database.

3. Final Answer:

   To create, update, or delete data in the database -> Option B

4. Quick Check:

   Mutation = change data [OK]

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

Common Mistakes:

• Confusing mutations with queries
• Thinking mutations only fetch data
• Mixing schema definition with data operations

2. Which of the following is the correct syntax to start a mutation with an input variable named input of type CreateUserInput!?

easy

A. mutation createUser($input: CreateUserInput!) { ... }

B. query createUser(input: CreateUserInput!) { ... }

C. mutation createUser(input CreateUserInput!) { ... }

D. mutation createUser($input CreateUserInput!) { ... }

Solution

1. Step 1: Recall mutation syntax with variables

   Variables in GraphQL mutations start with $ and have a colon before the type.

2. Step 2: Check each option

   mutation createUser($input: CreateUserInput!) { ... } correctly uses $input: CreateUserInput!. Others miss $ or colon.

3. Final Answer:

   mutation createUser($input: CreateUserInput!) { ... } -> Option A

4. Quick Check:

   Variables need $ and colon [OK]

Hint: Variables start with $ and use colon before type [OK]

Common Mistakes:

• Omitting $ before variable name
• Missing colon between variable and type
• Using query instead of mutation keyword

3. Given this mutation:

mutation AddBook($book: BookInput!) {
  addBook(input: $book) {
    id
    title
  }
}

What fields will the server return after running this mutation?

medium

A. Only the input object sent

B. All fields of the book including author and publishedYear

C. No fields, mutation returns nothing

D. Only the id and title of the new book

Solution

1. Step 1: Identify requested return fields

   The mutation requests id and title fields inside addBook.

2. Step 2: Understand GraphQL response

   GraphQL returns only the fields explicitly requested, so only id and title are returned.

3. Final Answer:

   Only the id and title of the new book -> Option D

4. Quick Check:

   Requested fields = returned fields [OK]

Hint: Returned fields match exactly requested fields in mutation body [OK]

Common Mistakes:

• Assuming all fields return by default
• Expecting input object to be returned
• Thinking mutation returns no data

4. Identify the error in this mutation:

mutation CreatePost($post: PostInput!) {
  createPost(post: $post) {
    id
    content
  }
}

Assuming the server expects the input argument to be named input, not post.

medium

A. The mutation keyword should be query

B. The variable $post should be $input

C. The argument name post should be input

D. The return fields id and content are invalid

Solution

1. Step 1: Check argument name in mutation call

   The mutation calls createPost(post: $post), but server expects input argument.

2. Step 2: Correct argument name

   Changing post to input matches server expectation and fixes error.

3. Final Answer:

   The argument name post should be input -> Option C

4. Quick Check:

   Argument names must match server schema [OK]

Hint: Match argument names exactly as server expects [OK]

Common Mistakes:

• Using wrong argument name in mutation call
• Confusing variable name with argument name
• Changing mutation keyword incorrectly

5. You want to create a mutation to add a new user with fields name and email. Which mutation correctly uses input variables and requests the new user's id and email in the response?

hard

A. mutation AddUser($input: UserInput!) { addUser(input: $input) { id email } }

B. mutation AddUser(input: UserInput!) { addUser(input: input) { id email } }

C. mutation AddUser($user: UserInput!) { addUser(user: $user) { name email } }

D. mutation AddUser($input: UserInput!) { addUser(input: $input) { name } }

Solution

1. Step 1: Check variable declaration and usage

   mutation AddUser($input: UserInput!) { addUser(input: $input) { id email } } correctly declares $input: UserInput! and uses it as input: $input.

2. Step 2: Verify requested return fields

   mutation AddUser($input: UserInput!) { addUser(input: $input) { id email } } requests id and email, matching the question requirement.

3. Final Answer:

   mutation AddUser($input: UserInput!) { addUser(input: $input) { id email } } -> Option A

4. Quick Check:

   Correct variable and requested fields = mutation AddUser($input: UserInput!) { addUser(input: $input) { id email } } [OK]

Hint: Use $variable and request needed fields explicitly [OK]

Common Mistakes:

• Omitting $ in variable declaration or usage
• Requesting wrong fields in response
• Using wrong argument names