Event-driven architecture in Nginx - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define an event handler for HTTP requests in NGINX.

Nginx

server {
    listen 80;
    location / {
        [1];
    }
}

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

Aproxy_pass http://backend

Broot /var/www/html

Creturn 200 'Hello World'

Derror_page 404 /404.html

Attempts:

3 left

💡 Hint

Common Mistakes

Using proxy_pass without defining a backend.

Using root without specifying a file.

Using error_page which handles errors, not normal requests.

The return 200 'Hello World' directive sends a simple response, acting as an event handler for HTTP requests.

2fill in blank

medium

Complete the code to trigger an event when a client connects using the NGINX stream module.

Nginx

stream {
    server {
        listen 12345;
        [1];
    }
}

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

Aroot /var/stream

Bproxy_pass backend:12345

Creturn 200 'Connected'

Derror_page 500 /500.html

Attempts:

3 left

💡 Hint

Common Mistakes

Using return in stream context which is invalid.

Using root which is for HTTP context.

Using error_page which handles errors, not connections.

The proxy_pass directive forwards the connection to a backend server, triggering an event on client connect.

3fill in blank

hard

Fix the error in the event-driven NGINX configuration to correctly log client connections.

Nginx

events {
    [1] 1024;
}

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

Aworker_connections

Bworker_processes

Cclient_max_body_size

Derror_log

Attempts:

3 left

💡 Hint

Common Mistakes

Using worker_processes inside events block.

Using client_max_body_size which is unrelated.

Using error_log which is for logging errors.

The worker_connections directive sets the maximum number of simultaneous connections per worker, essential for event handling.

4fill in blank

hard

Fill both blanks to create a map that triggers different actions based on request method.

Nginx

map $request_method $action {
    GET [1];
    POST [2];
}

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

A1

B0

Cdefault

Dproxy_pass

Attempts:

3 left

💡 Hint

Common Mistakes

Using proxy_pass inside map values which is invalid.

Using default as a value for specific methods.

Mixing string and numeric values inconsistently.

The map assigns 1 for GET requests and 0 for POST requests, which can be used to trigger different actions.

5fill in blank

hard

Fill all three blanks to define a server block that triggers an event on a specific URI and proxies the request.

Nginx

server {
    listen 80;
    location [1] {
        [2] http://backend;
        [3] 10s;
    }
}

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

A/api/event

Bproxy_pass

Cproxy_read_timeout

D/home

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong location paths that don't match the event.

Omitting proxy_pass causing no forwarding.

Using incorrect timeout directives.

The location /api/event matches the event URI, proxy_pass forwards the request, and proxy_read_timeout sets the timeout for the proxy response.

Practice

1. What is the main purpose of the events block in an nginx configuration?

easy

A. To configure how nginx handles connections and events

B. To define server names and ports

C. To specify the location of website files

D. To set up SSL certificates

Solution

1. Step 1: Understand the role of the events block

   The events block in nginx is used to configure how nginx manages connections and event handling.

2. Step 2: Differentiate from other blocks

   Other blocks like server handle server names and ports, while http handles website files and SSL setup.

3. Final Answer:

   To configure how nginx handles connections and events -> Option A

4. Quick Check:

   events block = connection management [OK]

Hint: Remember: events controls connection handling [OK]

Common Mistakes:

• Confusing events with server block
• Thinking events sets file locations
• Assuming events manages SSL

2. Which of the following is the correct syntax to set the event method to epoll in nginx?

easy

A. events { use epoll; }

B. events { event_method epoll; }

C. events { set_event epoll; }

D. events { epoll on; }

Solution

1. Step 1: Recall nginx event method syntax

   The correct syntax to specify the event method inside the events block is use epoll;.

2. Step 2: Verify other options

   Options like event_method, set_event, or epoll on are not valid nginx directives.

3. Final Answer:

   events { use epoll; } -> Option A

4. Quick Check:

   Correct event method syntax = use epoll; [OK]

Hint: Use 'use' keyword to set event method inside events block [OK]

Common Mistakes:

• Using incorrect directive names like event_method
• Omitting the semicolon after epoll
• Placing event method outside the events block

3. Given this nginx configuration snippet, what will be the effect?

events {
    worker_connections 1024;
    use epoll;
}

medium

A. Nginx will ignore worker_connections and only use epoll

B. Nginx will handle up to 1024 simultaneous connections using epoll event method

C. Nginx will limit connections to 1024 but use the default event method

D. Nginx will throw a syntax error due to wrong event method

Solution

1. Step 1: Analyze worker_connections directive

   The worker_connections 1024; sets the maximum simultaneous connections per worker process to 1024.

2. Step 2: Analyze use epoll directive

   The use epoll; sets the event method to epoll, which is efficient on Linux systems.

3. Final Answer:

   Nginx will handle up to 1024 simultaneous connections using epoll event method -> Option B

4. Quick Check:

   worker_connections + use epoll = Nginx will handle up to 1024 simultaneous connections using epoll event method [OK]

Hint: worker_connections limits connections; use sets event method [OK]

Common Mistakes:

• Assuming default event method is used despite 'use epoll;'
• Thinking worker_connections is ignored
• Believing configuration causes syntax error

4. You have this nginx events block:

events {
    worker_connections 2048
    use kqueue;
}

What is the error and how to fix it?

medium

A. kqueue is not a valid event method; replace with epoll

B. worker_connections value too high; reduce to 1024

C. Missing semicolon after worker_connections; add it

D. use directive must be outside events block

Solution

1. Step 1: Check syntax of worker_connections

   The line worker_connections 2048 is missing a semicolon at the end, which is required.

2. Step 2: Verify event method and directive placement

   kqueue is valid on BSD systems, and use must be inside events block, so no error there.

3. Final Answer:

   Missing semicolon after worker_connections; add it -> Option C

4. Quick Check:

   Semicolon missing = syntax error fixed by adding [OK]

Hint: Always end directives with semicolon inside blocks [OK]

Common Mistakes:

• Thinking kqueue is invalid on all systems
• Ignoring missing semicolon causing syntax error
• Moving use directive outside events block incorrectly

5. You want nginx to efficiently handle many connections on a Linux server. Which configuration snippet best applies event-driven architecture principles?

hard

A. events {
worker_connections 2048;
use kqueue;
}

B. events {
worker_connections 512;
use select;
}

C. events {
worker_connections 1024;
use poll;
}

D. events {
worker_connections 4096;
use epoll;
}

Solution

1. Step 1: Identify best event method for Linux

   On Linux, epoll is the most efficient event method for handling many connections.

2. Step 2: Choose highest worker_connections for capacity

   Setting worker_connections to 4096 allows more simultaneous connections, improving performance.

3. Final Answer:

   events { worker_connections 4096; use epoll; } -> Option D

4. Quick Check:

   Linux + many connections = use epoll + high worker_connections [OK]

Hint: Use epoll with high worker_connections on Linux [OK]

Common Mistakes:

• Using select or poll which are less efficient on Linux
• Choosing low worker_connections limiting connections
• Using kqueue which is for BSD, not Linux