Introspection control in GraphQL - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to disable introspection in a GraphQL server.

GraphQL

const server = new ApolloServer({ schema, [1] });

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

Aintrospection: false

Bintrospection: true

Cintrospect: false

Dintrospect: true

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'introspect' instead of 'introspection'.

Setting introspection to true disables it (it's the opposite).

Setting introspection: false disables introspection queries in Apollo Server.

2fill in blank

medium

Complete the code to allow introspection only in development environment.

GraphQL

const server = new ApolloServer({ schema, introspection: process.env.NODE_ENV === [1] });

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

A'staging'

B'production'

C'development'

D'test'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'production' instead of 'development'.

Forgetting to use quotes around the environment string.

Introspection is usually enabled only in development to prevent exposing schema details in production.

3fill in blank

hard

Fix the error in the code to properly disable introspection in Apollo Server.

GraphQL

const server = new ApolloServer({ schema, introspection: [1] });

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

Aundefined

B0

Cnull

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using 0 or null instead of false.

Leaving the option undefined.

The introspection option expects a boolean. Use false to disable it.

4fill in blank

hard

Fill both blanks to disable introspection and enable playground only in development.

GraphQL

const server = new ApolloServer({ schema, introspection: [1], playground: [2] });

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

Afalse

Bprocess.env.NODE_ENV === 'development'

Ctrue

Dprocess.env.NODE_ENV === 'production'

Attempts:

3 left

💡 Hint

Common Mistakes

Enabling introspection by mistake.

Enabling playground in production.

Introspection is disabled with false. Playground is enabled only in development environment.

5fill in blank

hard

Fill all three blanks to create a GraphQL server that disables introspection, disables playground, and sets a custom schema.

GraphQL

const server = new ApolloServer({ schema: [1], introspection: [2], playground: [3] });

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

AmyCustomSchema

Bfalse

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using true for introspection or playground.

Not passing the schema variable correctly.

The server uses a custom schema myCustomSchema, disables introspection and playground by setting both to false.

Practice

1. What is the main purpose of introspection control in GraphQL?

easy

A. To speed up database queries by caching results

B. To allow or block schema queries for security and performance

C. To automatically generate API documentation

D. To encrypt data sent between client and server

Solution

1. Step 1: Understand what introspection means in GraphQL

   Introspection allows clients to query the schema itself to learn about types and fields.

2. Step 2: Identify the purpose of controlling introspection

   Controlling introspection lets you block or allow these schema queries to protect your API and improve performance.

3. Final Answer:

   To allow or block schema queries for security and performance -> Option B

4. Quick Check:

   Introspection control = Allow/block schema queries [OK]

Hint: Introspection controls schema query access, not data fetching [OK]

Common Mistakes:

• Confusing introspection with data query optimization
• Thinking introspection encrypts data
• Assuming introspection auto-generates docs

2. Which of the following is the correct way to disable introspection in a GraphQL server setup?

easy

A. introspection: 'off'

B. introspection = false

C. disableIntrospection: true

D. introspection: false

Solution

1. Step 1: Recall the syntax for toggling introspection in GraphQL server config

   The option is usually set as introspection: true or introspection: false.

2. Step 2: Identify the correct syntax to disable introspection

   Setting introspection: false disables introspection queries.

3. Final Answer:

   introspection: false -> Option D

4. Quick Check:

   Disable introspection = introspection: false [OK]

Hint: Use boolean false, not strings or other keys [OK]

Common Mistakes:

• Using assignment (=) instead of colon (:)
• Using string values instead of boolean
• Using incorrect option names like disableIntrospection

3. Given this GraphQL server config snippet:

const server = new ApolloServer({
  typeDefs,
  resolvers,
  introspection: false
});

What will happen if a client sends an introspection query?

medium

A. The server will return an error or empty response

B. The server will respond with the full schema details

C. The server will ignore the introspection query and respond normally

D. The server will crash due to unsupported query

Solution

1. Step 1: Understand the effect of introspection: false

   This setting disables introspection queries, so the server blocks schema queries.

2. Step 2: Predict server response to introspection query

   The server will reject the introspection query, usually returning an error or empty result.

3. Final Answer:

   The server will return an error or empty response -> Option A

4. Quick Check:

   introspection: false blocks schema queries [OK]

Hint: introspection false means introspection queries fail [OK]

Common Mistakes:

• Thinking server still returns schema data
• Assuming server crashes on introspection query
• Believing server ignores introspection queries silently

4. You wrote this server setup:

const server = new ApolloServer({
  typeDefs,
  resolvers,
  introspection: 'false'
});

Why does introspection control not work as expected?

medium

A. Because ApolloServer does not support introspection control

B. Because introspection must be set to true to disable it

C. Because introspection expects a boolean, not a string

D. Because typeDefs is missing introspection schema

Solution

1. Step 1: Check the data type of the introspection option

   The option should be a boolean (true or false), not a string.

2. Step 2: Identify why using a string causes failure

   Using 'false' as a string is truthy in JavaScript, so introspection remains enabled.

3. Final Answer:

   Because introspection expects a boolean, not a string -> Option C

4. Quick Check:

   introspection must be boolean, not string [OK]

Hint: Use true/false without quotes for boolean options [OK]

Common Mistakes:

• Using string 'false' instead of boolean false
• Thinking introspection must be true to disable
• Assuming ApolloServer lacks introspection control

5. You want to improve API security by disabling introspection only in production but keep it enabled in development. Which code snippet correctly implements this?

hard

A. const server = new ApolloServer({ typeDefs, resolvers, introspection: process.env.NODE_ENV !== 'production' });

B. const server = new ApolloServer({ typeDefs, resolvers, introspection: process.env.NODE_ENV === 'production' });

C. const server = new ApolloServer({ typeDefs, resolvers, introspection: false });

D. const server = new ApolloServer({ typeDefs, resolvers, introspection: true });

Solution

1. Step 1: Understand the goal

   Disable introspection in production, enable in development.

2. Step 2: Analyze each option's logic

   const server = new ApolloServer({ typeDefs, resolvers, introspection: process.env.NODE_ENV !== 'production' }); sets introspection to true when not in production, false in production, matching the goal.

3. Final Answer:

   const server = new ApolloServer({ typeDefs, resolvers, introspection: process.env.NODE_ENV !== 'production' }); -> Option A

4. Quick Check:

   introspection enabled only if not production [OK]

Hint: Use environment check with !== 'production' for introspection [OK]

Common Mistakes:

• Using === 'production' enables introspection in production
• Always setting introspection true or false ignores environment
• Confusing production and development environment logic