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
    Demo of the app
    Times asked 8
  2. 2
    Explain the code for export CSV
    Times asked 2
  3. 3
    In notepad write any vue component, wrote basic v-for , than he asked to add relative fetch request for that and backend route for that..(Basically was testing if you know to write a component, route , backend fetch logic correctly)
    Times asked 2
  4. 4
    Also asked to check authentication in route and check for roles, allow only admin to view that route .
    Times asked 2
  5. 5
    Asked to explain caching.
    Times asked 2
Advice: He is very friendly yet professional.. Can ask anything related to your code ..
  1. 1
    Show Repo then collaborator
    Times asked 2
  2. 2
    For commands, I asked him then used readme file.
    Times asked 2
  3. 3
    Search application as admin
    Times asked 2
  4. 4
    Log in as company and Create a drive
    Times asked 2
  5. 5
    Approve the drive
    Times asked 2
  6. 6
    Login/register and Apply as a student
    Times asked 2
  7. 7
    Asked Can i apply twice, then he asked to show the code for it. I had implemented both frontend and backend validation, so I showed both.
    Times asked 1
  8. 8
    Asked about Jwt, but I told him I have used flask-security.
    Times asked 2
  9. 9
    Show mail for admin report, reminder
    Times asked 2
  10. 10
    In notepad - sqlalchemy query for retrieving all the blacklisted students.
    Times asked 1
Advice: He was very Chill. All the questions he asked were already in sheet. Time was 6pm but he joined 6:15 bcoz of something, still he was calm and didn't rush me for anything. Gave me time for doing what he asked, like installing the dependencies and all takes time. I was kind of just notifiying him like backend is running now, redis-server is running... Between these installs, there was complete silence, he didn't ask anything and I was just saying things after completing them or when he asked. Be calm, explain everything confidently. All the Best!!
  1. 1
    Then he asked what I will change if I have to scale it for 1L or 2L users.
    Times asked 2
  2. 2
    Then he asked me to show how a user is created and told to show on code where that logic is implemented.
    Times asked 2
  3. 3
    Then he really appreciated my project and explanations and finished the viva
    Times asked 2
Advice: Really chill proctor, did not interrupt me even once. Prepare your project presentation, and the scaling trade offs. And that's it'
  1. 1
    He will guide you through the entire demo
    Times asked 2
  2. 2
    Then he asked me to explain the celery beat command that I was using to start celery beat
    Times asked 2
  3. 3
    Difference between celery beat and worker? What role does redis play here
    Times asked 1
  4. 4
    Why have you used redis cache? What are the advantages?
    Times asked 1
  5. 5
    Then asked me some questions related to the Vue router
    Times asked 2
  6. 6
    What does timeout mean in @cache.cached(timeout)
    Times asked 2
  7. 7
    Asked me the celery configuration part
    Times asked 2
  8. 8
    CODING PART:
    Times asked 2
  9. 9
    Asked me to write a flask route to fetch all trek names that have been assigned to a staff with a particular name
    Times asked 1
Advice: Know your code really well, he doesn't follow any fixed pattern in questioning. He'll ask you stuff randomly from your code
  1. 1
    I had some issues with setting up the venv. so in the meanwhile he helped me setting up the venv.
    Times asked 2
  2. 2
    He was asking for every particular feature like in the code where have you implemented this. Than asked me to change the colour of the navbar and on the notepad asked me to write a sqlalchemy query. after that he said be ready for level-2
    Times asked 2
Advice: Know your codebase very well. because he can ask you to explain or show any part of the code of his choice. else He was chill and supportive.
  1. 1
    Show id
    Times asked 3
  2. 2
    Install and do the setup
    Times asked 2
  3. 3
    Opened worker and 3 lines in that describe it
    Times asked 2
  4. 4
    Composition api and optional ai
    Times asked 2
  5. 5
    If students cgpa is not greater than 7.5 disabled him to apply for job ( which i didn't) Mixed mood of proctor Thankyou
    Times asked 2
Advice: See the javascript code a little bit and enjoy I asked him for passed or failed he said he can't disclose that.
  1. 1
    He asked for demo (He himself told me the flow , like login as company , then approve as admin , ...)
    Times asked 2
  2. 2
    Have you used jwt?
    Times asked 1
  3. 3
    Then he asked me to show the code for sending the approval mail (after a company is successfully approved by admin)
    Times asked 2
  4. 4
    Then he asked many pieces of code like where is this , that etc...
    Times asked 2
  5. 5
    Then he asked me ports like what is 400, 401 , 200 , 403 etc....
    Times asked 2
  6. 6
    Then he asked me to show the sent mail( he also approves if you show him already sent mails that you've tested and you can show that from your inbox)
    Times asked 2
  7. 7
    Have you used ai ( I coded the blueprint and routes myself and used ai to refine the code and generate the messages to be send in the mail) and he said ok
    Times asked 2
  8. 8
    He asked me to code celery scheduler...i did'nt know so he asked...(you said you coded yourself , then why not this ? I told..if you'd allow me to verify celery documentation , I'll brush up the syntax and code it- Then he said not necessary)
    Times asked 1
  9. 9
    He asked me to code the route to display all unapproved drives
    Times asked 2
  10. 10
    Then he asked me to change the color and size of a button
    Times asked 2
  11. 11
    Finaly he asked...
    Times asked 2
Advice: He was very nonchalant , he will ask a question and won't ask any cross question until you answer it or directly tell him you don't know... Viva was exactly for 30 minutes One thing that can impress him is , whatever functionality he asks , know where that part of code is , in your project . He won't talk much , but he is not very strict too.... The coding questions are repeated . So make sure to go through the spreadsheet..Btw mine was level 1 He is very patient and waits for you to search your file . Just don't stay silent
  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!
Created for educational purposes only. Questions are based on students' personal experiences and may not reflect actual exam content.