Bird
Raised Fist0
GraphQLquery~20 mins

Search across types in GraphQL - Practice Problems & Coding Challenges

Choose your learning style10 modes available
Challenge - 5 Problems
🎖️
Master of Search Across Types
Get all challenges correct to earn this badge!
Test your skills under time pressure!
❓ query_result
intermediate
2:00remaining
What is the output of this GraphQL query searching across types?

Given a GraphQL schema with types Book and Author, and a search query that returns a union of these types, what will be the result of this query?

query {
  search(text: "Alice") {
    __typename
    ... on Book {
      title
      pages
    }
    ... on Author {
      name
      booksWritten
    }
  }
}
A[{"name": "Alice Walker", "booksWritten": 12}, {"title": "Alice in Wonderland", "pages": 200}]
B[{"__typename": "Author", "name": "Alice Walker", "booksWritten": 12}, {"__typename": "Book", "title": "Alice in Wonderland", "pages": 200}]
C[{"__typename": "Book", "title": "Alice in Wonderland", "pages": 200}]
D[]
Attempts:
2 left
💡 Hint

Remember that the search query returns a union type, so you need to check the __typename to know which fields are available.

🧠 Conceptual
intermediate
1:30remaining
Which GraphQL feature allows searching across multiple types in one query?

In GraphQL, how can you write a query that searches across different types like Movie and Director and returns results from both?

AUsing fragments only on one type
BUsing multiple separate queries for each type
CUsing a union type in the schema and inline fragments in the query
DUsing scalar types instead of objects
Attempts:
2 left
💡 Hint

Think about how to combine different types into one result list.

📝 Syntax
advanced
1:30remaining
Identify the syntax error in this GraphQL search query across types

What is wrong with this GraphQL query that searches across Article and Author types?

query {
  search(text: "GraphQL") {
    ... on Article {
      title
      content
    }
    ... on Author
      name
      articlesCount
  }
}
AThe search field must be called searchAll
BMissing __typename field in the query
CUsing ... on Article instead of ... on Articles
DMissing curly braces around the Author inline fragment fields
Attempts:
2 left
💡 Hint

Check the syntax of inline fragments carefully.

❓ optimization
advanced
1:30remaining
How to optimize a GraphQL search query across types to reduce data transfer?

You have a search query returning a union of Product and Category. How can you reduce the amount of data sent over the network?

ARequest only the fields you need using inline fragments
BRemove the search filter to get fewer results
CUse a scalar type instead of a union type
DRequest all fields for both types to avoid multiple queries
Attempts:
2 left
💡 Hint

Think about selecting only necessary data.

🔧 Debug
expert
2:30remaining
Why does this GraphQL search query across types return an empty list?

Given this query:

query {
  search(text: "John") {
    __typename
    ... on User {
      username
    }
    ... on Post {
      title
    }
  }
}

But the result is always an empty list, even though there are users and posts with "John" in their data. What is the most likely cause?

AThe search resolver does not implement searching across both User and Post types
BThe query is missing the <code>id</code> field in the fragments
CThe <code>__typename</code> field is causing the query to fail
DThe search argument <code>text</code> is case-sensitive and "John" does not match
Attempts:
2 left
💡 Hint

Think about what the backend resolver does with the search argument.

Practice

(1/5)
1. What does the __typename field do in a GraphQL query when searching across types?
easy
A. It tells you the type of each returned object in the result.
B. It filters the results to only one type.
C. It sorts the results alphabetically.
D. It limits the number of results returned.

Solution

  1. Step 1: Understand the role of __typename

    The __typename field returns the name of the type of each object in the query result.
  2. Step 2: Differentiate from other options

    It does not filter, sort, or limit results; it only identifies the type.
  3. Final Answer:

    It tells you the type of each returned object in the result. -> Option A
  4. Quick Check:

    __typename shows object type [OK]
Hint: Remember: __typename reveals object type, not filters or limits [OK]
Common Mistakes:
  • Thinking __typename filters results
  • Assuming it sorts or limits data
  • Confusing it with field selection
2. Which of the following is the correct syntax to query two different types, Book and Author, in one GraphQL query using fragments?
easy
A. query { search { ... on Book { title } ... on Author { name } } }
B. query { search { Book { title } Author { name } } }
C. query { search { title, name } }
D. query { search { ...Book { title } ...Author { name } } }

Solution

  1. Step 1: Recognize fragment syntax for multiple types

    Fragments use ... on TypeName { fields } to specify fields for each type.
  2. Step 2: Check each option's syntax

    query { search { ... on Book { title } ... on Author { name } } } correctly uses inline fragments for Book and Author. Options B, C, and D have invalid syntax.
  3. Final Answer:

    query { search { ... on Book { title } ... on Author { name } } } -> Option A
  4. Quick Check:

    Fragments use ... on Type [OK]
Hint: Use ... on Type for each type's fields [OK]
Common Mistakes:
  • Using type names as fields directly
  • Omitting 'on' keyword in fragments
  • Trying to list fields without fragments
3. Given this GraphQL query:
query { search { __typename ... on Book { title author } ... on Author { name booksCount } } }

What will be the output if the search returns one Book and one Author?
medium
A. [{ "title": "1984", "author": "Orwell" }, { "name": "Orwell", "booksCount": 5 }]
B. [{ "__typename": "Book", "title": "1984", "author": "Orwell" }, { "__typename": "Author", "name": "Orwell", "booksCount": 5 }]
C. [{ "__typename": "Book", "name": "1984", "author": "Orwell" }, { "__typename": "Author", "title": "Orwell", "booksCount": 5 }]
D. Error: Cannot query field 'booksCount' on type 'Author'

Solution

  1. Step 1: Understand the query structure

    The query requests __typename and fields specific to Book and Author types.
  2. Step 2: Match output to query

    The output includes type names and requested fields correctly matched to each object.
  3. Final Answer:

    [{ "__typename": "Book", "title": "1984", "author": "Orwell" }, { "__typename": "Author", "name": "Orwell", "booksCount": 5 }] -> Option B
  4. Quick Check:

    Output matches requested fields and types [OK]
Hint: Look for __typename and matching fields in output [OK]
Common Mistakes:
  • Ignoring __typename in output
  • Mixing fields between types
  • Assuming syntax errors without cause
4. Identify the error in this GraphQL query that searches across types:
query { search { ... on Book { title author } ... on Author { name booksCount } } }

Assuming booksCount is not a valid field on Author type.
medium
A. The query will ignore the Author fragment entirely.
B. The query will succeed but return null for booksCount.
C. The query will fail because booksCount is not a valid field on Author.
D. The query syntax is invalid due to missing commas.

Solution

  1. Step 1: Check field validity on types

    Since booksCount is not defined on Author, the query is invalid.
  2. Step 2: Understand GraphQL error handling

    GraphQL returns an error and fails the query if a requested field does not exist on the type.
  3. Final Answer:

    The query will fail because booksCount is not a valid field on Author. -> Option C
  4. Quick Check:

    Invalid field causes query failure [OK]
Hint: Check if all fields exist on their types before querying [OK]
Common Mistakes:
  • Assuming invalid fields return null
  • Ignoring GraphQL schema validation errors
  • Thinking commas are required between fragments
5. You want to search across three types: Book, Author, and Publisher. Each type has a field name, but Book also has pages, Author has birthYear, and Publisher has location. Which query correctly fetches the name for all types and their specific fields?
hard
A. query { search { ...Book { name pages } ...Author { name birthYear } ...Publisher { name location } } }
B. query { search { name pages birthYear location } }
C. query { search { __typename { name } ... on Book { pages } ... on Author { birthYear } ... on Publisher { location } } }
D. query { search { __typename ... on Book { name pages } ... on Author { name birthYear } ... on Publisher { name location } } }

Solution

  1. Step 1: Use __typename to identify each type

    This helps distinguish which object is which type in the results.
  2. Step 2: Use inline fragments with ... on Type syntax

    Each fragment fetches the common name and the type-specific fields.
  3. Step 3: Verify syntax correctness

    query { search { __typename ... on Book { name pages } ... on Author { name birthYear } ... on Publisher { name location } } } correctly uses fragments and includes __typename. Other options have syntax errors or missing fragments.
  4. Final Answer:

    query { search { __typename ... on Book { name pages } ... on Author { name birthYear } ... on Publisher { name location } } } -> Option D
  5. Quick Check:

    Fragments + __typename fetch all fields correctly [OK]
Hint: Use __typename and fragments for each type's fields [OK]
Common Mistakes:
  • Listing all fields without fragments
  • Omitting __typename for type identification
  • Incorrect fragment syntax without 'on'
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard