Random numbers: range, repetition and order are different choices
Selecting practice questions or activity tasks needs clear rules before numbers are generated. “Random” alone does not say whether repeats are permitted or whether both boundaries are included.
Count the available values first
With inclusive integer bounds, the number of available values is maximum minus minimum plus 1. The range 10 through 15 contains 6 values, not 5.
A no-repeats selection cannot contain more results than the available values. Widen the range or reduce the requested count rather than expecting a seventh different number from six possibilities.
Repetition and sorting answer different questions
Drawing with replacement permits a number to appear again. Preventing repeats within one list does not prevent a later, separate list from containing the same number.
Ascending sorting only changes positions. Its first result is the smallest value, not necessarily the first drawn. Keep draw order when priority matters.
Strong randomness is not a complete audit trail
The tool uses the browser’s cryptographic random source. That supports value generation, but is not independent evidence of how a contest was run or who was eligible.
An activity involving prizes or rights needs appropriate participation rules and a documented process. A small sample need not look perfectly balanced; repeatedly redrawing until it looks appealing is not the same as keeping the original draw.
References: MDN Web Docs — Crypto.getRandomValues()
Example: choose 5 question numbers from six possibilities
Within 10 through 15, an illustrative no-repeats list is 14, 10, 15, 12, 11. Every value is distinct and within range. The absence of 13 in this particular sample does not indicate a problem.
Sorting gives 10, 11, 12, 14, 15 without a new draw. Requesting 7 distinct numbers from that range is impossible. This is an explanatory sample, not promised output or proof of a contest’s fairness.