Why securing GraphQL is critical - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a GraphQL query that fetches user data.

GraphQL

query GetUser { user(id: [1]) { name email } }

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

AuserId

B123

C"123"

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using an unquoted number instead of a string ID.

The user ID must be a string in quotes in GraphQL queries.

2fill in blank

medium

Complete the code to add an authorization header to a GraphQL request.

GraphQL

fetch('/graphql', { method: 'POST', headers: { 'Content-Type': 'application/json', 'Authorization': [1] }, body: JSON.stringify({ query }) })

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

A"token123"

BBearer token123

C'token123'

D'Bearer token123'

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting quotes around the header value.

The Authorization header value must be a string with 'Bearer ' prefix and token in quotes.

3fill in blank

hard

Fix the error in the GraphQL schema definition for a secure user type.

GraphQL

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

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

AString

BInt

CBoolean

DFloat

Attempts:

3 left

💡 Hint

Common Mistakes

Using Int or Boolean for email field.

Email should be a String type in GraphQL schema.

4fill in blank

hard

Fill both blanks to create a GraphQL query that limits data exposure by requesting only id and name.

GraphQL

query GetUsers { users { [1] [2] } }

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

Aid

Bemail

Cname

Dpassword

Attempts:

3 left

💡 Hint

Common Mistakes

Including sensitive fields like password or email in the query.

Requesting only 'id' and 'name' limits sensitive data exposure like email or password.

5fill in blank

hard

Fill all three blanks to write a GraphQL mutation that updates a user's email securely.

GraphQL

mutation UpdateUserEmail { updateUser(id: [1], email: [2]) { [3] } }

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

A"123"

B"[e-mail]"

Cemail

Dpassword

Attempts:

3 left

💡 Hint

Common Mistakes

Using unquoted values or returning sensitive fields like password.

The mutation requires the user ID and new email as strings, and returns the updated email field.

Practice

1. Why is securing a GraphQL API critical for database safety?

easy

A. Because security adds more features automatically

B. Because GraphQL APIs are slower without security

C. To make the API easier to use for everyone

D. To prevent unauthorized users from accessing or modifying data

Solution

1. Step 1: Understand the purpose of security in APIs

   Security protects data from being accessed or changed by people who shouldn't have permission.

2. Step 2: Relate this to GraphQL APIs

   GraphQL APIs expose data queries and mutations, so without security, anyone could misuse them.

3. Final Answer:

   To prevent unauthorized users from accessing or modifying data -> Option D

4. Quick Check:

   Security = prevent unauthorized access [OK]

Hint: Think: Who should see or change data? Secure to protect! [OK]

Common Mistakes:

• Confusing security with performance
• Assuming security adds features automatically
• Thinking security makes APIs easier for everyone

2. Which of the following is the correct way to limit query complexity in a GraphQL server?

easy

A. Use only REST endpoints instead of GraphQL

B. Allow all queries without checks to improve speed

C. Use a middleware that checks query depth before execution

D. Disable authentication to reduce errors

Solution

1. Step 1: Identify how to limit query complexity

   Limiting query depth or complexity prevents expensive or malicious queries from overloading the server.

2. Step 2: Choose the correct method

   Middleware that checks query depth before running the query is a common and effective approach.

3. Final Answer:

   Use a middleware that checks query depth before execution -> Option C

4. Quick Check:

   Limit query depth = middleware check [OK]

Hint: Limit query depth with middleware to protect server [OK]

Common Mistakes:

• Disabling authentication thinking it helps
• Allowing all queries without checks
• Confusing REST with GraphQL security

3. Given this GraphQL query and security setup, what will happen if an unauthorized user tries to fetch sensitive data?

{ user(id: "123") { name, email, password } }

Assume the server uses authorization rules to block access to password field for unauthorized users.

medium

A. The query returns name and email but omits the password field

B. The query fails with an authorization error

C. The query returns all fields including password

D. The query returns no data at all

Solution

1. Step 1: Understand authorization rules on fields

   If a field is protected, unauthorized users should not access it; the server usually blocks the entire query or returns an error.

2. Step 2: Predict server behavior on unauthorized access

   Most secure GraphQL servers reject queries requesting forbidden fields rather than partially returning data.

3. Final Answer:

   The query fails with an authorization error -> Option B

4. Quick Check:

   Unauthorized field access = error [OK]

Hint: Unauthorized field access usually causes an error [OK]

Common Mistakes:

• Assuming partial data is returned
• Thinking password is visible to all
• Believing query returns no data silently

4. You have a GraphQL server that crashes when a user sends a very deep nested query. What is the best way to fix this issue?

medium

A. Implement query depth limiting middleware to reject too deep queries

B. Remove all authentication to speed up query processing

C. Allow unlimited query depth but increase server RAM

D. Disable logging to reduce server load

Solution

1. Step 1: Identify cause of crash

   Very deep nested queries can overload the server causing crashes.

2. Step 2: Choose a fix that prevents overload

   Limiting query depth with middleware stops too complex queries before execution, preventing crashes.

3. Final Answer:

   Implement query depth limiting middleware to reject too deep queries -> Option A

4. Quick Check:

   Limit query depth to prevent crashes [OK]

Hint: Limit query depth to avoid server crashes [OK]

Common Mistakes:

• Removing authentication which weakens security
• Relying only on hardware upgrades
• Disabling logging which doesn't fix query issues

5. You want to secure your GraphQL API so only logged-in users can update their own profiles. Which combination of methods best achieves this?

hard

A. Use authentication to verify users, authorization to check ownership, and query limits to prevent abuse

B. Only use authentication and allow all updates after login

C. Use query limits only to stop large updates

D. Disable mutations and allow only queries

Solution

1. Step 1: Understand the need for authentication

   Authentication confirms the user is logged in and identifies them.

2. Step 2: Apply authorization to check if user owns the profile

   Authorization ensures users can only update their own data, not others'.

3. Step 3: Use query limits to prevent abuse

   Query limits protect the server from overly large or complex update requests.

4. Final Answer:

   Use authentication to verify users, authorization to check ownership, and query limits to prevent abuse -> Option A

5. Quick Check:

   Auth + Authorization + Limits = Secure updates [OK]

Hint: Combine auth, ownership checks, and limits for secure updates [OK]

Common Mistakes:

• Skipping authorization and trusting authentication alone
• Relying only on query limits
• Disabling mutations which stops updates entirely