Solution:Step 1: Understand schema and queryThe Employee type has a one-to-one desk field of type Desk.Step 2: Analyze query resultThe query requests name and nested desk.location. Since the employee has a desk, both fields will be returned.Final Answer:The employee's name and the location of their

[Solved] Given this schema:type Employee { id: ID! name: Str... location: String }What will this query return?{ employee(id: "5") { name desk { location } } }Assuming employee with id "5" has a desk assigned. | GraphQL

GraphQL - Type Relationships

Given this schema:

type Employee { id: ID! name: String desk: Desk }

type Desk { id: ID! location: String }

What will this query return?

{ employee(id: "5") { name desk { location } } }

Assuming employee with id "5" has a desk assigned.

AThe employee's name and the location of their desk

BOnly the employee's name, desk will be null

CAn error because desk is not a list

DThe employee's name and a list of desk locations

Step-by-Step Solution

Solution:

Step 1: Understand schema and query
The Employee type has a one-to-one desk field of type Desk.
Step 2: Analyze query result
The query requests name and nested desk.location. Since the employee has a desk, both fields will be returned.
Final Answer:
The employee's name and the location of their desk -> Option A
Quick Check:
One-to-one returns nested object if exists [OK]

Quick Trick: One-to-one returns nested object if present [OK]

Common Mistakes:

Assuming desk returns a list
Expecting null when desk exists
Confusing one-to-one with one-to-many

Master "Type Relationships" in GraphQL

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More GraphQL Quizzes

Given this schema:

Step 1: Understand schema and query

Step 2: Analyze query result

Final Answer:

Quick Check:

Want More Practice?