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
    1.show id card
    Times asked 2
  2. 2
    2.download and present the project
    Times asked 2
  3. 3
    3.show the celery jobs daily emails and monthly notifications.
    Times asked 2
  4. 4
    4.change the appointments tab to show only cancelled appointments
    Times asked 1
  5. 5
    5.shift navbar at bottom
    Times asked 2
  6. 6
    6.have you implemented caching.
    Times asked 1
  7. 7
    7.what is celery async and celery beat . where have you implemented celery async
    Times asked 1
Advice: he is cool just go through this sheet
  1. 1
    -Download project from GitHub or open project and do checksum
    Times asked 2
  2. 2
    - Q. Have you used CDN or CLI?
    Times asked 1
  3. 3
    -All functionalities check
    Times asked 1
  4. 4
    -show frontend and show DoctorDashboard
    Times asked 2
  5. 5
    -Open notepad and write a login route (stopped me after 4 lines)
    Times asked 1
  6. 6
    -Q. What are 400, 401, etc? (HTTPs codes)
    Times asked 2
  7. 7
    -Q. If there is a bug in your code, how do you de-bug?
    Times asked 2
  8. 8
    -Do you have any questions? (I just asked tips for viva 2 and my review, which he gave me in depth)
    Times asked 2
Advice: Learn definitions
  1. 1
    2.GitHub Repo and collaboraters
    Times asked 1
  2. 2
    4.Asked if background mailing jobs had been added
    Times asked 2
  3. 3
    5.Asked if caching had been done
    Times asked 2
  4. 4
    6.Asked about authentication token used
    Times asked 2
  5. 5
    8. Asked me to write JS code to return the squared value of an integer
    Times asked 2
Advice: This was a Level 1 Viva.Most questions were in sheet already. I asked to refer VueJs documentation but he just gave a different question for JavaScript instead.
  1. 1
    schedule vs async celery beat
    Times asked 2
Advice: Be thorough with theory of mad 2 and try experimenting various changes in your code for practice
  1. 1
    Axios kya hota hh
    Times asked 2
  2. 2
    Authentication and authorisation diff
    Times asked 2
  3. 3
    Cache ka implement Kiya haii
    Times asked 2
  4. 4
    Bss
    Times asked 2
  5. 5
    No code changes
    Times asked 2
  6. 6
    Direct he started with checking edge in last he case these ques which I have mention above
    Times asked 2
  7. 7
    Aur edge me saari functionality test ki thi agar patient block kar de toh login kar skta haii ki nhi
    Times asked 2
  8. 8
    Can admin Search doc pat
    Times asked 2
  9. 9
    2 Patient can book same doc at same
    Times asked 2
  10. 10
    CSV export fucntionaly
    Times asked 2
  11. 11
    Email bejo
    Times asked 2
  12. 12
    He was chill aram se ho gyaa
    Times asked 2
Advice: Just beware of code you have written he will ask from code you have written
  1. 1
    Checked every functionality, everything is working
    Times asked 2
  2. 2
    where we used cache is the project
    Times asked 2
  3. 3
    why it is used
    Times asked 2
  4. 4
    export csv, how it works
    Times asked 2
  5. 5
    how authorization is done?
    Times asked 2
  6. 6
    and said to prepare for viva2
    Times asked 2
  7. 7
    very calm and nice person
    Times asked 2
  1. 1
    1.show all functionalities of app
    Times asked 2
  2. 2
    2.highlevel overview of code
    Times asked 2
  3. 3
    4.make change in register form frontend move a specific element
    Times asked 2
  4. 4
    7.explain appointment booking implementation in your code
    Times asked 2
  5. 5
    9 if user logins ur app how are you validating user
    Times asked 2
  6. 6
    10.show a get,post api of app in postman
    Times asked 2
  7. 7
    11.did you use bootstrap styling or css
    Times asked 2
  8. 8
    12.decorators
    Times asked 2
  9. 9
    13.git and vcs
    Times asked 1
Advice: properly understand your code.be confident.he is chill proctor mostly asking these questions to all in theory,coding changes and asking to explain code after seeing our code
  1. 1
    what is this cascade =all , delete orphans are they both needed
    Times asked 2
  2. 2
    then route ask for a explanation of a admin route
    Times asked 2
  3. 3
    the we move to app.py and ask for how this context celery code block do work(call_)
    Times asked 2
  4. 4
    then we move to front end ask me what is the difference in == and === in java and some more simple question (don't remember) easy one at one point i got stuck in one question and didn't know the answer(celery and redis code ) so give him a honest answer that i don't know that so he simply move to next question notes : have a good knowledge of each line of your code like every single like specially from back end an db
    Times asked 2
Advice: good proctor asked the questions in chill way you can take your time and think to keep in mind know your code well like each and everyline he will go in depth
  1. 1
    ask for basic ie. check github collaborators,id
    Times asked 2
  2. 2
    Q&N not in order
    Times asked 2
  3. 3
    3. where you code logic for stoping booking for two duplicate slot
    Times asked 2
  4. 4
    for coding problem
    Times asked 2
  5. 5
    asked to code a route which return some on two number
    Times asked 2
Advice: Very chill guy just practice the code and question given in the sheet he mostly ask same type of question
  1. 1
    demo of the project
    Times asked 1
  2. 2
    explain vcs , git
    Times asked 2
  3. 3
    explain the flow of how company will select student
    Times asked 2
  4. 4
    explain eligibility criterias(that you have set that student can see the drives according to that)
    Times asked 2
  5. 5
    explain relationship
    Times asked 2
  6. 6
    backref vs back_populated
    Times asked 2
  7. 7
    coding ques: move companyregister button to top right corner
    Times asked 2
Advice: good examiner
Created for educational purposes only. Questions are based on students' personal experiences and may not reflect actual exam content.