Karnataka KSEAB SSLC JTS Programming in ANSI C exam-day guide
Karnataka KSEAB SSLC JTS Programming in ANSI C · Prepare for the day ahead.
Your checklist
Hall ticket / admission ticket
Print the KSEAB SSLC JTS practical hall ticket and carry at least one extra copy. Verify the exam centre name, date, and reporting time printed on it. If the ticket is not yet available, download it as soon as your school releases it; confirm the release route with your school or the board's official portal.
School ID card and one photo ID
Carry your school identity card plus one additional photo ID if your school issues one. The exact list of accepted IDs for practical examinations should be confirmed with your school or exam centre; do not assume a single document is enough.
Blue or black ballpoint pens (two or more)
Carry at least two working ballpoint pens for writing the record, algorithm, and program on paper. Check the board's current instruction on permitted ink colour on the answer booklet; if unsure, confirm with your teacher.
Pencil, eraser, and sharpener
Useful for flowcharts, rough work, and corrections. Keep them in a transparent pouch if your centre requires transparent stationery.
Written record / observation book
Most JTS practical schemes require a completed practical record or observation book signed by the teacher. Bring it if your school has told you to submit it on the exam day. The exact requirement and submission procedure should be confirmed with your school.
Programs and algorithms revised on paper
Revise by handwriting programs, not only by reading. Practical exams usually ask you to write a program and then run or explain it, so practise writing complete programs with correct syntax, declarations, and header files.
Know your C syntax cold
Be able to write from memory: #include <stdio.h>, int main(void), variable declarations, scanf and printf format specifiers, if/else, for and while loops, arrays, and simple functions. These are the building blocks most practical tasks combine.
Dry-run and trace practice
Practise tracing a short program by hand: list variables, update them line by line, and write the output. Examiners often ask you to explain output or find an error, and tracing is the fastest way to answer.
Reporting time and travel plan
Confirm the reporting time with your school and plan to reach the centre well before it. Practical batches can start early and latecomers may not be accommodated; the exact late-entry rule should be confirmed with the provider.
Water bottle and simple snack
Practical sessions can run long. Carry water and a light snack, but check whether the centre allows them into the lab; if unsure, confirm with the provider.
No smart devices
Leave smartwatches and mobile phones out of the lab or switch them off and hand them over as instructed. Carrying a phone into the lab may be treated as malpractice.
Read the instructions on the question paper first
Before writing anything, read all questions or tasks, note the marks for each, and decide the order in which you will attempt them.
Plan the day
Revise from your own handwritten notes and record book, not from new material. Rewrite from memory the standard program patterns: sum and average of numbers, largest or smallest in an array, factorial, prime check, Fibonacci series, reversing a number or string, counting vowels, matrix addition, and simple menu-driven programs using switch. For each, write the algorithm, the program, and a sample input-output table. Time yourself writing one full program in about 15 to 20 minutes.
Practise on a computer if you have access, or at least on paper if you do not. Focus on the errors you actually make: missing semicolons, wrong format specifiers (%d for int, %f for float, %c for char, %s for string), missing & in scanf, uninitialised variables, and array index off-by-one. Keep a one-page list of your own recurring mistakes and read it before the exam.
Check logistics: confirm the exam centre, date, reporting time, and batch with your school. Arrange transport and, if needed, an overnight stay. Keep the hall ticket, ID, and record book together in one folder so nothing is misplaced.
Do a light revision only: read your one-page mistake list, the syntax summary, and two or three complete programs you have already written. Do not start new topics. Pack the checklist items into your bag, charge nothing that needs charging, and set two alarms. Sleep on time; a tired candidate makes syntax errors.
Eat a proper breakfast, re-check the hall ticket and ID, and leave early enough to arrive before the reporting time. Avoid last-minute cramming of new programs; instead skim your mistake list and the format specifier table.
Read the whole question paper first and mark which task you will do first. Write the algorithm or steps before the program, then write the program neatly with correct indentation. If you must run it on a computer, compile early and fix errors one at a time, reading the compiler message carefully. If asked to explain, speak clearly and trace the code line by line. Reserve the last few minutes to check semicolons, braces, header files, and that your name and roll number are filled in correctly.
Rules to check
Carry your hall ticket and the ID documents your school has specified at all times in the centre. The exact list of accepted identity documents should be confirmed with your school or the exam centre before the exam day.
Follow the centre's instructions on where to sit, which computer to use, and when to start. Do not touch another candidate's machine or share code, files, or answers; practical exams are individual work.
Mobile phones, smartwatches, and other electronic devices are generally not permitted in the lab. Hand them over or leave them outside as instructed; the exact policy should be confirmed with the provider.
Ask the invigilator or instructor if a question is unclear or if your computer fails. Do not attempt to fix lab equipment yourself; report the problem and wait for instructions.
Write your answers and programs in the answer booklet or on the computer exactly as instructed. Keep rough work clearly marked as rough work.
If you need to leave the room, raise your hand and wait for permission. The rules on breaks and re-entry during a practical session should be confirmed with the provider.
Scoring is done against the board's practical scheme, which typically covers the written program, execution or output, record book, and viva. The exact marks split and pass criteria for your year should be confirmed with your teacher or the official board material.
Any attempt to copy, use unauthorised material, or communicate with others may be treated as malpractice under board rules. The specific penalties should be confirmed with the provider.