RBSE SS Informatics Practices study materials
RBSE SS Informatics Practices study resources

RBSE SS Informatics Practices exam-day guide

RBSE SS Informatics Practices · Prepare for the day ahead.

Your checklist

Admit card or hall ticket

Carry the document your school has told you to bring. For practical examinations, some schools accept the school ID card instead of the theory admit card; confirm with your school or the RBSE exam coordinator which document is required (needs_review).

School ID card

Bring your current school identity card with a photograph. It is the simplest way to verify your identity at the lab door if the admit card is not demanded.

Practical record file or portfolio

Bring the complete file containing your Python/Pandas programs, SQL queries, and their outputs, in the order your teacher prescribed. Check that every practical listed in your syllabus is present and that pages are numbered (needs_review: confirm whether your school requires teacher signatures or a specific cover page).

Project report, if your school requires one

Carry a printed or handwritten copy of your Informatics Practices project with the problem statement, code, output, and a short conclusion. Confirm with your teacher whether the project is assessed separately in your school's practical scheme (needs_review).

Stationery

Bring two pens, a pencil, an eraser, a sharpener, and a small ruler. Do not rely on borrowing; lab desks are often cleared before the exam.

Know your roll number and subject code

Write your roll number, name, and subject code on every answer sheet, output printout, or file page the invigilator asks you to submit. Practise writing it from memory so you do not lose time.

Leave mobile phones and smart devices at home

Do not carry a phone, smartwatch, or any storage device into the lab. If your school allows phones on campus, submit them at the collection point before entering; carrying one into the lab can lead to disqualification.

Rehearse your own file

Be ready to explain any program or query in your record, including why you used a particular Pandas function or SQL clause. Examiners commonly open the file at random during the viva.

Confirm the lab, reporting time, and batch

Practical exams run in batches, so your reporting time may differ from a friend's. Confirm the room, batch, and reporting time with your school at least two days in advance (needs_review: batch timings are set by the school and are not uniform).

Water bottle, if permitted

Carry a transparent water bottle only if your school allows it in the lab. Keep it on the floor, away from keyboards and power sockets.

Plan the day

Final 72 hours

Finish the practical file: complete any missing programs or SQL queries, paste or write the outputs, number the pages, and get any required signatures. Set aside one session to run each program mentally or on paper and note the output format. Spend another session on the viva: practise explaining joins, GROUP BY, pandas Series versus DataFrame, and one project decision.

Final 24 hours

Pack the admit card or ID, the file, the project report, and stationery in one bag. Re-read your own file rather than new material. Confirm your reporting time and batch once more. Sleep on time; a tired candidate makes syntax errors in SQL and Python.

Morning of the exam

Eat before you leave, because batches can run long. Reach the school at least 30 minutes before your reporting time. Carry only the permitted items; hand over any phone at the collection point. Skim a one-page list of reminders such as quoting string values in SQL, using print() correctly, and saving your work.

During the test

Read the question paper or instructions fully before typing. Attempt the queries and programs you are most confident about first, and save your file after every significant change. Write or print the required outputs and label them with the question number. In the viva, answer briefly and precisely; if you do not know a term, say so and explain what you do know rather than guessing. Before leaving, check that your file, answer sheet, and any output have been submitted and signed for as instructed.

Rules to check

  • Carry the identity document your school specifies; if you are unsure whether the admit card or the school ID is required for the practical, confirm with your school before the exam day.

  • Do not carry mobile phones, smartwatches, or storage devices into the laboratory. Follow your school's deposit procedure if devices are collected at the gate.

  • Work independently in the lab. Do not exchange code, queries, or files with other candidates during the examination.

  • Follow the invigilator's instructions on logging in, saving files, and submitting outputs. If a computer or software fails, raise your hand immediately instead of restarting equipment yourself.

  • Leave the lab only when permitted. If you need a break, ask the invigilator; do not walk out during a batch without permission.

  • The marks for the practical, viva, file, and project are set by the board's scheme and your school's internal arrangements. Confirm the exact split with your teacher rather than relying on second-hand information (needs_review).

  • Keep your practical file and project report neat and your own work. Plagiarised or identical files can be penalised by the examiner.

  • Address any doubt about question wording or expected output to the invigilator or examiner during the test; do not guess silently and lose marks.