Admin access

[
  {
    "type": "mcq",
    "question_text": "Which is the largest planet in the Solar System?",
    "options": ["Earth", "Jupiter", "Saturn", "Neptune"],
    "correct_option": 1,
    "detailed_solution": "Jupiter is the largest planet by both mass and volume.",
    "difficulty": "easy"
  },
  {
    "type": "statement",
    "question_text": "Statement 1: ... \nStatement 2: ...\nWhich is/are correct?",
    "options": ["Only 1", "Only 2", "Both", "Neither"],
    "correct_option": 2,
    "detailed_solution": "Both statements are correct because…",
    "difficulty": "medium"
  },
  {
    "type": "table",
    "question_text": "Who scored the highest total?",
    "table_data": {
      "headers": ["Student", "Maths", "Science"],
      "rows": [["A", "72", "65"], ["B", "60", "78"]]
    },
    "options": ["Student A", "Student B", "Student C", "Student D"],
    "correct_option": 1,
    "detailed_solution": "B's total is 138, the highest here.",
    "difficulty": "medium"
  }
]

These fields exist in your database and are enforced exactly as your schema defines them:

• type must be mcq, statement, or table (defaults to mcq if left out).
• options must be an array of exactly 4 strings, every time, for all 3 types.
• correct_option must be an integer 0–3 — the index into options.
• detailed_solution is required — your DB doesn't allow a question without one.
• difficulty must be easy, medium, or hard (defaults to medium).
• table_data is required when type is "table", and ignored otherwise — it's { "headers": [...], "rows": [[...], ...] }, not an array of strings like options.

The subject/topic/quiz name and description come from the form above, not the file — the file is only ever this one flat list of questions.