Home / Methodology

Our methodology

A transparent walkthrough of where our questions come from, how we map them to official exam blueprints, and the editorial checks that happen before a question lands on the site.

Catalog snapshot: question pool last refreshed May 3, 2026 — 622 questions across 71 tests, 20 categories, drawn from Open Trivia Database plus original items. This figure updates whenever we run a catalog refresh; it is a whole-catalog count, not a per-test date (see "What we explicitly do not do" below for why we do not date individual tests).

Question sources

Exam Edge Hub does not invent questions in a vacuum, and we do not republish leaked exam content. Our practice items are drawn from a curated set of publicly accessible educational sources and supplemented with original items written by subject matter reviewers against the published exam blueprints.

The primary public source we draw from is the Open Trivia Database (opentdb.com), an openly licensed pool of multiple-choice items spanning science, technology, mathematics, geography, and general knowledge. We map relevant subsets of that pool into the technical knowledge categories on this site — for example, items in the "Science: Computers" trivia category map cleanly into the foundational concepts tested on CompTIA A+ and Network+. We supplement this with items written from scratch by our own contributors against the official exam objectives published by each certifying body.

For many tracks a public question pool does not exist (NCLEX, Praxis, Series 7, CPA, real estate licensing, most trade licenses). Where a track-specific question set is not yet available, drill pages currently pair track-specific study notes with a scored quiz drawn from our general practice pool — those quizzes are clearly labeled on the page and are not blueprint-specific. Track-specific sets are being built out over time.

Blueprint mapping

Track-specific practice items are tagged to objectives in the official exam blueprint published by the relevant certifying body; general-pool quizzes are not blueprint-mapped and are labeled as such. The blueprint is the authoritative document that describes what the exam covers and how heavily each topic is weighted. We re-validate the mapping any time a certifying body publishes a new exam version.

For track-specific sets, tagging is a manual editorial step, not an automated keyword match, because blueprint objectives often share terminology with adjacent objectives in subtle ways. For example, a question that mentions "subnetting" might map to the "Networking Fundamentals" objective on Network+ or to the "Network Architecture" objective on Security+ depending on what the question stem is actually asking. The reviewer makes the call.

Difficulty calibration

Each question carries a difficulty tag of easy, medium, or hard. These are not arbitrary — they correspond to the rough mix you should expect on the real exam: roughly 25% easy items that test recognition of vocabulary and core facts, roughly 50% medium items that test the application of a concept to a brief scenario, and roughly 25% hard items that test analysis, comparison, or troubleshooting across multiple concepts. Within track-specific practice sets, the mix of easy/medium/hard is chosen to approximate the published distribution for the corresponding real exam.

Editorial review

Track-specific practice sets go through three editorial checks before publication:

  • Answer key verification. A second reviewer confirms the correct answer and the rationale for why the distractors are wrong. If the second reviewer disagrees with the first, the item is returned for revision or pulled.
  • Currency check. The reviewer confirms that the question is consistent with the current published version of the exam. Items that reference deprecated services, retired protocols, or repealed regulations are flagged and rewritten.
  • Bias and clarity check. The reviewer reads the stem aloud and checks for ambiguous wording, double negatives, and culturally specific references that would unfairly disadvantage a non-native English reader. We aim for the same plain, neutral, scenario-driven prose used on the real exams.

What we explicitly do not do

We do not republish leaked exam content. So-called "brain dumps" — sites that publish memorized or screenshotted questions from current live exam pools — violate the terms and conditions of every major certifying body and, in many jurisdictions, expose the user to certification revocation if the use is detected. We do not link to brain dump sites, do not source content from them, and ask that you not use them.

We do not predict the exam. A passing score on our practice tests is a strong signal that you have prepared well. It is not a guarantee that you will pass the real exam, and a failing score on our tests does not guarantee that you will fail the real exam. The exam is the exam.

We do not customize practice tests by user. Every visitor sees the same library of tests with the same questions in the same order. We made this choice deliberately: it keeps the site fast, it keeps your data minimal, and it makes it possible to take a test, share the link with a study partner, and compare results without an account.

How we update the catalog

The catalog is reviewed quarterly. During each review, we re-check every category page against the certifying body's current published blueprint, retire questions that reference deprecated material, and add new items in domains that have grown in weight on the real exam. When a certifying body publishes a major new version of an exam (a meaningful change to the blueprint, not just a minor edition update), we publish an article on the blog describing what changed and how our coverage has updated.

Reporting an issue with a question

If you spot a wrong answer key, an outdated reference, or a question that no longer matches the current blueprint, please email corrections@examedgehub.com with the URL of the test page, the question number, and a brief note about the issue. Corrections are typically pushed within 48 hours and the contributor who flagged the issue is credited (with permission) on the blog.