The questions below are grouped the way most vivas run, each with what a good answer contains. Practise them out loud, with your own project open in front of you.
- The viva checks understanding, not memory. Explain in your own words.
- Expect five groups of questions: the problem, the design, your own part, testing and results, and limits and future work.
- Know your module cold. Examiners ask each member about what they built.
- Run the demo yourself on the laptop you will use, the day before.
- Prepare a one-minute summary of the whole project; it is often the first question.
What do examiners ask about the problem and the idea?
- “Explain your project in one minute.” The problem, who has it, what you built and the main result.
- “Why did you choose this topic?” A real reason: a problem you saw, a gap in existing work, a skill you wanted to build.
- “What do existing solutions do, and what is missing?” Name two or three, and the gap you address.
- “Who would use this, and how?” A concrete user and situation.
What do they ask about the design and tools?
- “Walk me through the architecture.” Point at the block diagram and follow one input to the output.
- “Why this language, framework or board?” A reason tied to the problem, such as a library you needed or a sensor it supports.
- “What does this module do?” Its input, its output and why it is separate.
- “What happens if this part fails?” How the system behaves and what you would add.
What do they ask about your own part?
- “Which part did you build?” Name it, then explain it without notes.
- “Show me where this happens in the code.” Open the file and find it quickly.
- “What was the hardest bug, and how did you fix it?” A real example is convincing.
- “What would you change if you started again?” One honest improvement.
Viva soon and not sure you can explain the code?
Send your project and your viva date. We walk your team through the code, the design and the likely questions, covering each member’s part, after a free consultation.
What do they ask about testing and results?
- “How did you test it?” Your test cases, including ones that should fail.
- “What does this number mean?” Accuracy, precision, recall, latency or error: what it measures and why it suits your problem.
- “Compared with what?” A baseline, an existing method or the manual way.
- “Where does it fail?” Show you know its limits.
Which questions come up for AI, web and IoT projects?
| Project type | Likely questions |
|---|---|
| Machine learning and AI | Where did the data come from? How did you split it? Why this model and not a simpler one? What is overfitting, and did you check for it? Why this metric? |
| Web and mobile apps | How is the database designed? How do you store passwords? What happens with two users at once? How would it handle more users? |
| IoT and electronics | Why this sensor? How did you calibrate it? How is the board powered? What happens if the network drops? How accurate are the readings against a reference? |
| M.Tech projects | What did the base paper report, and did you match it? What exactly is your contribution? Is the gain significant? What would a reviewer criticise? |
Topic-specific viva questions are listed in each of our project guides, such as customer churn prediction and waste classification.
How do you prepare for the viva in a week?
- Day 1–2: install and run the project from scratch on the laptop you will use, and note every step.
- Day 3: read your report and check it against the format, so your answers match what is written.
- Day 4: each member rehearses their own module out loud in under three minutes.
- Day 5: answer every question on this page for your project, in writing.
- Day 6: a mock viva, with a friend asking questions in a random order.
- Day 7: charge everything, keep a backup of the demo and a recorded video in case the hall’s network fails.
For what we provide with a project, including the walkthrough, see final year projects for CSE and IT and M.Tech projects.
Frequently asked questions
What questions are asked in a final year project viva?
Why you chose the problem, what existing solutions miss, how the system works, which part you built, why you chose your tools, how you tested it, what your results mean and what you would improve. Examiners also pick a screen or a block of code and ask you to explain it.
How do I prepare for a project viva in one week?
Run the project yourself from a fresh setup, prepare a one-minute summary, rehearse your own module out loud, read your report so your answers match it, and do a mock viva where a friend asks the questions on this page.
What if I don’t know the answer to a viva question?
Say so briefly, then say how you would find out or what you think the answer is and why. Examiners respond better to an honest, reasoned answer than to a confident guess that turns out wrong.
Do all team members get asked questions in a viva?
Usually yes. Examiners often ask each member about the part they built, so every member should be able to run the demo and explain their own module without help.
Can The Ultimate Project World help with viva preparation?
Yes. Viva preparation is part of every project we build: a walkthrough of the code and the likely questions, covering each member’s part. Send your project and your viva date in the free consultation.
