Uvicorn server basics in FastAPI - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when you run Uvicorn with default settings?

You start a FastAPI app using uvicorn main:app without extra options. What is the behavior of the server?

A The server runs on localhost at port 8000 but does not reload automatically on code changes.

B The server runs on all network interfaces at port 80 and reloads automatically on code changes.

C The server runs on localhost at port 8000 and reloads automatically on code changes.

D The server runs on all network interfaces at port 8000 but does not reload automatically.

💡 Hint

Think about the default host, port, and reload behavior of Uvicorn.

By default, Uvicorn runs on 127.0.0.1 (localhost) at port 8000. It does not reload automatically unless the --reload flag is used.

📝 Syntax

intermediate

Which command correctly starts Uvicorn with auto-reload and on all interfaces?

You want to run your FastAPI app with Uvicorn so it reloads on code changes and listens on all network interfaces. Which command is correct?

A uvicorn main:app --reload host=0.0.0.0

B uvicorn main:app --host 0.0.0.0 --reload

C uvicorn main:app --reload --host 0.0.0.0

D uvicorn main:app --host=localhost --reload

💡 Hint

Check the correct syntax for flags and their order.

The correct syntax uses double dashes for flags and spaces between flags and values. Both --reload and --host 0.0.0.0 are valid flags.

❓ state_output

advanced

What is the output when Uvicorn fails to bind to port 80?

You run uvicorn main:app --host 0.0.0.0 --port 80 without root privileges on Linux. What error message or behavior will you see?

A RuntimeError: Port 80 is already in use

B PermissionError: [Errno 13] Permission denied

C SyntaxError: invalid port number

D The server starts successfully on port 80

💡 Hint

Ports below 1024 require special permissions on Unix systems.

On Unix-like systems, binding to ports below 1024 requires root privileges. Without them, Uvicorn raises a PermissionError.

🔧 Debug

advanced

Why does Uvicorn not reload when using --reload with a custom app import path?

You run uvicorn myproject.app:app --reload but changes in your code do not trigger reload. What is the most likely cause?

A The server needs to be restarted manually to enable reload.

B The <code>--reload</code> flag only works with the default <code>main:app</code> import path.

C Uvicorn does not support reload on Windows systems.

D The import path is incorrect or the app is not detected properly.

💡 Hint

Check if the app path matches your project structure exactly.

If the import path is wrong or the app variable is not found, Uvicorn cannot watch files properly and reload won't work.

🧠 Conceptual

expert

How does Uvicorn handle multiple worker processes?

You start Uvicorn with --workers 4. What is true about how Uvicorn manages these workers?

A Uvicorn starts 4 separate processes, each running the app independently to handle requests concurrently.

B Uvicorn runs a single process with 4 threads to handle requests concurrently.

C Uvicorn runs 4 processes but shares the same memory space for app state.

D Uvicorn cannot run multiple workers; the flag is ignored.

💡 Hint

Think about how Python handles concurrency with processes vs threads.

Using --workers starts multiple independent processes. Each process runs its own instance of the app, allowing better CPU utilization.

Practice

1. What is the main purpose of running uvicorn with a FastAPI app?

easy

A. To start a server that handles web requests for the FastAPI app

B. To compile the FastAPI app into an executable file

C. To create a database connection for the FastAPI app

D. To generate API documentation automatically

Solution

1. Step 1: Understand what Uvicorn does

   Uvicorn is an ASGI server that runs your FastAPI app so it can receive and respond to web requests.

2. Step 2: Identify the purpose of running Uvicorn

   Running Uvicorn starts the server that listens for HTTP requests and sends responses from your FastAPI app.

3. Final Answer:

   To start a server that handles web requests for the FastAPI app -> Option A

4. Quick Check:

   Uvicorn runs server = A [OK]

Hint: Remember: Uvicorn runs the server for your app [OK]

Common Mistakes:

• Thinking Uvicorn compiles code
• Confusing server start with database setup
• Assuming Uvicorn generates docs automatically

2. Which of the following is the correct command to run a FastAPI app located in main.py with auto-reload enabled?

easy

A. uvicorn main:app reload

B. uvicorn main:app --reload

C. uvicorn app:main --reload

D. uvicorn main.py --reload

Solution

1. Step 1: Understand Uvicorn command syntax

   The correct syntax is uvicorn module_name:app_variable. Here, the module is main and the app variable is app.

2. Step 2: Check the options for auto-reload

   The option --reload enables auto-reload during development.

3. Final Answer:

   uvicorn main:app --reload -> Option B

4. Quick Check:

   Correct syntax with --reload = D [OK]

Hint: Use module:app format with --reload flag [OK]

Common Mistakes:

• Including .py extension in module name
• Swapping module and app names
• Missing double dashes before reload

3. Given this command: uvicorn app.main:app --host 0.0.0.0 --port 8080, what will be the effect?

medium

A. The app runs on localhost at port 80

B. The app runs only on 127.0.0.1 at port 8080

C. The app runs on all network interfaces at port 8080

D. The app runs on all interfaces at default port 8000

Solution

1. Step 1: Analyze the host option

   The host 0.0.0.0 means the server listens on all network interfaces, not just localhost.

2. Step 2: Analyze the port option

   The port is explicitly set to 8080, so the app will listen on port 8080.

3. Final Answer:

   The app runs on all network interfaces at port 8080 -> Option C

4. Quick Check:

   Host 0.0.0.0 + port 8080 = C [OK]

Hint: 0.0.0.0 means all interfaces, port sets listening port [OK]

Common Mistakes:

• Assuming 0.0.0.0 means localhost only
• Ignoring the port option
• Confusing default port 8000 with specified port

4. You run uvicorn main:app --reload but get an error: ModuleNotFoundError: No module named 'main'. What is the likely cause?

medium

A. The app variable is not named app inside main.py

B. Uvicorn requires Python 2, but you have Python 3

C. The --reload flag is not supported on your system

D. The file main.py is missing or not in the current directory

Solution

1. Step 1: Understand the error message

   The error says the module main cannot be found, meaning Python can't locate main.py.

2. Step 2: Check file location

   If main.py is missing or not in the current directory where the command runs, this error occurs.

3. Final Answer:

   The file main.py is missing or not in the current directory -> Option D

4. Quick Check:

   ModuleNotFoundError means missing file/module = B [OK]

Hint: Check if main.py exists in current folder [OK]

Common Mistakes:

• Assuming app variable name causes ModuleNotFoundError
• Blaming --reload flag for module errors
• Confusing Python version requirements

5. You want to run your FastAPI app with Uvicorn so it reloads on code changes and listens only on localhost at port 5000. Which command is correct?

hard

A. uvicorn app:app --reload --host 127.0.0.1 --port 5000

B. uvicorn app:app --reload --host 0.0.0.0 --port 5000

C. uvicorn app:app --host 127.0.0.1 --port 5000

D. uvicorn app:app --reload --port 127.0.0.1 --host 5000

Solution

1. Step 1: Identify the reload option

   The --reload flag enables auto-reload on code changes, so it must be included.

2. Step 2: Set host and port correctly

   Listening only on localhost means host should be 127.0.0.1. The port must be set to 5000 using --port 5000.

3. Step 3: Check option order and syntax

   Options order does not affect functionality, but the syntax must be correct: --host followed by IP, --port followed by port number.

4. Final Answer:

   uvicorn app:app --reload --host 127.0.0.1 --port 5000 -> Option A

5. Quick Check:

   Reload + localhost + port 5000 = A [OK]

Hint: Use --reload with --host 127.0.0.1 and --port 5000 [OK]

Common Mistakes:

• Using 0.0.0.0 for localhost only
• Swapping host and port values
• Omitting --reload for auto-reload