Dec 2022Campus Tooling1 min read

PIET Quest Exam Portal

Campus exams ran side by side in shared labs, where one screen was easy to copy from. I built PIET Quest, the college's exam portal: each student gets their own question and option order, leaving the exam window is detected, and faculty load whole question banks in bulk.

Students sitting side by side got different papers, so copying stopped paying off

PHP / SQL

Integrity model
Per-session seeded permutation
Faculty tooling
Bulk CSV/JSON question bank import

What it does

Static digital exams make collusion easy: every candidate sees the same order. Faculty also spent too long formatting banks and grading MCQs by hand.

PIET Quest issues a session seed, permutes questions and options per candidate, monitors focus-loss / tab events with configurable thresholds, and grades against a canonical key after mapping permutations back.

Constraints

  • Burst login load when an exam slot opens
  • Unique paper per session without breaking grading keys
  • Usable latency on campus Wi-Fi
  • Faculty need bulk bank import and automated reports

Decisions & tradeoffs

  1. Seeded on-the-fly permutation instead of pre-generating thousands of static papers
  2. Integrity monitor that can reshuffle when anomaly thresholds trip
  3. Signed session tokens carrying seed/state to reduce live DB lookups mid-exam
  4. CSV/JSON bank parsers with schema checks for faculty prep
Diagram
NominalAnomalyCandidate LoginSession Token plus SeedSeeded QuestionPermutationsActive Exam InterfaceFocus lost?Permuted SequenceAnti-Tamper ReshuffleResponse Submission

Tradeoffs: on-the-fly permutation saves storage and costs CPU at render time. Aggressive anti-cheat creates false positives: thresholds are configurable for that reason.

What it demonstrates

  • Designing for concurrent campus exam load
  • Integrity controls that stay explainable (seeds + rules, not black-box scoring)
  • Admin tooling that shortens faculty prep time