Contexts (main, events, http, server, location) in Nginx - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the main context in an Nginx configuration.

Nginx

user nginx;
worker_processes auto;
[1] {
    worker_connections 1024;
}

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

Aserver

Bhttp

Cevents

Dlocation

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'http' instead of 'events' for worker_connections.

Placing 'worker_connections' outside any context.

The events context is used inside the main context to define worker connections and event handling.

2fill in blank

medium

Complete the code to start the HTTP context in Nginx configuration.

Nginx

events {
    worker_connections 1024;
}

[1] {
    include mime.types;
    default_type application/octet-stream;
}

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

Ahttp

Bmain

Clocation

Dserver

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'server' instead of 'http' for HTTP settings.

Placing 'include mime.types' outside the HTTP context.

The http context contains settings for handling HTTP traffic, including MIME types and default content types.

3fill in blank

hard

Fix the error in the server block context declaration.

Nginx

http {
    [1] {
        listen 80;
        server_name example.com;
    }
}

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

Aserver

Blocation

Cevents

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'location' instead of 'server' inside HTTP.

Placing 'server' outside the HTTP context.

The server context defines a virtual server inside the HTTP context.

4fill in blank

hard

Complete the code to define a location block inside a server block.

Nginx

http {
    server {
        listen 80;
        server_name example.com;

        {BLANK_1}} /images/ { {
            root /data;
        }
    }
}

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

Alocation

Bserver

C{

D}

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'server' instead of 'location' for URL matching.

Forgetting the opening brace '{' after the location path.

The location directive defines a location block, which must be followed by a path and an opening brace {.

5fill in blank

hard

Fill both blanks to complete a location block that matches the root URL and sets the root directory.

Nginx

http {
    server {
        listen 80;
        server_name example.com;

        {BLANK_1}} / { {
            {{BLANK_2}} /var/www/html;
        }
    }
}

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

Alocation

Broot

C{

Dserver

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'server' instead of 'location' for the first blank.

Forgetting the opening brace '{' after the location path.

Placing 'root' outside the location block.

The location directive starts the block, followed by an opening brace {, and inside the block the root directive sets the directory for files.

Practice

1. Which nginx context is used to define global settings that affect the entire nginx server?

easy

A. main

B. http

C. server

D. location

Solution

1. Step 1: Understand nginx context scopes

   The main context is the top-level context for global settings.

2. Step 2: Differentiate other contexts

   The http context is for HTTP-specific settings, server for virtual hosts, and location for URL matching.

3. Final Answer:

   main -> Option A

4. Quick Check:

   Global settings = main [OK]

Hint: Global settings go in main context only [OK]

Common Mistakes:

• Confusing http with main context
• Placing global settings inside server or location
• Thinking events is for global settings

2. Which of the following is the correct way to nest the server context inside nginx configuration?

easy

A. main { server { ... } }

B. http { server { ... } }

C. events { server { ... } }

D. location { server { ... } }

Solution

1. Step 1: Recall nginx context hierarchy

   The server context must be inside the http context.

2. Step 2: Check each option's nesting

   Only http { server { ... } } is valid nesting; others are invalid.

3. Final Answer:

   http { server { ... } } -> Option B

4. Quick Check:

   server inside http = correct [OK]

Hint: Server blocks go inside http context [OK]

Common Mistakes:

• Placing server inside main or events
• Nesting server inside location
• Confusing events with http context

3. Given this nginx snippet, what is the correct context for the listen 80; directive?

http {
  server {
    listen 80;
    location / {
      root /var/www/html;
    }
  }
}

medium

A. server

B. events

C. main

D. location

Solution

1. Step 1: Identify where listen directive belongs

   The listen directive configures the port for a virtual host, which belongs in the server context.

2. Step 2: Check the snippet structure

   In the snippet, listen 80; is inside server, which is correct.

3. Final Answer:

   server -> Option A

4. Quick Check:

   listen directive = server context [OK]

Hint: listen always goes inside server context [OK]

Common Mistakes:

• Placing listen inside location
• Thinking listen belongs in main or events
• Confusing location with server context

4. You wrote this nginx config but nginx fails to start:

events {
  server {
    worker_connections 1024;
  }
}

What is the error?

medium

A. Missing http context around server

B. worker_connections must be inside server

C. events context cannot contain any directives

D. server context cannot be inside events

Solution

1. Step 1: Understand events context usage

   The events context is for event-related directives only and cannot contain server blocks.

2. Step 2: Identify invalid nesting

   Placing server inside events is invalid and causes nginx startup failure.

3. Final Answer:

   server context cannot be inside events -> Option D

4. Quick Check:

   server inside events = invalid [OK]

Hint: server blocks never go inside events context [OK]

Common Mistakes:

• Putting server inside events
• Misplacing worker_connections inside server
• Confusing events with http context

5. You want to serve static files from /var/www/html only for URLs starting with /images/. Which context should you use to configure this in nginx?

hard

A. main

B. server

C. location

D. events

Solution

1. Step 1: Identify context for URL matching

   The location context is used to match specific URL patterns like /images/.

2. Step 2: Understand static file serving setup

   Inside location, you set the root directive to serve files from the desired folder.

3. Final Answer:

   location -> Option C

4. Quick Check:

   URL-specific config = location context [OK]

Hint: Use location for URL path specific settings [OK]

Common Mistakes:

• Trying to serve files from main or events
• Placing root directive in server without location
• Confusing server and location contexts