Online Examination System

@RestController
@RequestMapping("/exam")
public class ExamController {
}

// 1. Student Entity
import jakarta.persistence.*;

@Entity
class Student {

  @Id
  @GeneratedValue(strategy = GenerationType.IDENTITY)
  private Long id;

  private String name;
  private String email;
}


// 2. Exam Entity
@Entity
class Exam {

  @Id
  @GeneratedValue(strategy = GenerationType.IDENTITY)
  private Long id;

  private String title;
  private String subject;
  private Integer totalMarks;
}


// 3. Question Entity
@Entity
class Question {

  @Id
  @GeneratedValue(strategy = GenerationType.IDENTITY)
  private Long id;

  private Long examId;
  private String questionText;
  private String optionA;
  private String optionB;
  private String optionC;
  private String optionD;
  private String correctAnswer;
}


// 4. Result Entity
@Entity
class Result {

  @Id
  @GeneratedValue(strategy = GenerationType.IDENTITY)
  private Long id;

  private Long studentId;
  private Long examId;
  private Integer score;
}


// 5. Repository Layer
import org.springframework.data.jpa.repository.JpaRepository;

interface StudentRepository extends JpaRepository<Student, Long> {}
interface ExamRepository extends JpaRepository<Exam, Long> {}
interface QuestionRepository extends JpaRepository<Question, Long> {}
interface ResultRepository extends JpaRepository<Result, Long> {}


// 6. Service Layer
import org.springframework.stereotype.Service;
import java.util.List;

@Service
class ExamService {

  private final ExamRepository examRepo;
  private final QuestionRepository questionRepo;
  private final ResultRepository resultRepo;

  public ExamService(ExamRepository examRepo, QuestionRepository questionRepo, ResultRepository resultRepo) {
    this.examRepo = examRepo;
    this.questionRepo = questionRepo;
    this.resultRepo = resultRepo;
  }

  public Exam createExam(Exam exam) {
    return examRepo.save(exam);
  }

  public List<Question> getQuestions(Long examId) {
    return questionRepo.findAll()
      .stream()
      .filter(q -> q.getExamId().equals(examId))
      .toList();
  }

  public Result submitResult(Result result) {
    return resultRepo.save(result);
  }
}


// 7. Controller Layer
import org.springframework.web.bind.annotation.*;

@RestController
@RequestMapping("/exam")
class ExamController {

  private final ExamService service;

  public ExamController(ExamService service) {
    this.service = service;
  }

  @PostMapping("/create")
  public Exam create(@RequestBody Exam exam) {
    return service.createExam(exam);
  }

  @GetMapping("/questions/{examId}")
  public List<Question> getQuestions(@PathVariable Long examId) {
    return service.getQuestions(examId);
  }

  @PostMapping("/submit")
  public Result submit(@RequestBody Result result) {
    return service.submitResult(result);
  }
}


// 8. application.properties
spring.datasource.url=jdbc:mysql://localhost:3306/online_exam
spring.datasource.username=root
spring.datasource.password=root
spring.jpa.hibernate.ddl-auto=update


// Output:
// /exam/create -> Create exam
// /exam/questions/{id} -> Get exam questions
// /exam/submit -> Submit result

• 1 System for conducting digital exams.
• 2 Manages questions and answers.
• 3 Evaluates student results.
• 4 Built using Spring Boot backend.

• 1 Student management
• 2 Exam management
• 3 Question bank
• 4 Result evaluation

• 1 Admin creates exam
• 2 Students take exam
• 3 Answers submitted
• 4 Results calculated

• 1 Digital assessment system
• 2 Scalable education platform
• 3 Reduces manual evaluation
• 4 Real-time result processing

• 1 Used in school and college exam systems.
• 2 Used in competitive exam platforms.
• 3 Used in training and certification portals.
• 4 Used in HR assessment systems.
• 5 SaaS products use Online Examination System using Spring Boot in services, dashboards, background jobs, and API workflows.
• 6 ERP and banking systems apply Online Examination System using Spring Boot with validation, logging, review, and rollback plans.
• 7 E-commerce and healthcare platforms use Online Examination System using Spring Boot carefully because reliability and data correctness matter.

• 1 A Java program first evaluates the surrounding context, then applies the Online Examination System using Spring Boot rules to the current data.
• 2 The important mental model is input, transformation, result, and failure path.
• 3 In production, the same flow usually sits inside a larger layer such as a controller, service, repository, job, or UI component.

• 1 Choose the simplest implementation first, then measure real workloads.
• 2 Watch for repeated work inside loops, unnecessary allocations, and slow I/O in hot paths.
• 3 Prefer clear data structures and stable APIs before micro-optimizing syntax.

• 1 Treat external input as untrusted until it is validated.
• 2 Avoid hardcoded secrets and never print sensitive values in examples or logs.
• 3 Use established libraries for authentication, encryption, parsing, and database access.

• 1 No timer implementation for exams.
• 2 Missing anti-cheating mechanisms.
• 3 No question randomization.
• 4 Poor result validation logic.
• 5 Skipping the small working example before adding framework code.
• 6 Ignoring null, empty, duplicate, and boundary inputs.
• 7 Mixing business logic, input handling, and output formatting in one place.
• 8 Using broad error handling that hides the real failure.
• 9 Forgetting to test the behavior after refactoring.
• 10 Adding clever code that future maintainers will struggle to read.

• 1 Use timer-based exam sessions.
• 2 Randomize questions and options.
• 3 Implement secure authentication.
• 4 Prevent tab switching cheating (frontend + backend).
• 5 Start with clear requirements and one minimal working example.
• 6 Use meaningful names that explain business intent.
• 7 Keep examples small enough to debug line by line.
• 8 Validate input at every trust boundary.
• 9 Handle errors explicitly and preserve useful context.
• 10 Prefer simple control flow over deeply nested logic.
• 11 Separate domain logic from I/O and framework code.
• 12 Write tests for normal, boundary, and failure cases.
• 13 Review security assumptions before production use.
• 14 Measure performance before optimizing.
• 15 Document non-obvious decisions close to the code or in project notes.
• 16 Use official documentation when behavior is version-specific.
• 17 Keep dependencies current and remove unused code.
• 18 Avoid hardcoded secrets, credentials, and environment-specific paths.
• 19 Log operational events without exposing sensitive data.
• 20 Design examples so learners can safely modify and rerun them.

• 1 Beginner: rewrite the example with different names and values.
• 2 Intermediate: add validation and handle one expected failure case.
• 3 Advanced: place Online Examination System using Spring Boot inside a small service-style design with tests.

• 1 Build a small Java console feature that demonstrates Online Examination System using Spring Boot.
• 2 Accept input, process it with the concept, print a clear result, and handle invalid input.
• 3 Add a README note explaining the design choice and two edge cases you tested.

• 1 If the program does not compile, check spelling, imports, braces, and file/class names first.
• 2 If output is unexpected, print intermediate values and verify each branch of the logic.
• 3 If the design feels complex, reduce it to the smallest working example and add pieces back one at a time.

• 1 Practice Online Examination System using Spring Boot with a second example from a business domain such as inventory, payroll, banking, or e-commerce.
• 2 Review related Java topics that cover data flow, error handling, testing, and clean design.
• 3 Compare your solution with official documentation and simplify anything you cannot explain clearly.