How the Lessons and Questions Are Made · Certify
certify.courses

How it's made

How the lessons and questions are made

Every chapter and every practice question on this site comes from the same short process. This page is that process, end to end, plus the form for reporting a question that looks wrong.

Sources: official material only

Three kinds of source, and nothing else:

  1. The official exam guide for the exam version currently being delivered. It sets the domains, their weights and the objectives, and it decides which chapters exist. Each course home names the guide version it is aligned to and the date it was last checked.
  2. The vendor's own documentation for how a feature actually behaves, its defaults and its limits.
  3. Release notes, because renames and new defaults land there first, often months before the exam guide catches up.

No third-party question banks, no forum recollections of "what was on my exam", no dumps. If a fact cannot be traced to one of the three sources above, it does not go in.

The Learn, Recall, Reason loop

A chapter is a run of eight to twelve cards, each one a single screen, and the cards come in three kinds:

  1. Learn.One concept, one diagram that builds up as you tap, and the trade-off the vendor is steering you toward.
  2. Recall.A short check that you kept the fact: a default, a limit, a name.
  3. Reason.A scenario with one best answer and three plausible distractors, followed by an explanation of why the correct option wins and why the most tempting wrong one loses.

Each unit closes with a timed practice exam in the same scenario style, and the course-level Practice hub turns those pools into five-question drills, domain focus sessions, a readiness check and, where they exist, full-length timed mocks drawn from a sealed pool that the drills never touch.

Terminology rules

Every course carries a written list of terms to use and terms to avoid, checked before anything ships. The Lakeflow rename is the example that shows why. Databricks renamed Delta Live Tables to Lakeflow Spark Declarative Pipelines, and the November 2025 Data Engineer Professional exam guide uses only the new name. So the Professional course says "Lakeflow Spark Declarative Pipelines" every time and never "Delta Live Tables" or "DLT", because the exam will not say them either. In the same course, Liquid Clustering is the recommended layout and partitioning or Z-Order appear only as the contrast case, again because that is how the current guide frames them.

The AWS courses have the mirror-image rule. Prose says "Amazon Data Firehose" and "Amazon Managed Service for Apache Flink", the current names, while IAM policies and CLI samples keep firehose:* and kinesisanalyticsv2, because the identifiers never changed and a question can hinge on that split.

Validation before anything ships

A lesson or exam is not published until an automated check passes on the file itself. It fails a lesson that has more or fewer than one correct answer on a quiz card, a missing explanation, a step-built diagram with gaps in its sequence, a cover illustration that does not animate, any animation that ignores the reduced-motion setting, a "next chapter" link that disagrees with the course index, or an em dash anywhere in the copy. It fails an exam whose answer letters bunch up, that skips a chapter in scope, or whose explanations do not cover both the correct answer and the top distractor. A second check runs on every change to the site and fails any page whose links or canonical URL are in the wrong form.

Frozen courses and errata

Once a course is released, its lessons and exams are frozen. They are not edited in place, so a chapter you studied last month reads the same when you go back to it and a question you drilled is not quietly rewritten under you. Corrections ship as errata: the fix is listed here with the chapter or question it applies to, and the next version of the course carries it. A course is only re-cut as a new version when the vendor publishes a new exam guide, which is also when the "last verified" date on the course home moves.

Errata

No errata are open. Anything confirmed through the form below appears here.

Report a question

Think a question is wrong, has two defensible answers, or is out of date against the current docs? Say so here. Include the question ID if you have it (the practice hub shows it next to the Report link), or paste the question text.

Only used to reply about this report.

Prefer email? Support and contact has the address.