Why advanced features improve flexibility in GraphQL - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to query the name of a user.

GraphQL

query { user(id: 1) { [1] } }

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

Aname

Bage

Cemail

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a field that does not represent the user's name.

Leaving the field blank.

The field name returns the user's name as requested.

2fill in blank

medium

Complete the code to fetch the user's email address.

GraphQL

query { user(id: 2) { [1] } }

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

Aemail

Bage

Cname

Daddress

Attempts:

3 left

💡 Hint

Common Mistakes

Selecting a field unrelated to email.

Confusing 'email' with 'address'.

The email field returns the user's email address.

3fill in blank

hard

Fix the error in the query to get the user's age.

GraphQL

query { user(id: 3) { [1] } }

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

Aphone

Bemail

Cname

Dage

Attempts:

3 left

💡 Hint

Common Mistakes

Using a field that does not exist or is unrelated to age.

Misspelling the field name.

The field age correctly fetches the user's age.

4fill in blank

hard

Fill both blanks to query user's name and email.

GraphQL

query { user(id: 4) { [1] [2] } }

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

Aname

Bemail

Cage

Daddress

Attempts:

3 left

💡 Hint

Common Mistakes

Selecting fields unrelated to name or email.

Using the same field twice.

To get both name and email, include name and email fields.

5fill in blank

hard

Fill all three blanks to query user's name, email, and age.

GraphQL

query { user(id: 5) { [1] [2] [3] } }

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

Aaddress

Bemail

Cage

Dname

Attempts:

3 left

💡 Hint

Common Mistakes

Including unrelated fields like address.

Missing one of the required fields.

The fields name, email, and age fetch the requested user information.

Practice

1. What is one main benefit of using advanced features in GraphQL queries?

easy

A. You can request only the data you need, reducing data transfer.

B. It makes the server slower by processing more data.

C. You must always request all fields in a query.

D. It prevents you from filtering data.

Solution

1. Step 1: Understand GraphQL query flexibility

   GraphQL allows clients to specify exactly which fields they want in a query.

2. Step 2: Recognize the benefit of selective data fetching

   Requesting only needed data reduces the amount of data sent over the network, improving speed and efficiency.

3. Final Answer:

   You can request only the data you need, reducing data transfer. -> Option A

4. Quick Check:

   Selective data fetching = You can request only the data you need, reducing data transfer. [OK]

Hint: Advanced features let you pick only needed data [OK]

Common Mistakes:

• Thinking GraphQL always sends all data
• Believing advanced features slow down the server
• Assuming filtering is not possible

2. Which of the following is the correct syntax to filter a list of users by age greater than 18 in GraphQL?

easy

A. query { users(where: {age: {gt: 18}}) { id name } }

B. query { users(filter: {age: >18}) { id name } }

C. query { users(age > 18) { id name } }

D. query { users(age_gt: 18) { id name } }

Solution

1. Step 1: Identify correct GraphQL filter syntax

   GraphQL commonly uses nested input objects for filtering, like where: {field: {operator: value}}.

2. Step 2: Match the syntax to the options

   query { users(where: {age: {gt: 18}}) { id name } } uses where: {age: {gt: 18}}, which is the standard way to filter for age greater than 18.

3. Final Answer:

   query { users(where: {age: {gt: 18}}) { id name } } -> Option A

4. Quick Check:

   Filter syntax with nested objects = query { users(where: {age: {gt: 18}}) { id name } } [OK]

Hint: Use nested objects for filters like where: {field: {operator: value}} [OK]

Common Mistakes:

• Using invalid operators directly in arguments
• Incorrect filter key names
• Missing nested structure for conditions

3. Given the GraphQL query:

query { books(filter: {rating_gte: 4}) { title author { name } } }

What will the query return?

medium

A. An error because nested author fields are not allowed.

B. All books with rating less than 4 and their authors' names.

C. Only the titles of all books regardless of rating.

D. Books with rating greater than or equal to 4 and their authors' names.

Solution

1. Step 1: Understand the filter condition

   The filter rating_gte: 4 means rating greater than or equal to 4.

2. Step 2: Analyze requested fields

   The query asks for book titles and nested author names, which is valid and returns those fields.

3. Final Answer:

   Books with rating greater than or equal to 4 and their authors' names. -> Option D

4. Quick Check:

   Filter rating_gte=4 + nested author = Books with rating greater than or equal to 4 and their authors' names. [OK]

Hint: gte means greater or equal; nested fields are allowed [OK]

Common Mistakes:

• Confusing gte with less than
• Thinking nested fields cause errors
• Ignoring filter conditions

4. Identify the error in this GraphQL query:

query { users(filter: {age: {gt: 20}}) { id name posts { title } } }

medium

A. The filter syntax is incorrect; 'gt' should be 'greaterThan'.

B. Nested fields like posts are not allowed inside users.

C. The query is valid and will return users older than 20 with their posts' titles.

D. The filter key should be 'where' instead of 'filter'.

Solution

1. Step 1: Check filter syntax

   Using filter: {age: {gt: 20}} is a common and valid way to filter users older than 20.

2. Step 2: Verify nested fields

   Requesting nested posts { title } inside users is allowed to fetch related data.

3. Final Answer:

   The query is valid and will return users older than 20 with their posts' titles. -> Option C

4. Quick Check:

   Valid filter and nested fields = The query is valid and will return users older than 20 with their posts' titles. [OK]

Hint: Check if filter and nested fields follow schema rules [OK]

Common Mistakes:

• Assuming 'gt' is invalid
• Thinking nested fields are forbidden
• Confusing filter and where keywords

5. You want to fetch a list of products with their categories, but only products priced above 50 and categories that are active. Which GraphQL query structure best uses advanced features for this?

hard

A. query { products(filter: {price_gt: 50}) { name category { name active } } }

B. query { products(filter: {price_gt: 50, category: {active: true}}) { name category { name } } }

C. query { products { name category(filter: {active: true}) { name } } }

D. query { products(filter: {price_gt: 50}) { name category(filter: {active: true}) { name } } }

Solution

1. Step 1: Understand filtering on related fields

   To filter products by price and also filter categories by active status, the filter must include nested conditions.

2. Step 2: Analyze options for nested filtering

   query { products(filter: {price_gt: 50, category: {active: true}}) { name category { name } } } uses filter: {price_gt: 50, category: {active: true}}, which applies filters on both product and its category correctly.

3. Final Answer:

   query { products(filter: {price_gt: 50, category: {active: true}}) { name category { name } } } -> Option B

4. Quick Check:

   Nested filters for related fields = query { products(filter: {price_gt: 50, category: {active: true}}) { name category { name } } } [OK]

Hint: Use nested filters inside main filter for related data [OK]

Common Mistakes:

• Filtering related fields outside main filter
• Applying filters only on one level
• Ignoring nested filter syntax