> For the complete documentation index, see [llms.txt](https://synap.ac/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://synap.ac/docs/platform/exams/questions-and-structure.md).

# Questions and structure

Static exams use a defined set of questions. The **Questions**, **EMQ groups** and **Sections** pages let you arrange that content into the paper students will take.

<figure><img src="https://3891068282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWXE6hvHQFtER1a1Dm3l5%2Fuploads%2FppUDP9jcj05OioLCZsJW%2Fsections.png?alt=media&#x26;token=94dac853-5631-455e-8511-80fa386b344a" alt="Exam sections arranged in the editor"><figcaption><p>Sections let you divide a static exam into named parts and control their order.</p></figcaption></figure>

### Questions

The Questions page shows the items inherited from the source quiz and the exam's working order. Review it for:

* missing or unpublished questions;
* accidental duplicates;
* question type and manual-marking requirements;
* available marks and question-level timers;
* media or file dependencies;
* tags used later in result reporting.

You can fine-tune questions in the exam without changing the source quiz. If you later use **Pull latest version** or update the source quizzes, Synap resynchronises the content and can replace those exam-level question and Extended Matching Question (EMQ) group edits. Preview the draft again after pulling changes.

### Sections

Sections divide a paper into meaningful blocks. They can carry their own title, instructions, grades and timer behaviour, and they form boundaries respected by question shuffling.

| Section setting      | What students experience                                            | What to check                                                                             |
| -------------------- | ------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| Name and description | Introduces the block                                                | Use wording candidates will understand under exam conditions                              |
| Question membership  | Determines which items are grouped together                         | Keep blueprint domains and timing needs aligned                                           |
| Order                | Controls the default sequence                                       | Section shuffling can later randomise this order                                          |
| Section timer        | Gives the section its own countdown                                 | Candidates cannot transfer unused time unless the assessment design explicitly permits it |
| Section grades       | Produces section outcomes                                           | Validate both overall and section pass rules                                              |
| Soft sections        | Lets candidates review a submitted section without changing answers | Reduces confusion while preserving the section lock                                       |

{% hint style="warning" %}
Section timers change the failure mode of an exam. A candidate who spends too long in one section cannot recover that time in another. Use them only where separate timing is part of the assessment design, and explain the transition clearly in instructions.
{% endhint %}

### Question and section shuffling

Question shuffling randomises questions while maintaining EMQ grouping and respecting section boundaries. Section shuffling randomises the sections themselves. Option shuffling is configured separately in Candidate experience.

Question, option and section shuffling are separate choices. Preview the paper with each enabled setting so you can see exactly what changes for students.

### Extended Matching Question groups

An EMQ group shares a scenario or option list across related questions. Synap keeps the group together when shuffling questions. Check that:

* the shared stem and option list make sense without outside context;
* every linked question belongs to the intended group;
* shuffling individual options is compatible with the question design;
* marks and feedback are correct for each question, not only the group.

### Static versus dynamic structure

This page applies directly to static exams. In dynamic exams, filter rules select questions at attempt generation time. Sections and EMQ behaviour still matter, but the final paper must be tested by generating multiple representative attempts rather than previewing a single fixed list.

### Preview the paper

Generate or preview the paper at least once for every relevant combination of:

* standard and access-arrangement timing;
* shuffled and unshuffled content;
* section timers and overall timers;
* automatic and manual-marked question types;
* desktop, browser extension or no-install delivery where proctoring is enabled.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://synap.ac/docs/platform/exams/questions-and-structure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
