Viva prep · Real questions · Student experiences Enroll in Bootcamp

Proctor level1_viva14

All approved submissions for this examiner code.

level1_viva14 MAD1 Level 1 Jul 31, 2026
  1. 1
    Show your GitHub repository.
  2. 2
    Verify GitHub collaborator access.
  3. 3
    Show the AI/LLM usage percentage.
  4. 4
    Download the project from the Viva Portal.
  5. 5
    Run the application.
  6. 6
    Demonstrate the complete application.
  7. 7
    Perform all CRUD operations.
  8. 8
    Demonstrate all Admin, User/Student, and Company functionalities.
  9. 9
    Show the search functionality.
  10. 10
    Explain the booking/appointment logic.
  11. 11
    Explain how the booking cost is calculated.
  12. 12
    Test edge cases (e.g., booking two appointments at the same time).
  13. 13
    Show database models.
  14. 14
    Explain models.py.
  15. 15
    Explain the User model.
  16. 16
    Explain backref.
  17. 17
    Is the Admin user created automatically when the database is initialized?
  18. 18
    What is Cascade in DBMS?
  19. 19
    Explain a solution if duplicate applications should later be allowed despite a unique constraint.
  20. 20
    What is ORM?
  21. 21
    Why is ORM used? What are its advantages?
  22. 22
    What is a Virtual Environment (venv)? Why do we use it?
  23. 23
    What frontend and backend frameworks have you used?
  24. 24
    Difference between frontend validation and backend validation (with examples).
  25. 25
    Explain all HTTP request methods.
  26. 26
    Difference between PUT and PATCH.
  27. 27
    How do CRUD operations map to REST APIs?
  28. 28
    What security features have you implemented?
  29. 29
    What additional security measures would you add?
  30. 30
    How would you improve SQL/database security?
  31. 31
    Add a column showing the total appointments handled by each doctor (excluding cancelled appointments).
  32. 32
    Display the total number of applications submitted by a student.
  33. 33
    Disable the Apply button after a student has already applied.
  34. 34
    Display the student's name and department on the Student Dashboard.
  35. 35
    Create a profile box on the Student Dashboard that: Redirects to the profile page. Appears at a specified location. Dynamically displays the student's name. Uses a specific color.
  36. 36
    Suggest an additional template/page showing details of the user booking a parking slot.
  37. 37
    Answer hypothetical scenarios based on your application design and implementation.
Created for educational purposes only. Questions are based on students' personal experiences and may not reflect actual exam content.