Node interface pattern in GraphQL - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a Node interface with an ID field.

GraphQL

interface Node { id: [1]! }

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

AString

BInt

CID

DBoolean

Attempts:

3 left

💡 Hint

Common Mistakes

Using String instead of ID for the id field.

Omitting the non-nullable exclamation mark (!).

The Node interface requires an id field of type ID! which is a unique identifier.

2fill in blank

medium

Complete the code to make the User type implement the Node interface.

GraphQL

type User implements [1] { id: ID! name: String! }

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

AEntity

BObject

CInterface

DNode

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong interface name like Entity or Interface.

Forgetting to implement the Node interface.

The User type implements the Node interface to ensure it has an id field.

3fill in blank

hard

Fix the error in the Node interface definition by completing the type of the id field.

GraphQL

interface Node { id: [1] }

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

AID!

BInt

CString

DBoolean

Attempts:

3 left

💡 Hint

Common Mistakes

Using nullable types like String or Int for id.

Omitting the exclamation mark to make id non-nullable.

The id field must be of type ID! to be a non-null unique identifier.

4fill in blank

hard

Fill both blanks to define a Query type with a node field that returns a Node by id.

GraphQL

type Query { node(id: [1]!): [2] }

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

AID

BString

CNode

DUser

Attempts:

3 left

💡 Hint

Common Mistakes

Using String instead of ID for the id argument.

Returning a concrete type like User instead of the Node interface.

The node field takes an id of type ID! and returns a Node interface type.

5fill in blank

hard

Fill all three blanks to define a schema with Node interface, User type implementing Node, and Query type with node field.

GraphQL

interface [1] { id: ID! } type [2] implements Node { id: ID! name: String! } type [3] { node(id: ID!): Node }

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

ANode

BUser

CQuery

DMutation

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up type names like Mutation instead of Query.

Not implementing Node interface in User type.

This schema defines the Node interface, a User type implementing Node, and a Query type with a node field to fetch any Node by id.

Practice

1. What is the main purpose of the Node interface in GraphQL?

easy

A. To provide a unique ID for all object types

B. To define custom mutations for each type

C. To restrict queries to only one type

D. To automatically generate database schemas

Solution

1. Step 1: Understand the Node interface role

   The Node interface is designed to give every object type a unique identifier.

2. Step 2: Identify its main use

   This unique ID allows fetching any object by ID in a single query.

3. Final Answer:

   To provide a unique ID for all object types -> Option A

4. Quick Check:

   Node interface = unique ID for all types [OK]

Hint: Node interface always provides unique IDs for all types [OK]

Common Mistakes:

• Thinking Node defines mutations
• Believing Node restricts queries to one type
• Assuming Node auto-generates database schemas

2. Which of the following is the correct way to declare the Node interface in GraphQL SDL?

easy

A. interface Node { id: Boolean! }

B. interface Node { id: String }

C. interface Node { id: Int! }

D. interface Node { id: ID! }

Solution

1. Step 1: Recall the Node interface ID type

   The Node interface requires an id field of type ID!, which is a non-null unique identifier.

2. Step 2: Check each option's ID type

   interface Node { id: ID! } uses ID!, which is correct. Others use wrong types like String, Int, or Boolean.

3. Final Answer:

   interface Node { id: ID! } -> Option D

4. Quick Check:

   ID field in Node = ID! type [OK]

Hint: Node interface ID must be non-null ID type [OK]

Common Mistakes:

• Using String or Int instead of ID type
• Making ID nullable (missing !)
• Using Boolean as ID type

3. Given this query using the Node interface:

query { node(id: "123") { id ... on User { name } ... on Post { title } } }

What fields will be returned if the node with ID "123" is a Post?

medium

A. { "id": "123", "name": "Alice" }

B. { "id": "123", "title": "GraphQL Basics" }

C. { "id": "123" }

D. Error: Cannot query fragment on Post

Solution

1. Step 1: Understand the query structure

   The query fetches a node by ID and requests the id field plus fragments for User and Post types.

2. Step 2: Determine the node type and returned fields

   If the node is a Post, the title field from the Post fragment is returned along with id. The User fragment is ignored.

3. Final Answer:

   { "id": "123", "title": "GraphQL Basics" } -> Option B

4. Quick Check:

   Node query returns fields for actual type fragment [OK]

Hint: Fragments return fields only for matching node type [OK]

Common Mistakes:

• Expecting fields from non-matching fragments
• Ignoring the id field
• Assuming query causes error

4. You wrote this schema snippet:

interface Node { id: ID! }
type User implements Node { id: ID name: String }

Why will this schema cause an error?

medium

A. User's id field must be non-null (ID!) to match Node interface

B. User type cannot implement Node interface

C. id field type must be String, not ID

D. User type must not have extra fields like name

Solution

1. Step 1: Compare interface and type field definitions

   The Node interface requires id as ID! (non-null). The User type declares id as ID (nullable).

2. Step 2: Understand GraphQL type compatibility rules

   Implementing types must match or be more strict. Here, User's id is less strict (nullable), causing an error.

3. Final Answer:

   User's id field must be non-null (ID!) to match Node interface -> Option A

4. Quick Check:

   Implementing type fields must match interface exactly [OK]

Hint: Implementing type fields must be equal or stricter than interface [OK]

Common Mistakes:

• Thinking User can't implement Node
• Changing id type to String
• Removing extra fields like name

5. You want to fetch a list of mixed objects (Users and Posts) by their IDs using the Node interface. Which approach correctly fetches their specific fields in one query?

hard

A. Use a union type instead of Node interface

B. Query Users and Posts separately with two queries

C. Use a nodes(ids: [ID!]!) query returning [Node], then use inline fragments for User and Post fields

D. Fetch only the id field without fragments

Solution

1. Step 1: Understand Node interface usage for mixed types

   The Node interface allows fetching any object by ID in one query, returning a list of Nodes.

2. Step 2: Use inline fragments to get type-specific fields

   To get fields specific to Users and Posts, use inline fragments ... on User and ... on Post inside the query.

3. Final Answer:

   Use a nodes(ids: [ID!]!) query returning [Node], then use inline fragments for User and Post fields -> Option C

4. Quick Check:

   Node interface + fragments fetch mixed types in one query [OK]

Hint: Use nodes query with fragments for mixed type fields [OK]

Common Mistakes:

• Querying types separately instead of one query
• Using union instead of interface for this pattern
• Fetching only id without needed fields