RBSE SS Computer Science exam-day guide
RBSE SS Computer Science · Prepare for the day ahead.
Your checklist
Printed admit card / hall ticket
Carry at least one printed copy and keep a photo on your phone as backup. Check that the roll number, subject (Computer Science), and exam centre address match your records. If the admit card has not been issued or you cannot download it, confirm the release process and download window with your school or the board's official portal - do not assume a timeline.
Valid photo ID as specified by the board
Bring the original ID document named on your admit card or in the board's instructions (commonly a school ID or government-issued photo ID). Photocopies are usually not accepted. The exact list of accepted documents and whether a school ID alone suffices must be confirmed with the provider or your school coordinator.
Two or three blue/black ballpoint pens
Bring spare pens of the same type. Confirm with the provider whether the answer book must be written in blue or black ink, and whether gel pens are permitted, since some centres restrict certain ink types.
Pencil, eraser, and sharpener
Useful for rough work, diagrams, and any multiple-choice or OMR-style section. Confirm whether the paper includes an OMR sheet, since that changes how carefully you must shade answers.
Simple analog or non-programmable watch
Many centres do not have a visible clock. A basic watch helps you pace sections. Smart watches and any device with connectivity or storage are almost always banned - confirm the allowed-watch rule with the provider.
Transparent water bottle and a light snack
Stay hydrated and keep energy up. Keep the bottle transparent and label-free if your centre requires it; confirm whether water bottles are allowed inside the hall at your specific centre.
Know the reporting time and centre location
Do a dry run to the centre or check the route and travel time in advance. Arrive before the reporting time printed on your admit card; late entry rules vary, so confirm the cut-off with the provider.
Revise the practical syllabus topics, not new material
Focus on the programming language in your syllabus, file handling, SQL or database basics, Boolean logic, and computer networks concepts as per your prescribed textbook. Do not start a new topic in the last 72 hours.
Practise writing code by hand
In the exam you write code on paper, not in an IDE. Practise writing complete programs, syntax, and dry runs on paper so you do not lose marks to indentation, semicolons, or bracket errors.
Prepare a one-page formula and syntax sheet
Summarise syntax for loops, functions, file open modes, SQL commands, and logic gates. Review it in the final hours instead of rereading the whole textbook.
Leave prohibited items at home
Phones, smart watches, Bluetooth devices, and study notes must not enter the hall. Confirm the centre's policy on where bags and phones can be deposited, since some centres provide no storage.
Check board-specific exam pattern and marks split
Confirm the theory and practical mark distribution, the number of sections, and whether internal choice exists in each section. This information should come from your prescribed syllabus or teacher; confirm any detail you are unsure about with the provider.
Plan the day
Do a full syllabus audit against the official syllabus checklist. Mark each topic as confident, shaky, or unknown. Spend this day only on shaky topics. Write at least two full programs by hand per shaky topic, then dry-run them line by line to catch logic errors.
Solve one full previous-pattern or sample paper under timed conditions, ideally at the same time of day as the real exam. Mark it strictly. List every lost mark and classify it as a knowledge gap, a syntax slip, or a time-management problem. Spend the evening fixing knowledge gaps only.
Light revision only. Review your one-page syntax sheet, logic gate truth tables, common SQL queries, and network topologies. Pack your bag with the admit card, ID, pens, pencil, eraser, and watch. Confirm the centre address and travel plan. Sleep early; do not study past midnight.
Do a final checklist of documents and stationery. Re-read the instructions printed on the admit card, including reporting time and prohibited items. Set two alarms. Avoid group discussions that might create panic about an unprepared topic; if a doubt arises, note it and move on rather than starting a new topic.
Eat a proper breakfast and carry water. Leave home with buffer time for traffic. Reach the centre before the reporting time. Keep your admit card and ID in hand for verification. Avoid last-minute cramming of new material; skim only your syntax sheet.
Read the full question paper and instructions carefully. Note the marks per section and any internal choices. Plan the order: attempt the questions you are most confident about first, and reserve time at the end for code-heavy and long-answer questions.
Write code with clear indentation and comments where helpful. Show dry-run tables for programs where the question asks for output. For SQL, write the query and, where asked, show the expected result. For logic gates, draw neat truth tables. Do not leave programming questions blank; partial structure often earns step marks.
Check that every question number matches the answer you wrote, that no question is unattempted, and that your roll number and details on the answer book are correct. Cross out rough work clearly. Do not rewrite large sections at the last minute.
Rules to check
Carry your admit card and the specified original photo ID at all times in the exam hall. If any document is missing, inform the invigilator immediately; the board's policy on provisional entry must be confirmed with the provider rather than assumed.
Electronic devices - phones, smart watches, Bluetooth earbuds, and programmable calculators - are generally prohibited. Confirm the exact permitted-calculator rule with the provider, since some boards allow a basic non-programmable calculator for certain papers.
Follow the invigilator's instructions on seating, answer book details, and timing. Do not communicate with other candidates during the exam, and do not borrow stationery from others; carry your own spares.
Write answers only in the designated answer book or sheet. Rough work should be done in the space provided and clearly marked. Answers written on question papers or loose sheets are usually not evaluated.
If you need a washroom break or feel unwell, raise your hand and wait for the invigilator. Time lost is generally not compensated, so plan hydration and breaks accordingly; confirm any specific break policy with the provider.
Marks are awarded for correct method and structure as well as final answers. Show steps in programs, SQL, and logic problems; an incomplete but well-structured answer can earn partial credit.
Any suspicion of unfair means can lead to cancellation of your paper. Keep your eyes on your own work, keep your answer book covered, and do not look around during the exam.
Confirm the board's policy on re-checking, re-evaluation, and compartment or supplementary exams from official sources after the exam; do not rely on rumours from peers.