Karnataka II PUC Computer Science (KSEAB) exam-day guide
Karnataka II PUC Computer Science (KSEAB) · Prepare for the day ahead.
Your checklist
Hall ticket / admission ticket with your register number
Carry the same photo-bearing ticket your school issued for the board exams. Some centres accept only the college ID for practicals, so confirm with your teacher which document the external examiner will ask for (needs_review).
College identity card
A second photo ID removes any doubt at the door if the hall ticket is not demanded. Keep both in one plastic folder so you are not searching your bag while the examiner is calling roll.
Completed practical record / journal, signed
Every prescribed program should be written with aim, algorithm, program, and pasted or handwritten output, and signed by your teacher. Confirm with your school the exact number of programs and the signature/date columns they require (needs_review).
Two blue or black ball pens, one pencil, eraser, sharpener, small scale
Write the program portion in pen so it is legible; use the pencil for rough work and for drawing any table or flowchart the examiner expects. Test your pens the night before - a leaking pen ruins an answer booklet.
Confirmed reporting time and centre location
Practicals are usually held at your own college in batches, but the timing can differ from the theory exam. Ask your teacher for the batch list and reporting time in writing, and plan to arrive 30-40 minutes early (needs_review).
Knowledge of the programming language your batch was taught
KSEAB has revised the II PUC Computer Science material in recent years, so confirm whether your batch writes programs in C++ or Python and practise only that syntax. Mixing languages in the answer booklet costs marks.
Handwritten one-page syntax sheet to revise outside the hall
List the loop and array syntax, function definition, and the SQL clauses (SELECT, FROM, WHERE, GROUP BY, HAVING, ORDER BY) you keep forgetting. Read it before entry and leave it in your bag - nothing written may be carried to the table.
Plain wrist watch (not a smartwatch)
Practical sessions can run two to three hours for a batch, and there may be no visible clock. A simple analogue or digital watch lets you budget ten minutes for planning and the rest for writing and execution.
Water bottle and a light snack for after the session
Batches often wait long before their turn and finish well past the scheduled hour. Keep these in your bag outside the hall; eating or drinking at the computer table is normally not allowed.
Dress code checked with your college
Many Karnataka PU colleges insist on the prescribed uniform for board practicals. If your college relaxes it during exams, get that confirmed by the coordinator rather than assuming (needs_review).
Plan the day
Close out the practical journal: check that every program listed in the syllabus is written with aim, algorithm, program and output, and that nothing is missing or unsigned. Get your teacher's signature the same day; finding a teacher on exam morning is rarely possible.
Take two or three programs from your record and rewrite them on blank paper from memory, then compare with the book. Do the same with three SQL queries on the sample tables: a simple SELECT with WHERE, one with GROUP BY and HAVING, and one with ORDER BY.
Examiners usually ask about your own record: why you used a particular loop, what a primary key is, the difference between DELETE and DROP, what a foreign key does, and the meaning of the OOP or Python terms in your syllabus. Prepare short spoken answers in your own words.
Put the hall ticket, ID, record, pens and geometry items in one bag. Reconfirm the batch timing and reporting time with your teacher or the college notice board, and check the travel time to the centre so you are not guessing in the morning.
Reread the syntax sheet and skim your record's table of contents. Do not start learning a new topic or a new language feature; sleep at your normal time, because mistakes in practicals come mostly from rushing and fatigue.
Eat a proper breakfast, reach the centre 30-40 minutes before the reporting time, and keep your bag light. Once the batch is seated, listen carefully to the examiner's instructions about which questions to attempt and where to write the program and output.
Read both questions and pick the one you can finish completely; a half-written program scores poorly. Spend a few minutes writing the aim, algorithm or logic and the expected output, then write the program neatly with correct indentation and declared variables.
Type the program exactly as written, compile, fix only syntax errors you understand, and run it with the given test input. Save the file with the name and in the folder the examiner specifies, then raise your hand and show the working output before you leave the machine.
For the database question, write the query in full with the correct table and column names, then verify it against the given tables. When the viva begins, answer briefly and honestly; if you do not know, say so and explain what you do know rather than guessing.
Rules to check
Carry your hall ticket and a photo ID. Entry without the documents the centre demands can be refused, and the exact list differs by centre - confirm with your school before exam day (needs_review).
Mobile phones, smartwatches, and any other electronic device must stay switched off in your bag outside the hall. Using one is treated as malpractice under board rules.
Do not carry pre-written programs, printed code, or notes to the examination table. Only the answer booklet or record issued by the centre may be used for your answers.
Follow the batch and reporting discipline of the centre. If you are late, entry is at the examiner's discretion, so treat the reporting time as a hard deadline rather than a suggestion.
Ask the examiner or invigilator if a question is unclear or a machine or software fails. Report hardware problems immediately; do not silently restart or switch machines on your own.
Do not copy from or dictate to another candidate. Shared code or answers are treated as malpractice for both candidates, irrespective of who copied.
The practical marks usually combine the program/procedure, execution and output, the record, and the viva. The exact split can change with the syllabus revision, so confirm the current marking scheme with your teacher (needs_review).
Leave the lab only after your output has been seen and your booklet or record has been collected. Walking out without submitting can mean your work is not evaluated.