Written from published material, and corrected in public
Rubric publishes 123 lessons across 4 certifications. This page explains where the material comes from, how it is checked, and what has been fixed since it went up.
Where the material comes from
Exam facts come from the vendor. Domains, weightings, task statements, item counts, duration and passing scores are transcribed from the published exam guide, and each exam page carries the date it was last checked against that guide.
Explanations come from primary documentation. Every lesson is written against the vendor’s own product documentation and engineering write-ups, and lists the pages it was checked against at the bottom. Where the documentation and the exam guide disagree — products move faster than exam guides do — the lesson says so and tells you which to answer with.
Nothing comes from an exam, or from anyone else’s question bank. Rubric does not use recalled exam content, does not accept it, and does not copy questions from other preparation sites. Practice questions are written for the objective they teach.
How a lesson is checked before it goes up
- Sourced. The claims a lesson needs are listed first, then read from the vendor’s documentation. Anything that cannot be verified is left out rather than guessed.
- Validated. An automated check runs on every lesson: the task statement must match the published blueprint word for word, every practice question must have exactly as many correct answers as it claims, every option must carry a written explanation, and no source may come from a third-party question bank.
- Looked at. Each page is rendered and read before publication, so diagrams and examples are checked as they appear, not as they were intended.
- Dated. Each lesson shows when it was last checked. A page that has not been re-checked says so rather than implying freshness.
Review status, stated plainly
Lessons are drafted with AI assistance and checked against the sources listed on each page. Where a lesson has been reviewed by someone who holds the certification, the page says so. Where it has not, the page says that too, at the end, next to the sources. We would rather tell you than let you assume.
Corrections
Every fix to something that was wrong, and every substantial change, newest first. Spotted something? Write to support@rubricedu.com with the page and what looks off. Corrections are made, dated and listed here.
- ChangePractice questions
Added a practice quiz for every exam domain, built from the questions already published in the lessons and scored in the browser. Labelled practice, not mock exams: their answers appear on the lesson pages.
Two ways of explaining the same decision — one to an engineering lead, one to a COO — were shown in red and green, which implied the first was wrong. Both are valid; the colours now say so.
- CorrectionCCAR-F 1.5 — Agent SDK hooks
The example hook compared the tool name to a bare name, but custom SDK tools are namespaced, so the hook as written would never have fired. The example now matches the full tool name.
- CorrectionCCAR-F 1.5 — Agent SDK hooks
A sample Unix timestamp in the normalisation example did not match the ISO date beside it. Both now refer to the same moment.
A table said a subagent never carries anything over from its earlier runs. That is true of a fresh spawn but not of a resumed session, and the row now says so.
- ChangeEvery lesson
Lessons gained diagrams, worked examples and a plain-language opening, and each one now names the documentation pages it was checked against.