Viva prep · Real questions · Student experiences Enroll in Bootcamp

Search viva questions

Search by question text across the whole library — then narrow with subject, level, or proctor.

Question sets

  1. 1
    1)Asked to run the project in the portal
    Times asked 2
  2. 2
    Asked to explain the front-end file
    Times asked 2
  3. 3
    Asked to write the api roots where trekkers booking regarding
    Times asked 2
  4. 4
    Asked to explain database columns
    Times asked 2
  5. 5
    Asked that have u stopped the trekkers count for booking it
    Times asked 2
  6. 6
    Asked to explain models
    Times asked 1
  7. 7
    Asked csl or CdS which one u have used
    Times asked 2
  8. 8
    Asked to explain the users dashboard in the admin dashboard
    Times asked 2
  9. 9
    Asked how much ai percentage have u used in particular in front-end, backend etc
    Times asked 2
Advice: Go through Overall of your code
  1. 1
    HE asked for the demo
    Times asked 2
  2. 2
    Then told me to write a route to connect the frontend and the backend
    Times asked 2
  3. 3
    Asked me where I have created a specific functionality,
    Times asked 2
  4. 4
    Asked 1 2 thoery questions very easy
    Times asked 2
  5. 5
    Said to leave
    Times asked 2
  6. 6
    He was in a hurry just know your code and functionalities he is just checking if youuu know your own code
    Times asked 2
Advice: Chill proctor just know your code
  1. 1
    How the viva started
    Times asked 1
  2. 2
    There was no project demo in my case. The examiner directly started asking questions from my codebase. He went through the project line by line and asked why I had written certain things, what they do, and whether I had actually implemented those features.
    Times asked 2
  3. 3
    Types of questions I was asked
    Times asked 1
  4. 4
    Some of the questions I remember are:
    Times asked 2
  5. 5
    Explain router.js.
    Times asked 2
  6. 6
    Write a database query to fetch all treks belonging to a particular manager.
    Times asked 2
  7. 7
    What are computed properties and watchers in Vue?
    Times asked 1
  8. 8
    Why did you use :class (colon before class)? What is its purpose?
    Times asked 1
  9. 9
    There were many more questions, but these are the ones I remember.
    Times asked 1
  10. 10
    My experience
    Times asked 2
  11. 11
    Some questions I answered well, some only partially, and a few I couldn't answer. I didn't try to bluff or make things up. Whenever I genuinely didn't know something, I told him honestly.
    Times asked 2
  12. 12
    At one point, he gave feedback saying that my answers were okay-ish, but I should understand my own code much better. He specifically said that using AI is not an excuse for not being able to explain or write the code yourself. If you've used AI to build something, you should still understand every part of it.
    Times asked 2
  13. 13
    That honestly made me feel much better.
    Times asked 2
  14. 14
    Biggest lesson
    Times asked 2
  15. 15
    Know every single line of your own code.
    Times asked 2
  16. 16
    If you've imported a library:
    Times asked 2
  17. 17
    Why did you import it?
    Times asked 1
  18. 18
    What problem does it solve?
    Times asked 2
  19. 19
    Could you have done it another way?
    Times asked 2
  20. 20
    If you've used a function:
    Times asked 2
  21. 21
    What does it return?
    Times asked 2
  22. 22
    Why is it needed?
    Times asked 2
  23. 23
    What happens if you remove it?
    Times asked 2
  24. 24
    If you've copied something from documentation or AI:
    Times asked 2
  25. 25
    Read it.
    Times asked 2
  26. 26
    Be able to write it again without looking.
    Times asked 2
  27. 27
    The examiner doesn't care whether the project works. He wants to know whether you understand what you've written.
    Times asked 2
Advice: My advice for everyone Go through your project line by line. Understand every import, configuration, and dependency. Be able to write important snippets (like router configuration or common database queries) without looking. Learn the concepts behind whatever you've used (JWT, Vue Router, computed, watch, Axios, Pinia, SQLAlchemy, etc.). If you haven't implemented a feature, be honest. Don't try to fake it. Revise common Vue concepts like props, emits, computed, watch, routing, conditional rendering, lifecycle hooks, and API calls. Revise backend concepts like JWT authentication, database relationships, SQLAlchemy queries, and why each package is used. Final takeaway The viva is less about whether your project runs and more about whether you truly understand your project. If you know your own code well, you'll do much better than someone who simply copied everything and hoped it wouldn't be asked. That's all from my side. I hope this helps. Best of luck to everyone appearing for the viva—you've got this!
  1. 1
    Which Vue version ae you using
    Times asked 2
  2. 2
    Difference between vue CLI and Vue CDN and which one are you using.
    Times asked 2
  3. 3
    What is Vue router and where have you used it in your code.
    Times asked 1
  4. 4
    What is ORM?
    Times asked 49
  5. 5
    What is Blueprint and where have you used it.
    Times asked 2
  6. 6
    Where have you implemented caching.
    Times asked 2
  7. 7
    Write a route to show the list of blacklisted companies. Also write frontend code for the same.
    Times asked 2
Advice: Know everything about your code. He can ask from anywhere.
  1. 1
    Similar to the other responses here, seems like he follows a rigid format
    Times asked 2
  2. 2
    - Asked me for a demo of the application
    Times asked 4
  3. 3
    - Did NOT let me open the code for some reason
    Times asked 2
  4. 4
    - Asked me to write Python code to fetch all students in notepad
    Times asked 2
  5. 5
    - Asked me where JWT is stored
    Times asked 2
  6. 6
    - Asked me what are lifecycle hooks in Vue
    Times asked 2
Advice: Didn't feel very friendly, his mic quality was very bad. I had to ask him to repeat his questions multiple times. But his format is rigid, just study the responses given in the sheet and you'll do well.
  1. 1
    - Show ID
    Times asked 3
  2. 2
    - Show GitHub Repo
    Times asked 1
  3. 3
    - Detailed codes
    Times asked 2
  4. 4
    - questions, files, show api,
    Times asked 2
  5. 5
    - write all the vue codes you know or used in notepad.
    Times asked 2
  6. 6
    - Explain your codes, all modules from the start,
    Times asked 2
  7. 7
    - explain each functions that are being used.
    Times asked 2
  8. 8
    Some personal questions,
    Times asked 2
  9. 9
    - like what I'm doing currently and
    Times asked 2
  10. 10
    - where I see myself in 5 years.
    Times asked 2
  11. 11
    - grades in every other project
    Times asked 2
  12. 12
    Didn't let me show the application, or explain it.
    Times asked 2
Advice: Be confident, Know your codes, know your file and know basic coding
  1. 1
    Can a drive be edited after it has been created?
    Times asked 2
  2. 2
    What are HTTP status/error codes? like 201, 403 etc.
    Times asked 2
  3. 3
    Remove Actions column from the Registered Companies table in the Admin Dashboard frontend.
    Times asked 2
  4. 4
    Show the scheduler code.
    Times asked 2
  5. 5
    Something related to email sender functionality.
    Times asked 2
  6. 6
    Can companies change the status of student applications?
    Times asked 2
  7. 7
    How do you ensure that a student can apply to a drive only once?
    Times asked 2
  8. 8
    Write a new route to list all blacklisted companies.
    Times asked 2
Advice: Just be chill because he is chill too.
  1. 1
    Level1_viva18 Super chill, waited patiently for my demo to work - legit took 15 minutes coz of my lazy laptop
    Times asked 2
  2. 2
    Project demonstration
    Times asked 6
  3. 3
    Backend jobs what and where have you implemented them
    Times asked 2
  4. 4
    Write an api to fetch all the blacklisted companies
    Times asked 2
  5. 5
    Vue CDN and CLI differences and what have I used
    Times asked 2
  6. 6
    Vue lifecycle methods and where have i implemented it in the code
    Times asked 2
  7. 7
    Show how mails are received when a student gets deactivated Super chill, let's you do your thing and doesn't interrupt anywhere
    Times asked 2
Advice: Don't panic much, he won't eat you or anything Stay calm and patiently run your demo even if it takes time
  1. 1
    TREK-APP
    Times asked 2
  2. 2
    First he asked me show the appa and complete demo
    Times asked 2
  3. 3
    vue-router and show where its used
    Times asked 2
  4. 4
    blueprints in flask (i havent used and didnt know abt them)
    Times asked 2
  5. 5
    Choding qn:
    Times asked 2
  6. 6
    Make an endpoint to list all the deactivated or blacklisted staff members in the admin dashboard.
    Times asked 2
  7. 7
    wasnt able to completely implement it
    Times asked 2
  8. 8
    but i explained everything and he said its ok
    Times asked 2
  9. 9
    i felt hes kind
    Times asked 2
  10. 10
    props in vue
    Times asked 2
Advice: IF U GET SAME vivataker do this qn!!!! Make an endpoint to list all the deactivated or blacklisted staff members in the admin dashboard. Stay confiden I hope i pass lvl1 viva
  1. 1
    My project name is Trekking Management App.
    Times asked 2
  2. 2
    He tell me to show the idcard, then git collaborator and download the project and start the demo.
    Times asked 2
  3. 3
    In mid of the demo he asked me to show the search functionality and monthly report(admin dashboard).
    Times asked 2
  4. 4
    Tell me open the notepad and write the api code to show the list of blacklisted users.
    Times asked 2
  5. 5
    Tell me to show the models.py and asked what is uselist and lazy.
    Times asked 1
  6. 6
    Vue life cycle hooks and where u have implemented them.
    Times asked 2
  7. 7
    Explain the http methods
    Times asked 2
  8. 8
    Then tell me to continue the demo and i was in half of the demo and then he asked me have u used schedule tasks and tell me to give demo of that.
    Times asked 2
  9. 9
    Then he said that this is enough for level 1 viva .
    Times asked 2
Advice: He is calm, listen to u patiently and give time also for explaining and moreover u just have to go through to your code carefully and stay calm.
Maintaine By Lazy IITians Team + IITM BS students Regualr for More data you have