For the full guide to answering them, see our viva questions guide. The most useful line in our viva question bank is not a question. It is the short note printed under each one, saying what the examiner is actually testing. When I set the bank up, I decided that every entry had to carry one, because a list of questions is only half a tool. The follow-up in a viva is always aimed at the note, never at the wording.
The student’s problem, in plain words
You search for project viva questions and find PDFs, document-sharing pages and a few college blogs, mostly long lists with a one-line answer under each. You read fifty of them the night before. Then the panel asks something that is not on any list, and you freeze, because you memorised sentences and not what they were for.
Picture a BCA student with a good project and a good memory. This is a made-up student. The panel says “open the database and show me a real record” and she has only ever shown the app. Nothing on her list covered that, because it is not a question about knowledge. It checks whether the data is real or hardcoded for the demo.
Chapter one: group the questions by purpose
The bank currently holds 83 questions, in ten categories. By count they are: failure handling 15, design decisions 11, machine learning 11, security 9, database 8, your code 8, running it 6, closing 6, frontend 5 and testing 4. The sizes are simply what you get when you sort the questions by what they test, and the shape is informative. The largest group is not about knowledge at all. It is about what happens when something goes wrong.
Chapter two: “running it” and “your code”
These are the groups that catch students who did not build the project. “Can you set this up from scratch on this machine right now?” tests whether you have ever installed it yourself. “What does this line do? Why is it necessary?” carries a blunt note in the bank: usually asked about the one line you copied. “Show me a bug you fixed and explain what was wrong” is marked as the clearest evidence of authorship.
And there is “Which part did you find hardest, and how did you get past it?” The bank says: not small talk. Builders have a specific story; buyers do not. That is the reason this whole series of guides is written as stories. If you have built something, you already have one. Write it down before the viva, in three sentences.
Chapter three: failure handling is the biggest group
Fifteen questions, more than any other category. “What happens if two users do this at exactly the same time?” is marked “race conditions; almost nobody prepares for this”. Others: enter a negative number here, submit this form empty, upload a file in the wrong format, what if the network drops halfway through, what does your app do when the external API is down.
The pattern is that none of them need advanced knowledge. They need the habit of having broken your own project on purpose. A student can prepare for this category completely, in one afternoon, by trying each of those on their own app and writing down what happened. The race condition has a concrete answer in two of our projects. In the hospital management system, a unique index stops two patients booking one slot. In the e-commerce project, a single atomic update that matches only when enough stock remains stops two customers buying the last unit.
The turning point: stop collecting answers
Here is the idea the bank is built on. A one-line model answer is useless if the question arrives in different words. The note under the question is what transfers. “Whether you can name the alternative you rejected” applies to the database, the framework and the algorithm. “Whether the report matches the code”, the note on the ER diagram question, applies to every diagram you submit. Once you learn the ten or so things being tested, most questions become variations.
Security and database questions work the same way. Where are passwords stored and in what form? Whether hashing is understood or just mentioned. Can one user read another user’s data by changing the URL? Object-level authorisation, which the bank notes is very commonly missing. If you can answer those in the language of your own routes and tables, you have answered the category.
What I would do again
- Sort practice questions by what they test, not by topic.
- Run your project from a clean folder once, on a different machine if you can.
- Open your database and have one real record ready to show.
- Break your own app with a negative number, an empty form and a wrong file type, and note what happens.
- Prepare one real story about the hardest part and one bug you fixed.
- For each design choice, write the alternative you rejected in one sentence.
- Prepare an honest, specific answer to “how much did you write yourself?”
Where to practise
The full bank is on the question bank page, filterable by category and project type, with a tick-off list that saves your progress in your own browser. For how the whole viva is structured, read the viva questions guide and then how to explain your project.
If your worry is that the project is not yours enough to answer these, that is a real problem and a fixable one. On DefendIt’s Mentored tier the project is built together in live classes, one module per class, with you writing part of each module yourself, and it ends with viva prep and a mock viva. See the custom project class if you want to talk it through.