File upload handling basics in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when a file is uploaded using Django's default FileField?

Consider a Django model with a FileField. When a user uploads a file through a form linked to this model, what is the default behavior regarding the file storage?

Django

class Document(models.Model):
    upload = models.FileField(upload_to='uploads/')

A The file is uploaded but not saved anywhere unless manually handled in the view.

B The file is stored directly in the database as binary data.

C The file is saved in a temporary folder and deleted after the request finishes.

D The file is saved to the directory specified by <code>upload_to</code> inside the <code>MEDIA_ROOT</code> folder.

💡 Hint

Think about where Django stores uploaded files by default when using FileField.

Django saves uploaded files to the filesystem under the MEDIA_ROOT directory combined with the upload_to path. It does not store files in the database or temporary folders by default.

📝 Syntax

intermediate

Identify the correct way to handle file upload in a Django view

Which of the following Django view snippets correctly handles a file upload from a form?

Django

def upload_file(request):
    if request.method == 'POST':
        form = UploadForm(request.POST, request.FILES)
        if form.is_valid():
            # What should happen here?
            pass
    else:
        form = UploadForm()
    return render(request, 'upload.html', {'form': form})

A file = request.FILES['file']; instance = Document(); instance.upload = file; instance.save()

B file = request.POST['file']; instance = Document(upload=file); instance.save()

C file = request.FILES.get('file'); instance = Document(); instance.upload = file; instance.save()

D file = request.FILES['file']; instance = Document(upload=file); instance.save()

💡 Hint

Remember that uploaded files are in request.FILES and you can assign them to model fields before saving.

Uploaded files are accessed via request.FILES. You create a model instance, assign the file to the FileField, then save the instance. Option A correctly does this.

🔧 Debug

advanced

Why does this Django file upload view raise a MultiValueDictKeyError?

Examine the following Django view code snippet. It raises a MultiValueDictKeyError when no file is uploaded. Why?

Django

def upload_file(request):
    if request.method == 'POST':
        file = request.FILES['file']
        instance = Document(upload=file)
        instance.save()
    return render(request, 'upload.html')

A Because <code>request.FILES['file']</code> assumes the file key always exists, but it may be missing if no file is uploaded.

B Because the <code>Document</code> model does not have a <code>FileField</code> named <code>upload</code>.

C Because the view does not check if the request method is GET before accessing <code>request.FILES</code>.

D Because the file is too large and Django rejects it silently.

💡 Hint

Think about what happens if the form is submitted without a file.

Accessing request.FILES['file'] directly causes a MultiValueDictKeyError if the key 'file' is missing. Using request.FILES.get('file') or checking if the key exists avoids this error.

❓ state_output

advanced

What is the value of the model field after saving a file upload?

Given this Django model and view, what will be the value of instance.upload.name after saving a file named example.txt?

Django

class Document(models.Model):
    upload = models.FileField(upload_to='docs/')

def upload_file(request):
    if request.method == 'POST':
        file = request.FILES['file']
        instance = Document(upload=file)
        instance.save()
        return instance.upload.name

A example.txt

B docs/example.txt

C MEDIA_ROOT/docs/example.txt

D /docs/example.txt

💡 Hint

Remember that upload_to sets a folder path relative to MEDIA_ROOT.

The upload.name property returns the relative path including the upload_to folder and the filename. It does not include MEDIA_ROOT or a leading slash.

🧠 Conceptual

expert

Why is it important to use request.FILES instead of request.POST for file uploads in Django?

When handling file uploads in Django, why must you access uploaded files via request.FILES instead of request.POST?

A <code>request.FILES</code> is only used for images, while <code>request.POST</code> handles other file types.

B <code>request.POST</code> contains file data but in a compressed format that needs decoding.

C <code>request.FILES</code> contains file data as <code>UploadedFile</code> objects, while <code>request.POST</code> only contains text data from the form fields.

D <code>request.POST</code> is deprecated and should never be used.

💡 Hint

Think about how browsers send files in forms and how Django separates data.

Files uploaded via forms are sent in a separate part of the request and are accessible in Django through request.FILES as UploadedFile objects. request.POST only contains text data from form fields.