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
    Very sweet proctor
    Times asked 2
  2. 2
    - Show github collaborators
    Times asked 2
  3. 3
    - Demo of project (i gave quick demo in 5-7 mins)
    Times asked 2
  4. 4
    - He gave me a task: Create a button in student dashboard page which shows current student id logged in and clicking it redirects to student history page.
    Times asked 2
  5. 5
    - I took 10 mins for this task, was navigating everywhere console, thunder client to find the error, later found out that i had not used .first() while querying student object, after adding that task was completed.
    Times asked 2
  6. 6
    - He was impressed by my determination to complete that task and praised me.
    Times asked 2
  7. 7
    - Viva over after this one task.
    Times asked 2
Advice: I dont have much tips, maybe it was just my lucky day. I gave demo very quickly and just straight away became ready for his questions. He gave me task, i explained each and every line as i typed and my overall approach For error debugging too, i tried everywhere console.log(data), sending request through thunder client, so maybe he was impressed by all these.
  1. 1
    my proctor was 30 mins late
    Times asked 2
  2. 2
    he arrived at 2:32, said do OPPE setup, i was facing some issues with echoing so i wasted 5 more mins in "debugging" that
    Times asked 2
  3. 3
    He said you can download the project
    Times asked 2
  4. 4
    Then as I was going through my admin page, admin can see student's resume
    Times asked 2
  5. 5
    so he stopped me and asked, how is admin able to see this resume?
    Times asked 2
  6. 6
    I explained a lil bit
    Times asked 2
  7. 7
    He then asked, "show me the code" i was dying inside, but managed to search through file and go to that functionality, explaiin it a lil bit confidently
    Times asked 2
  8. 8
    then he asked me "instead of drive link, add another link"
    Times asked 2
  9. 9
    i added, and it showed my home page ☠️ he asked why ?
    Times asked 2
  10. 10
    I said "good question sir let's try to debug it"
    Times asked 2
  11. 11
    and then i added a doc link, and it showed doc api,
    Times asked 2
  12. 12
    So i explained it handled google apps properly
    Times asked 2
  13. 13
    then he said, okay moving ahead
    Times asked 2
  14. 14
    Then as i was showing my demo
    Times asked 2
  15. 15
    He stopped me and asked, how much AI have you used ?
    Times asked 2
  16. 16
    Then i said "i am using it to beautify my mail, let me show you"
    Times asked 2
  17. 17
    He said not in dashboard, it looks like your project is heavily relied on AI
    Times asked 2
  18. 18
    He said open the AI you used, and show me history ☠️☠️☠️🙏🏻
    Times asked 2
  19. 19
    i used gemini nd claude, so i showed chatgpt instead
    Times asked 2
  20. 20
    And he said, not recent history, old history.
    Times asked 2
  21. 21
    So, i asked is there any way to search ? he said "i don't know"
    Times asked 2
  22. 22
    he asked what is : in :href ? i said it's v-bind
    Times asked 2
  23. 23
    he asked diff b/w v-bind and v-model
    Times asked 2
  24. 24
    okay leave it, write a code
    Times asked 2
  25. 25
    Then he gave me this problem:
    Times asked 2
  26. 26
    write a component which will have an input (date) submit button when user clicks on submit button, api is sent to server, this api sends back all drives whose deadline is from that date till today should be visible, fetch on console
    Times asked 2
  27. 27
    I took 10-12 mins to wrte this code he didn't interrupt, in the end when i was done
    Times asked 2
  28. 28
    He HELPED me write my code better, then said okay leena we're done
    Times asked 2
  29. 29
    Then I asked his feedback, and he said "your understanding is extremely well for coding, but it looks like your code is not written by you, maybe i am wrong, but it gives me that vibe"
    Times asked 2
  30. 30
    Then i deflected the subject and asked how can i improve, can i show this in CV, do you think we should not use AI at all, (he said he uses AI daily when working, but advised me to rely less on it)
    Times asked 2
  31. 31
    We talked about 10-12 mins, and then he left
    Times asked 2
  32. 32
    He is not rude, just maintains the tension and pressure, and can ASK ANYTHING from your code. if you don't know your exact code/function he will know you're faking it.
    Times asked 2
  33. 33
    from 2:32-3:3:18 PM
    Times asked 2
Advice: Strictest proctor i've ever met. Know all your functions/code. he can ask anything in theory. But his coding questions remain similar. all the best.
  1. 1
    HTML template coding question to move a div to different location and change its formatting.
    Times asked 2
  2. 2
    Reasoning for my frontend design. - all dashboards using onMounted hook.
    Times asked 2
  3. 3
    Parent - Child Vue Components relation usage and explain with example from the project code.
    Times asked 2
  4. 4
    Difference between Server client vs distributed networks.
    Times asked 1
Advice: Know your code. They go deep into the code and ask for explanations and reasoning.
  1. 1
    1)to eplain the project all functions
    Times asked 2
  2. 2
    2)checked all functionalities(and flow mentioned in the milestones) again
    Times asked 2
  3. 3
    3)asked quetion based on the projects like:
    Times asked 2
  4. 4
    ->how do i show a list of students(he wants to know about how i used for loops if iam passing a list of student objects etc for html/jinja- asked me to show it in a notepad)
    Times asked 2
  5. 5
    ->asked to write some codes if template-he chooses it randomly i guess,for me it was how arguments are passed how its inutted etc
    Times asked 2
Advice: be through with you project especially the variables used and how they are passed etc the examiner is chill(even though he asks a lot of questions)
  1. 1
    Then asked to give a demo of all the functionalities.
    Times asked 2
  2. 2
    Authentication and authorisation based
    Times asked 2
  3. 3
    (Session or token) Then asked what is token based
    Times asked 2
Advice: He is very chill and nice but be thorough with your code line by line be it frontend or backend.
  1. 1
    This person mainly focuses on code changes and backend jobs. If you know your stuff, it'll be alright.
    Times asked 2
  2. 2
    Theory:
    Times asked 8
  3. 3
    - One way binding vs. Two way binding
    Times asked 2
  4. 4
    - And more but only questions already in the sheet.
    Times asked 2
  5. 5
    Start
    Times asked 2
  6. 6
    Camera Setup Check
    Times asked 2
  7. 7
    Screen Share
    Times asked 2
  8. 8
    ID Verification
    Times asked 3
  9. 9
    Download from Portal and Run
    Times asked 2
  10. 10
    Demo of App
    Times asked 4
  11. 11
    GitHub Repository
    Times asked 2
  12. 12
    End
    Times asked 3
  13. 13
    Good luck! 🤞🏼
    Times asked 2
Advice: OPPE Setup! (Very Important) Be ready to run all batch jobs (Celery worker, Celery beat, Both Backend and Frontend) as soon as possible. You can copy paste `venv` and `node_modules`. For some reason, there's no info about them before this. So... Hope this helps somewhat! Rumours day that he's Shri Krishna Pandey Sir (POD). I can't confirm that 🫪
  1. 1
    *how will u make it production ready
    Times asked 2
  2. 2
    *how did u test this application
    Times asked 2
  3. 3
    *wht will u do to handel 10000 users
    Times asked 1
Advice: explain the demo properly very nice proctor in demo explain the code and the application simultaniusly 30 min of demo
  1. 1
    GitHub (checked both number of commits and collaborators)
    Times asked 2
  2. 2
    What is Vue lifecycle hook
    Times asked 1
  3. 3
    Are you generating monthly reports? (I showed him the frontend but my beat wasn't working so I told him that and he said to fix it before level 2)
    Times asked 1
Advice: Nice proctor. Passed me. Just be calm and explain your code and app well.
  1. 1
    Show ID
    Times asked 6
  2. 2
    What problems you faced while working on this application?
    Times asked 2
  3. 3
    If you had to deploy this app for over 10000 users how would you scale it?
    Times asked 1
  4. 4
    How did you handle the errors while making the app?
    Times asked 2
Advice: Very nice proctor. Just be confident with your answers and know your app well. You are good to go.
  1. 1
    - Showcase project.
    Times asked 2
  2. 2
    - Make only the appointments of treated patients appear in all appointments for doctor.
    Times asked 2
  3. 3
    - Show GitHub page.
    Times asked 2
Advice: Make sure your entire project is working.
Created for educational purposes only. Questions are based on students' personal experiences and may not reflect actual exam content.