5 exercises — choosing between vague quantifiers (some/several/many/most) and precise forms (all/none/at most/at least/approximately/99%) in API documentation, SLOs, and technical specifications.
0 / 5 completed
1 / 5
An SLO document states: "The API must respond within 200 ms for _____ requests under normal load." Which quantifier is most appropriate for a formal SLO?
Option D is correct. In SLOs (Service Level Objectives) and SLAs, precise numeric quantifiers ("99% of", "99.9% of") are required. Vague quantifiers like "most", "many", or "the majority of" cannot be monitored, measured, or enforced. Technical specifications for availability, latency, and throughput require numeric precision: "99th percentile", "at most 200 ms", "no fewer than 99.9% of requests". The choice between quantifiers in technical specifications is not stylistic — it is a measurement and contractual precision decision.
2 / 5
A code comment reads: "This function is called _____ when processing large batches." Which option is most precise and informative for a technical audience?
Option C is correct.Precise quantification ("approximately 1,000 times per second at peak load") is more useful than vague frequency adverbs in technical documentation. Code comments that explain performance-critical call patterns help engineers make informed decisions about optimisation. "Frequently" and "several times" are acceptable in prose but provide no actionable data. When documenting hot paths, call frequency, or resource usage, prefer measured values with context ("at peak load", "under normal conditions"). "Approximately" signals the value is an estimate, which is honest and appropriate.
3 / 5
An API rate-limiting policy states: "Clients may make _____ 100 requests per minute." Which quantifier correctly expresses an upper limit?
Option B is correct."At most" is the correct technical quantifier for expressing an upper bound or maximum limit: "at most 100 requests per minute" means the limit is 100 — clients may make fewer but not more. "At least" (option C) expresses a minimum/lower bound — the opposite meaning. "Approximately" and "roughly" (options A and D) signal estimates, not enforced limits — inappropriate for rate-limiting policies that are contractual. In API documentation, SLOs, and specifications, use "at most/at least/no more than/no fewer than" for precise boundary conditions.
4 / 5
A system health dashboard description reads: "_____ of our data centres are currently operating within normal parameters." Which quantifier conveys the strongest reassurance about coverage?
Option D is correct."All" is the universal quantifier — it asserts 100% coverage and provides the strongest possible assurance. In a status dashboard context, "all data centres are operating normally" is the most reassuring and precise statement. The quantifier hierarchy in terms of reassurance: all > most/the majority of > several > some > a number of. In technical status communications (incident updates, service status pages), quantifier choice directly affects user confidence — precision matters. If "all" is not accurate, use a specific number: "4 of 5 data centres".
5 / 5
A performance benchmark report states: "Response times ranged from 45 ms to 312 ms, with _____ results falling between 80 ms and 150 ms." Which quantifier best describes a statistical majority in a formal report?
Option C is correct."The majority of" is the most formal quantifier for reporting a statistical plurality in a benchmark report. It clearly implies more than 50% of results and is appropriate for technical and executive-level reporting. "Most" (option D) is a valid synonym but is slightly less formal. "Many" (option B) is more ambiguous — it does not necessarily imply a majority. "Lots of" (option A) is informal and should never appear in benchmark reports. For maximum precision in reports, pair "the majority of" with a specific percentage: "the majority of results (73%) fell between 80 ms and 150 ms."