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
    LEVEL 2 VIVA
    Times asked 3
  2. 2
    Introduce yourself, show your ID, and share your GitHub profile.
    Times asked 2
  3. 3
    Download the app from the portal and start the setup. While doing the setup, she will ask questions like, "Why use a venv?" or "What is this and what is that?"
    Times asked 2
  4. 4
    Give a demo of your app. (While you give the demo, she will also ask questions about what you are showing, such as frontend vs. backend validation. You can expect at least one question from every section you present.)
    Times asked 2
  5. 5
    Explain the backend structure of your app. Inside this section, she will ask many questions (e.g., "What is Celery/Redis?", "What is a Beat vs. a Worker?", "Where are you configuring this or that?", "What authentication are you using?", "Where is it configured?", and "How does the data flow?" ).
    Times asked 2
  6. 6
    Explain the frontend structure of your app (components, store, views, and the router). She will ask tons of questions here about how data flows, what is happening, what props and emits are, and how you are sending and receiving data. You will have to physically show this in the code Or even ask explain the whole file from top to bottom it could be from view or from component. 6.Code change task: Add a button to the admin page navbar. When the admin clicks it, open a page showing a bookings table with the username, trek name, and booking status.
    Times asked 1
Advice: You have to know your code thoroughly because she will ask questions from everywhere. If you know your code very well, her questions won't bother you. The question level is easy to moderate, though some are hard. She is an interactive, kind, and cool person. If you make a mistake, she will guide you too. All you have to do is be able to explain all of your code. Her main focus is to see your understanding and test it. All the best! 🤞
  1. 1
    Show id, GitHub collaborator, and commits
    Times asked 2
  2. 2
    Demo of project
    Times asked 2
  3. 3
    “tell me about caching”
    Times asked 2
  4. 4
    Asked about CLI and CDN
    Times asked 2
  5. 5
    What is celery worker
    Times asked 1
  6. 6
    Open a notepad and write a route for login
    Times asked 2
  7. 7
    —in this he asked me what if the user gives empty values to email and password
    Times asked 2
  8. 8
    — fronted backend validation? Which can be easily bypassed?
    Times asked 2
  9. 9
    — if front end validation was easily bypassed and empty values are given how will you handle?
    Times asked 2
  10. 10
    Vue code to get info from user and call api for login
    Times asked 2
Advice: He was not very responsive, he was too silent for so long. Maybe when he asks to write code, finish writing and Inform him you finished. Gives a little feedback at the end. However I messed up mine.
  1. 1
    Proctor: level2_141 (level 1)
    Times asked 2
  2. 2
    Show GitHub and ID
    Times asked 2
  3. 3
    Download the code / do a checksum
    Times asked 2
  4. 4
    Show specific functions — create trek, register user, book a trek
    Times asked 2
  5. 5
    Show the monthly report and download the CSV
    Times asked 2
  6. 6
    Show the APIs
    Times asked 2
  7. 7
    Show a Celery task executing (e.g. mail sending)
    Times asked 2
  8. 8
    What is async / what does await do
    Times asked 2
  9. 9
    Explain fetch and mounted
    Times asked 2
  10. 10
    What is JWT (and where it's stored)
    Times asked 1
  11. 11
    Write a signup route in notepad
    Times asked 1
Advice: He's chill and gives you time. Questions are similar to the sheet, so practice those. Stay relaxed and be confident about your code.
  1. 1
    Vue lifecyclehooks
    Times asked 2
  2. 2
    library used for jwt authentication
    Times asked 2
  3. 3
    have u implemented search functionality
    Times asked 2
  4. 4
    Caching
    Times asked 4
Advice: Don't be nervous. Proctor is supportive
  1. 1
    He joined a little late around 12:06 AM and asked me the following questions:
    Times asked 2
  2. 2
    i didn't had a js script which would be used to check on phone number length so he asked how u will code it, just tell me verbally so that i can get ur understanding.
    Times asked 2
  3. 3
    he also asked several celery and redis questions which is basically in many ppls feedback, u can go through that as well.
    Times asked 2
  4. 4
    then he asked what approach would be usefull Vertical scalling or horzontal scalling in order to handle millions of upcoming api calls for the booking of treks slots, then I replied that there r no perfect solutions in distributed systems its just what we want to make tradeoffs with.
    Times asked 2
  5. 5
    and then I just wasted time in demonstrating the app and giving him an idea of how i have implemented those stuffs in frontend or backend and got him impressed by me.
    Times asked 2
Advice: Be calm and confident go through ur code so well that u can say about that for so looong
  1. 1
    Asked about celery
    Times asked 2
  2. 2
    asked about reddis
    Times asked 2
  3. 3
    asked about scheduling i.e beat vs worker
    Times asked 2
  4. 4
    asked if i have implemented all features (i did all the core features)
    Times asked 2
  5. 5
    coding ques-
    Times asked 2
  6. 6
    how to prevent those user whos name start from N from login in.
    Times asked 2
Advice: He is Veryy Cill , but he saidd he has failed more than 50% of students he got so read the sheet throghly before facing him
  1. 1
    - All the code question are mentioned in the sheet only so practice it thoroughly, like changing colour, moving the nav bar position, etc
    Times asked 2
  2. 2
    - theory questions are also same as mentioned in the sheet like, mvc, celery
    Times asked 1
  3. 3
    - one question he asked but I wasn't able to answer was adding a new entry (like a student) to the db through python script or terminal... (It was mentioned in the sheet but still 😭🥲)
    Times asked 1
Advice: - he will not speak very much ... You just have to go on explaining. He asked for a full demo (explain everything you app can do, demo background jobs like mail if possible), then asked to fully explain the code (both front end and backend, just detailed overview) - he's very chill, even though I wasn't able to answer the final question, he told me my approach was correct and then told me I did a good job 🙃🫪.
  1. 1
    Questions are almost similar what is mentioned in the sheet.
    Times asked 2
Advice: Examiner is not so rude, shares feedback (positive and negative). Overall ok experience.
  1. 1
    level2_141: Placement Portal
    Times asked 2
  2. 2
    1.⁠ ⁠Asked to run the application
    Times asked 2
  3. 3
    2.⁠ ⁠⁠Asked to register student, company and show admin dashboard
    Times asked 2
  4. 4
    3.⁠ ⁠⁠asked to schedule a drive
    Times asked 2
  5. 5
    4.⁠ ⁠⁠asked to shortlist and select a student, and also make it show on the student dashboard
    Times asked 2
  6. 6
    5.⁠ ⁠⁠show the search functionality
    Times asked 2
  7. 7
    6.⁠ ⁠⁠show the celery task being executed, such as mail sending
    Times asked 2
Advice: Examiner is chill. Remain relaxed, and answer confidently upto the extent you know, no need to panic as he gives ample time to think and answer. Mostly the above questions will get repeated in your case too. Happy Learning.
  1. 1
    the exact same questions given in this sheet for the proctor id and for level 1.
    Times asked 2
Advice: proctor is a chill guy.
Maintaine By Lazy IITians Team + IITM BS students Regualr for More data you have