11:18:44 AM NPT Arduino, Robotics & IoT tutorials for Nepal
Beginner

Project Viva and Defence: Questions Examiners Commonly Ask (and How to Answer)

Prepare for your BE or BSc CSIT project defence: a 5-minute demo script, common viva questions with answer patterns, slide tips and a mock viva checklist.

On this page
Project Viva and Defence: Questions Examiners Commonly Ask (and How to Answer)

The demo worked. The slides looked good. Then the examiner asked one question, and the room went quiet.

That moment is what most students fear about the project defence, and it is also the part you can prepare for best. Examiners are not trying to trap you. They want to know three things: did you understand what you built, did you actually build it, and can you judge your own work honestly.

This guide covers a demo script you can rehearse, the questions that commonly come up in BE and BSc CSIT project defences, patterns for answering them, and a mock viva checklist.

A note before we start: every college runs proposal, mid-term and final defences differently. Panel size, time limits, marking and format all vary. Ask your supervisor and your seniors how it works in your department, and follow their guidance over anything general like this article.

The 5-minute demo script

A demo without a plan turns into clicking around and hoping. Write a script and rehearse it with a timer.

Scroll sideways to see all columns.

Minute What you do What you say (example)
0:00 to 0:30 State the problem in one line "Rooftop tanks overflow or run dry because nobody can see the level."
0:30 to 1:00 Show the block diagram "Sensor on the lid, ESP32 in the middle, phone page on the right."
1:00 to 3:00 Show it working, live Change the input, point to the output changing
3:00 to 4:00 Show one failure case and how you handle it "If the sensor gets no echo, the page shows 'sensor error' instead of a wrong number."
4:00 to 5:00 Results and limitations "Within about two centimetres of a tape measure in our tests. Not tested on tanks taller than two metres."

Showing a failure case on purpose sounds risky, but it is one of the strongest things you can do. It proves you tested the edges of your system and did not just hope.

Always have a backup: a short screen recording or video of the working system on your laptop, in case the hardware or the network misbehaves on the day.

Questions examiners commonly ask

The exact questions depend on your project and your panel, but these patterns come up again and again. Prepare a short answer to each before the defence.

"Why did you choose this microcontroller / algorithm / framework?"

Have a 20-second answer ready. The pattern is: requirements first, then a comparison, then a trade-off.

"We needed Wi-Fi, at least six GPIO pins and an analog input. We compared Arduino Uno and ESP32. The Uno has no Wi-Fi, so we chose ESP32. The trade-off is 3.3 V logic, so we added a voltage divider on the sensor's echo pin."

The same shape works for software: "We needed X, we compared A and B, we chose B because Y, the downside is Z." Never say "because our senior used it" or "because it was popular".

"What are the limitations of your project?"

Never answer "none". Every system has limits, and saying "none" tells the panel you have not thought about it. Think in three groups:

  • Accuracy limits: how far off are your readings or predictions, and under what conditions?
  • Scale, cost and power limits: does it work for one room but not a building? Does it need mains power or constant Wi-Fi?
  • What you would do next: this turns a limitation into a plan, which examiners like.

"What did you personally do?"

In group projects, this question is common. Each member should be able to explain the whole system at a basic level and their own part in depth. Agree the division of work before the defence, so your answers match. If you wrote the firmware, be ready to open the code and explain any function.

"Explain this block / this function / this formula."

Examiners often point to one part and ask you to go deeper. Pick the part of your project you know best and prepare to explain it from first principles. For a hardware project that might be how the sensor works and how you converted its reading. For a CSIT project it might be your main algorithm, the database schema, or how authentication works. If your project uses an algorithm, our web and mobile app project ideas guide explains why naming and explaining a real algorithm matters.

"How did you test it? What were the results?"

Link your answer back to your objectives. If an objective was "display the tank level as a percentage", your test might be "compared against a measuring tape at five water depths". Show a results table, not just "it worked". Real numbers, even imperfect ones, are far more convincing than claims.

"What happens if...?"

Power fails, Wi-Fi drops, a user enters wrong data, the sensor is unplugged. Run through these before the defence and know what your system does in each case. If it does something bad, say so and explain how you would fix it.

"Why is this better than existing solutions?"

This comes from your literature review. Point to the gap you identified in your proposal and show how your project addresses it. Be modest: "it adds remote viewing, which the projects we reviewed did not have" is better than "it is the best system".

Handling "I don't know"

You will not know every answer, and that is normal. What matters is how you respond.

  • Do not guess wildly. A confident wrong answer is worse than an honest one.
  • Say what you do know, then admit the gap: "I know the sensor uses the echo time to measure distance. I have not studied how the module filters noise internally."
  • Offer how you would find out: "I would check the datasheet for that."
  • Never blame a teammate in front of the panel.

Slides: one idea per slide

A wall of text loses the panel. Good defence slides follow a few simple rules:

Scroll sideways to see all columns.

Do Avoid
One idea per slide Paragraphs copied from the report
Diagrams, photos of your build, result charts Clip-art and stock images
Big numbers, few words Tiny fonts that need squinting
Your block diagram early in the deck Starting with the history of the internet
A slide for limitations and future work Hiding the weak points

Practise with a timer. If your slot is short, cut slides rather than talking faster.

Your report will be read too

Panels often look at the report before or during the defence. Make sure your chapters, figures and references are in order and match what you say. The companion guide, How to Write Your Project Report: Chapters, Diagrams and References, walks through chapter order and citing datasheets properly.

Mock viva checklist

Run at least one mock viva with friends, seniors or your supervisor a week before the real one.

  • Demo script rehearsed with a timer, at least three times.
  • Backup video of the working system saved offline on the laptop.
  • Every team member can explain the block diagram end to end.
  • Each member can explain their own part in depth, including code.
  • Short answers ready for: why this board or algorithm, limitations, testing, what happens if, what you did.
  • Results table with real measurements in the slides.
  • Spare cables, a charged power bank, the board's USB cable, and a copy of the code.
  • Report, slides and demo all describe the same system and the same numbers.

FAQ

What should I wear and bring?

Follow your college's norms; neat and comfortable is usually right. Bring your hardware, spare cables, power, a printed or digital copy of the report, and a backup video.

What if the demo fails during the defence?

Stay calm, explain what you think went wrong, and show the backup video. Explaining a failure clearly can still show the panel that you understand your system.

Do examiners ask questions outside the project?

Sometimes questions touch on basic theory behind your project, such as how a sensor works or what a protocol does. Revise the fundamentals of every component and technology you used.

How do I prepare as a team?

Divide the slides, but make sure everyone can explain everything at a basic level. Run mock vivas where teammates ask each other hard questions.

Where do I start if my project is still at the planning stage?

Read How to Choose and Plan Your Final Year Project. For a complete build you can study for viva practice, see the RFID attendance system with a web dashboard.

Related tutorials

See all BSc CSIT Projects →