Bird
Raised Fist0
Nginxdevops~10 mins

Index directive in Nginx - Interactive Code Practice

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to set the default index file to index.html.

Nginx
index [1];
Drag options to blanks, or click blank then click option'
Adefault.html
Bindex.html
Chome.html
Dmain.html
Attempts:
3 left
💡 Hint
Common Mistakes
Using a file name that is not commonly used as an index file.
Forgetting the semicolon at the end.
2fill in blank
medium

Complete the code to set multiple index files: index.php and index.html.

Nginx
index [1] [2];
Drag options to blanks, or click blank then click option'
Aindex.php
Bindex.html
Cdefault.php
Dhome.html
Attempts:
3 left
💡 Hint
Common Mistakes
Using incorrect file names.
Not separating file names with spaces.
3fill in blank
hard

Fix the error in the code to correctly set the index file to home.html.

Nginx
index [1];
Drag options to blanks, or click blank then click option'
Ahome.htm
Bhome.html
Chome.htm;
Dhome.html;
Attempts:
3 left
💡 Hint
Common Mistakes
Omitting the semicolon at the end.
Using wrong file extension.
4fill in blank
hard

Fill both blanks to set the index files to default.html and index.htm.

Nginx
index [1] [2];
Drag options to blanks, or click blank then click option'
Adefault.html
Bindex.html
Cindex.htm
Dhome.html
Attempts:
3 left
💡 Hint
Common Mistakes
Mixing up file names or extensions.
Forgetting the semicolon at the end.
5fill in blank
hard

Fill all three blanks to set the index files to main.php, index.html, and default.htm.

Nginx
index [1] [2] [3];
Drag options to blanks, or click blank then click option'
Amain.php
Bindex.html
Cdefault.htm
Dhome.html
Attempts:
3 left
💡 Hint
Common Mistakes
Incorrect file order.
Using wrong file extensions.
Missing semicolon.

Practice

(1/5)
1.

What is the main purpose of the index directive in nginx?

easy
A. To specify default files to serve when a directory is requested
B. To set the server's IP address
C. To configure SSL certificates
D. To define error pages

Solution

  1. Step 1: Understand the role of the index directive

    The index directive tells nginx which files to look for by default when a user requests a directory URL.
  2. Step 2: Match the purpose with the options

    Only To specify default files to serve when a directory is requested describes setting default files to serve in a folder, which matches the index directive's function.
  3. Final Answer:

    To specify default files to serve when a directory is requested -> Option A
  4. Quick Check:

    index directive = default files [OK]
Hint: Index sets default homepage files for folders [OK]
Common Mistakes:
  • Confusing index with server IP settings
  • Thinking index sets error pages
  • Mixing index with SSL configuration
2.

Which of the following is the correct syntax to set index.html and home.html as default files using the index directive?

?
easy
A. index: index.html; home.html;
B. index = index.html, home.html;
C. index { index.html home.html }
D. index index.html home.html;

Solution

  1. Step 1: Recall nginx index directive syntax

    The correct syntax lists files separated by spaces, ending with a semicolon.
  2. Step 2: Compare options with correct syntax

    index index.html home.html; matches the correct syntax: index index.html home.html;. Others use invalid punctuation or braces.
  3. Final Answer:

    index index.html home.html; -> Option D
  4. Quick Check:

    Correct syntax = index index.html home.html; [OK]
Hint: List files with spaces, end with semicolon [OK]
Common Mistakes:
  • Using commas between filenames
  • Using braces or colons incorrectly
  • Adding equal signs in directive
3.

Given this nginx config snippet:

location / {
    index about.html index.html;
}

If the folder contains index.html but not about.html, which file will nginx serve when a user visits /?

medium
A. 404 Not Found error
B. about.html
C. index.html
D. Directory listing

Solution

  1. Step 1: Understand index file priority

    nginx tries files in order: first about.html, then index.html.
  2. Step 2: Check which files exist

    about.html is missing, but index.html exists, so nginx serves index.html.
  3. Final Answer:

    index.html -> Option C
  4. Quick Check:

    First found file served = index.html [OK]
Hint: nginx serves first existing file in index list [OK]
Common Mistakes:
  • Assuming nginx serves first listed file regardless of existence
  • Expecting directory listing if first file missing
  • Thinking nginx returns error immediately
4.

Identify the error in this nginx config snippet:

location / {
    index index.html, home.html;
}
medium
A. Missing semicolon at the end
B. Using a comma between filenames is invalid syntax
C. index directive cannot be used inside location block
D. File names must be in quotes

Solution

  1. Step 1: Check syntax for index directive

    File names must be separated by spaces, not commas.
  2. Step 2: Identify the error in the snippet

    The comma between index.html and home.html is invalid syntax.
  3. Final Answer:

    Using a comma between filenames is invalid syntax -> Option B
  4. Quick Check:

    No commas allowed in index list [OK]
Hint: Separate files with spaces, no commas [OK]
Common Mistakes:
  • Adding commas between filenames
  • Omitting semicolon
  • Thinking quotes are required
5.

You want nginx to serve main.html as the default file, but only if index.html is missing. Which index directive correctly achieves this?

hard
A. index index.html main.html;
B. index main.html index.html;
C. index main.html;
D. index index.html;

Solution

  1. Step 1: Understand index file priority order

    nginx serves the first existing file in the list from left to right.
  2. Step 2: Choose order to serve main.html only if index.html missing

    To serve main.html only if index.html is missing, index.html must be first, then main.html.
  3. Final Answer:

    index index.html main.html; -> Option A
  4. Quick Check:

    First existing file served = index.html then main.html [OK]
Hint: List index.html first to prefer it over main.html [OK]
Common Mistakes:
  • Reversing file order
  • Listing only one file
  • Expecting nginx to skip files in order