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
    Probably the most patient and most nice proctor i have ever had in all subjects. Minimal implementation that too UI and Colours only. But you have to have good knowledge on your project and know what code does what. That should be enough. if you know what functions are in your files, that is it. Nothing else. Just demo wlakthrough and 10 minutes of simple questions. All the best
    Times asked 1
Advice: Just be confident. Nice and sweet proctor
  1. 1
    Explain vcs and git.
    Times asked 1
  2. 2
    Thats it no coding ques asked, viva ended in 30 mins
    Times asked 2
Advice: She is very good and friendly, know your code in detail and be confident. All the best
  1. 1
    Celery: What does .delay() do when calling a Celery task?
    Times asked 2
  2. 2
    Flask Coding: Write a simple POST route that accepts JSON data (username and email), creates a new user, and commits it to the SQL database.
    Times asked 2
  3. 3
    Database Logic: If the database file is deleted and the backend is rerun, will the application still work? Where exactly is the database created in the code?
    Times asked 2
  4. 4
    JavaScript Variables: What is the difference between const and let? Why did you use const for the search query variable instead of let?
    Times asked 2
  5. 5
    JavaScript Operators: What is the difference between single =, double ==, and triple ===?
    Times asked 2
  6. 6
    Caching: How exactly is Redis being used in your application?
    Times asked 2
  7. 7
    Live UI Edits: Modify the login page to put the emoji on top and change "Welcome back" to "Good morning" on the next line.
    Times asked 2
  8. 8
    App Logic Demo: What happens if all the slots are full? What will the user get to see?
    Times asked 2
  9. 9
    Background Jobs Demo: Demonstrate the CSV export functionality and the automated email reminders.
    Times asked 2
Advice: He was super chill, Be confident and if u are unsure u can say him , he will guide u on that way, be sure of what u have done in the code
  1. 1
    -Github collaborator
    Times asked 2
  2. 2
    -Download from portal and setup, no checksum required
    Times asked 2
  3. 3
    -show demo of the project
    Times asked 1
  4. 4
    -Open notepad and write the backend route for showing all trekkers who selected difficult trek only
    Times asked 2
  5. 5
    -Continue with demo show staff side of the portal
    Times asked 2
  6. 6
    -In your codebase where have you written the code for not letting the user do overbooking
    Times asked 2
  7. 7
    -List some HTTP methods
    Times asked 2
Advice: thank your lucky stars if you got this proctor
  1. 1
    10pm-11pm
    Times asked 2
  2. 2
    i had joined 10 minutes early, but so had the proctor
    Times asked 2
  3. 3
    explained at the start that you are in full control, show all functionalites and explain codebase
    Times asked 2
  4. 4
    stopped midway explaining the codebase for asking theory questions
    Times asked 2
  5. 5
    git vs versional control system
    Times asked 1
  6. 6
    if you query an empty table, what do u get
    Times asked 2
  7. 7
    if an app crashes, what is the first question you will ask the user and admin to identify source of crash (answer is check logs)
    Times asked 2
  8. 8
    said that you have thorough knowledge but suggested to learn more about backend systems like logs for industry standards
    Times asked 2
  9. 9
    ended within 40 minutes
    Times asked 2
Advice: extremely nice proctor, repeats questions from sheet, but more importantly very helpful person.
  1. 1
    first she asked to show the ID card. Before going to application walkthrough...she asked to explain the project structures, then asked...
    Times asked 2
  2. 2
    what is celery? what it does and why we need in this project.
    Times asked 2
  3. 3
    what is redis? what it does and why need of it.
    Times asked 1
  4. 4
    which db are you using? How sqlite and redis are different? then asked to go through with Models and asked: 4: what is to_dict() function in every table? what is the need of it? 5: what are other methods for serilizable data? then asked to show api's and asked: 6: what are the decorators? working and all. 7: how @admin_required working according to code which i had written? then send to go through with application. in mid she asked 8: to make the form validation while creating a new trek for prevention of negative inputs at last she just asked to show how celery is working and is user getting exported csv or not. and it's done!
    Times asked 1
Advice: she is very keen to know your theoretical knowledge. Prepare well.
  1. 1
    firstly he asked for Id card and github repo and commits then asked to start application and explanation. In between, i was asked to open models and he questioned:
    Times asked 1
  2. 2
    why uselist=False?
    Times asked 2
Advice: Know all the keywords that are used in Model Practice a simple api for GET and POST and PATCH also Know the basics of celery config and structure and workflow.
  1. 1
    Demo of application core functionality
    Times asked 2
  2. 2
    Show models.py asked to explain it.
    Times asked 2
  3. 3
    While explaining tell me to explain the relationship between tables i used.
    Times asked 2
  4. 4
    Difference between primary key and unique
    Times asked 2
  5. 5
    Can unique key be primary key?
    Times asked 1
  6. 6
    What is foreign key?
    Times asked 2
  7. 7
    Tell me to show admin’s staff management page then he asked me to change the colour of table’s row which i used to show staff information. ( like status approve and blacklisted ).
    Times asked 2
  8. 8
    After this he told me to add a button on the same admin’s staff management page to delete an existing staff from the application. ( both html template part and also the delete route for the same )
    Times asked 2
  9. 9
    Rapid fire questions: what is vertical and horizontal scaling? Difference between them.
    Times asked 2
  10. 10
    Authentication vs Authorisation
    Times asked 2
  11. 11
    Structured vs unstructured database
    Times asked 2
  12. 12
    I can’t remember more theory part now but similar questions to other reviews available on the sheet.
    Times asked 2
Advice: You should have well known to code base and he will thoroughly go through your code and will ask you to explain any part.
  1. 1
    - Show ID and GitHub page.
    Times asked 1
  2. 2
    - Download code from portal and run it.
    Times asked 2
  3. 3
    - Show login page and login route code.
    Times asked 2
  4. 4
    - Modify login code to print email when you click on the login button.
    Times asked 2
  5. 5
    - Login to the page and open the page in incognito window. Why in incognito you are redirected to login rather than to the portal with your credentials (Explain JWT and routing). Show the code for the same too.
    Times asked 1
  6. 6
    - Is caching done? What all data is cached? Why so? Is there any timeout set? When or how does this update?
    Times asked 2
  7. 7
    - Have you done any CSV exports? Show the same. (Explained how I had done and fallback as well)
    Times asked 2
  8. 8
    - Wished all the very best for Level 2.
    Times asked 2
Advice: - Be respectful and polite. Proctor is very respectful and accommodating. Do not stress, proctor is very calm. Proctor will give pointers or hints if things get stuck. - If you can't find the code, explain everything related to what code is asked and how you implemented and why such scenarios happen. - When coding, try to explain what you are doing and how exactly you have done it and why rather than coding in silence. - Might sometimes indirectly check all requirements through specific questions or asking for particular implementations or functionality demo. (Session-based logins, Celery Tasks, MailHog, Caching, Vue Routing, etc.). - Try to explain theory and other choices made when showing the code or showing the working of that feature. Try to tie theory concepts and implementation choices directly when showing so less chance of more questions asked. - Proctor may join early so make sure to join at least 10-15 earlier. It will be advantageous especially since most people might have issues with running the code; you can use that extra time to setup everything accordingly to make sure your code runs with no issues.
  1. 1
    Everything which is mentioned earlier in the sheet.
    Times asked 2
  2. 2
    Just follow the sheet he will ask exactly the same questions.
    Times asked 2
Advice: Take a chill pill he is very chill proctor. My app got crashed db was not sending data … celery beat and worker stopped working still he said take time its server and network issues, so no problem. Then it started working and done. Very good proctor. My L2 was easier than L1 tbh.
Maintaine By Lazy IITians Team + IITM BS students Regualr for More data you have