Demonstrate all Admin, User/Student, and Company functionalities.
9
Show the search functionality.
10
Explain the booking/appointment logic.
11
Explain how the booking cost is calculated.
12
Test edge cases (e.g., booking two appointments at the same time).
13
Show database models.
14
Explain models.py.
15
Explain the User model.
16
Explain backref.
17
Is the Admin user created automatically when the database is initialized?
18
What is Cascade in DBMS?
19
Explain a solution if duplicate applications should later be allowed despite a unique constraint.
20
What is ORM?
21
Why is ORM used? What are its advantages?
22
What is a Virtual Environment (venv)? Why do we use it?
23
What frontend and backend frameworks have you used?
24
Difference between frontend validation and backend validation (with examples).
25
Explain all HTTP request methods.
26
Difference between PUT and PATCH.
27
How do CRUD operations map to REST APIs?
28
What security features have you implemented?
29
What additional security measures would you add?
30
How would you improve SQL/database security?
31
Add a column showing the total appointments handled by each doctor (excluding cancelled appointments).
32
Display the total number of applications submitted by a student.
33
Disable the Apply button after a student has already applied.
34
Display the student's name and department on the Student Dashboard.
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
Suggest an additional template/page showing details of the user booking a parking slot.
37
Answer hypothetical scenarios based on your application design and implementation.