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

2403 results · page 29/241

See reviews Level3_24 MAD2 Level 3
Download all Download all
Copy set link
  1. 1
    Well, you're lucky if you get him. Basically you won the lottery of Proctors. ✨
    Times asked 2
  2. 2
    Join sharply at the hour mark. At the start, he'll explain how the viva will go: Demonstrate your app functionality completely, explain the code and he'll just sit back and listen to your podcast. 😎
    Times asked 2
  3. 3
    He's pretty chill in letting you setup things (no pressure) but try to be as quick as you can.
    Times asked 2
  4. 4
    Demonstrate every nook and corner of your app.
    Times asked 2
  5. 5
    Go through every part of your code, one by one.
    Times asked 2
  6. 6
    At one point, he'll stop you and ask some theory questions. Luckily, it's always repeated. All will already be in the sheet above.
    Times asked 2
  7. 7
    * Can Flask API respond with a boolean value?
    Times asked 1
  8. 8
    * What will happen when you run the app when a table has no values?
    Times asked 2
  9. 9
    Other questions are already in the sheet! 🥰
    Times asked 1
  10. 10
    Hope this helps somewhat! Prepare and celebrate! 🎉
    Times asked 2
Advice: He's very chill but you get plus points if you're fast and smooth. Just go with the flow and don't stumble over anything. 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`. You'll do great! Good luck! 🤞🏼
See reviews appdev_level1_viva30 MAD2 Level 1
Download all Download all
Copy set link
  1. 1
    First complete project demo,
    Times asked 2
  2. 2
    Then for coding he asked me write a route to return all doctors (I have done hms project)
    Times asked 2
  3. 3
    Then for theory, he asked:
    Times asked 1
  4. 4
    where redis stores data (answer is ram),
    Times asked 2
  5. 5
    what is props in vue,
    Times asked 2
  6. 6
    where is jwt tokens stored (answer is local storage)
    Times asked 2
  7. 7
    that's all
    Times asked 2
Advice: Speaks very little, won't interrupt you. Didn't have any issues with him, just know your stuff and you'll get full marks
See reviews Level2_137 MAD2 Level 2
Download all Download all
Copy set link
  1. 1
    Session vs JWT
    Times asked 2
  2. 2
    Demo
    Times asked 9
  3. 3
    Good job and best of luck for level 2
    Times asked 2
Advice: He's chill
See reviews Appdev_level1_viva5 MAD2 Level 1
Download all Download all
Copy set link
  1. 1
    - he asked me run the project and all commands at beginning itself
    Times asked 2
  2. 2
    - ⁠asked me to give demo of entire website
    Times asked 2
  3. 3
    - ⁠asked me for celery tasks (i had only implemented them for admin)
    Times asked 2
  4. 4
    - ⁠i had not implmented the export functionality so he didnt ask for that
    Times asked 2
  5. 5
    - ⁠asked me if i could send a specific email but i didnt know what was so he asked to see code but i had not implemented that specific method too so he let it be
    Times asked 2
  6. 6
    - ⁠on my admin dashboard there is list of doctors and proctor asked me to only display 2 doctors (i wasnt expecting coding questions so i was a little bit surprised but was able to code in 3 minutes)
    Times asked 2
  7. 7
    - ⁠he then asked me to shift the navbar/header to the bottom (i was panicking but i was able to do it)
    Times asked 2
  8. 8
    - ⁠he then asked me theory questions
    Times asked 2
  9. 9
    - ⁠what is session based and token based caching
    Times asked 2
  10. 10
    - ⁠he asked me if i had implemented caching in project (i had only implemented redis for celery tasks not for project)
    Times asked 1
  11. 11
    - ⁠asked me to show github repo and done
    Times asked 2
  12. 12
    .
    Times asked 3
Advice: Overall an decent proctor. He seemed impatient and I was also nervous but i recommend be confident and know your code
See reviews level1_viva30 MAD2 Level 1
Download all Download all
Copy set link
  1. 1
    He came late, like 5 mins or so
    Times asked 2
  2. 2
    Asked for my ID Card
    Times asked 2
  3. 3
    Then asked me to download the submission from the portal and give me the Demo
    Times asked 2
  4. 4
    The demo took like 20-25 mins, I explained each and every feature, He wasn't responding much
    Times asked 2
  5. 5
    Then after Demo he asked me to show the Repository & Show collaborartor
    Times asked 2
  6. 6
    Then he asked me to write a route to fetch all the students and their details
    Times asked 2
  7. 7
    Then he asked me to write a for loop in Jinja
    Times asked 2
  8. 8
    Then he said, the viva is over and he left without saying anything.
    Times asked 2
Advice: Give the Demo in deep detail
See reviews Level3_24 MAD2 Level 3
Download all Download all
Copy set link
  1. 1
    Demonstration of all functionalities
    Times asked 2
  2. 2
    Move on to code demonstration
    Times asked 2
  3. 3
    Explained all the API code line by line
    Times asked 1
  4. 4
    Showed the edge cases being handled.
    Times asked 2
  5. 5
    Asked Types of browser Storage
    Times asked 2
Advice: Know your code thoroughly. Refer the sheet. Be confident. Chill proctor.
See reviews Appdev_level1_viva5 MAD2 Level 1
Download all Download all
Copy set link
  1. 1
    It starts with a demo then in admin i have shown booked, completed and cancelled appointment so he asks only show booked only then ask to make navbar to bottom and footer to navbar basically interchange.
    Times asked 2
  2. 2
    And then what is catching.
    Times asked 2
  3. 3
    Celery and redis working
    Times asked 4
Advice: He is rude and he do not listen much,not even focusing much. in level 1 itself asks to do changes much
See reviews APPDEV_LEVEL1_VIVA2 MAD2 Level 1
Download all Download all
Copy set link
  1. 1
    I began by accessing GitHub and navigating through the relevant repositories to familiarize myself with the project structure and available resources.
    Times asked 2
  2. 2
    Following that, I downloaded the project files from the portal and set up the local environment to ensure the application could be run and tested properly.
    Times asked 2
  3. 3
    I spent time exploring the project in detail, going through different modules, components, and files to build a general understanding of how the system is structured and how different parts interact with each other.
    Times asked 2
  4. 4
    During the session, important theoretical concepts were discussed, including the distinction between authentication (verifying a user’s identity) and authorisation (determining what actions the user is permitted to perform).
    Times asked 2
  5. 5
    Additionally, frontend concepts such as props and emit were explained, focusing on how data is passed between components and how child components communicate with parent components in a structured way.
    Times asked 2
  6. 6
    After gaining this foundational understanding, I was assigned a practical task involving code modification within the existing project.
    Times asked 2
  7. 7
    The task required adding a new button to the patient dashboard interface. This button was intended to utilize the weight data already present in the edit profile functionality.
    Times asked 2
  8. 8
    The expected functionality was that, upon clicking this button, it should connect to the history model and display the patient’s historical data accordingly.
    Times asked 2
  9. 9
    I successfully implemented the UI part of the requirement by creating and placing the button within the patient dashboard.
    Times asked 2
  10. 10
    However, I faced challenges in implementing the backend linkage and data flow, specifically in connecting the button action to the history model and retrieving/displaying the relevant patient history.
    Times asked 2
Advice: Transitioning to the proctor interaction, the overall experience was very positive and encouraging. The proctor created a comfortable environment right from the beginning of the session. As soon as he joined the meeting, he greeted me warmly and asked how I was doing, which helped ease some of my initial nervousness. He was attentive enough to notice that I seemed slightly anxious and made a conscious effort to motivate and reassure me, which significantly improved my confidence during the interaction. Throughout the viva, his tone remained polite, patient, and supportive, making it easier to communicate openly without feeling intimidated. After the viva concluded, I took the opportunity to ask for feedback on my performance. He responded thoughtfully and constructively, pointing out that I should focus more on improving both my understanding of theoretical concepts and my ability to implement code changes effectively. His feedback was clear, helpful, and delivered in a kind manner, making it easier to understand where I need to improve without feeling discouraged.
See reviews VIVA14 MAD2 Level 2
Download all Download all
Copy set link
  1. 1
    Authorization and authentication where token is stored asked me to find the token
    Times asked 2
Advice: He is cool good proctor
See reviews level1_viva2 MAD2 Level 1
Download all Download all
Copy set link
  1. 1
    Show app demonstration
    Times asked 2
  2. 2
    Then add one button on student dashboard that fetch student roll number and show roll number as button name and after clicking it should redirect and show student profile section
    Times asked 2
  3. 3
    Then he asked me what authentication method i used and where is token get stored
    Times asked 2
  4. 4
    Thats all he asked and lasted 25 min only
    Times asked 2
Advice: He is very nice and helpful proctor. Take most of time in demonstration and show each functionality and take more time in demonstration Good luck
Maintaine By Lazy IITians Team + IITM BS students Regualr for More data you have