What to Expect on the CBE Exam
The CBE exam itself is less intimidating than its name suggests, and that’s worth saying plainly before anything else. It’s a 100-mark, multiple-choice test taken entirely in your browser — no lockdown software, no webcam proctoring to fuss over. Blockchain Council sets the bar at 60 marks to pass, and gives you a one-hour window to get there. You’ll see a mix of single-answer and multi-answer MCQs, pulled from the same ground covered in the self-paced training modules.
Don’t mistake “easy format” for “no studying required,” though. A meaningful share of the questions are scenario-based — you’re given a short business situation (a supply chain dispute, a cross-border payment delay, a dispute over transaction finality) and asked which blockchain property or mechanism actually resolves it. That’s a different skill than memorizing that “a block contains a hash, a timestamp, and transactions.” You need to recognize the concept wearing a business-problem costume.
If you don’t clear it on the first attempt, Blockchain Council allows up to three attempts total, with a mandatory 24-hour wait between tries. That’s a reasonable safety net, but it’s not a substitute for going in prepared — people who treat the first attempt as a “see what’s on it” dry run often regret the wasted week waiting to retake.
Domain Breakdown
This is where candidates researching CBE run into a wall: Blockchain Council does not publish an official weighted domain breakdown for this exam. Several independent reviewers who’ve taken it confirm the same thing — there’s no published bifurcation of how many questions come from which module. What we can tell you, based on the current published curriculum, is which topic areas the training (and therefore the exam pool) draws from:
Module Area | What It Covers | Published Weighting |
|---|
Blockchain Origins & Fundamentals | History, decentralization, why blockchain exists | Not published by Blockchain Council |
Tokenization | Fungible vs. non-fungible assets, tokenizing -world value | Not published by Blockchain Council |
Blockchain Ecosystem | Nodes, networks, public/private/consortium models | Not published by Blockchain Council |
Mining & Consensus Mechanisms | Proof of Work, and “other consensus mechanisms” beyond PoW | Not published by Blockchain Council |
Transaction Models | UTXO vs. account-based models | Not published by Blockchain Council |
Security & Privacy | Cryptographic basics, attack vectors, privacy trade-offs | Not published by Blockchain Council |
Enterprise Use Cases | Industry applications and implementation steps | Not published by Blockchain Council |
Because there’s no stated weighting, the safest prep strategy is to treat every module as fair game rather than guessing which section “matters more.” Our practice sets are built across all of these areas in roughly equal proportion for exactly that reason.
The Topics Candidates Consistently Underestimate
Two things trip people up more than anything else on this exam.
First, the UTXO vs. account-based model distinction. It sounds like trivia — Bitcoin uses one, Ethereum uses the other — but the exam likes to test whether you understand why it matters: double-spend prevention, how balances are tracked, and what it means for transaction privacy and parallel processing. Candidates who only memorized “Bitcoin = UTXO” without understanding the mechanics get caught by scenario questions that don’t name the chain explicitly.
Second, consensus mechanisms beyond Proof of Work. The course module is literally titled “Other Consensus Mechanisms,” which is a signal in itself — Blockchain Council clearly wants you to know Proof of Stake, and ideally have a working sense of alternatives like delegated or Byzantine fault-tolerant variants, not just PoW mining mechanics. If your only mental model of consensus is “miners solve puzzles,” you’ll stumble on any question that doesn’t involve mining at all.
A smaller but recurring trap: distinguishing a true multi-answer MCQ from a single-answer one mid-exam. A few test-takers in public reviews have noted losing marks simply from selecting only one option on questions that required more than one correct answer — a format quirk worth being mentally ready for, not a knowledge gap.
How to Use Practice Tests Effectively for CBE Exam
Because the exam leans on scenario interpretation rather than pure recall, drilling flashcard-style definitions alone won’t get you far. When you work through our practice questions, read the scenario setup fully before jumping to the options — the exam rewards people who can translate “a logistics company wants to verify a shipment without trusting a central registry” into “they need a permissioned or consortium chain with consensus-based validation,” not people who just spot a keyword and pattern-match.
Given the one-hour time limit across 100 marks, pacing matters more than it might seem for an exam this size. Run at least one full practice set under a strict one-hour clock before your attempt, so you’re not discovering your pacing problems for the first time with points on the line.
Also use practice tests to catch the multi-select trap mentioned above — deliberately notice, question by question, whether it’s asking for one answer or several, until checking that becomes automatic.
Common Mistakes That Cause Retakes
Treating the training video as sufficient without active review. Several candidates who passed comfortably describe watching the full module set once and then relying on general blockchain familiarity — that works for people who already had some crypto exposure, but it’s a weak strategy if blockchain concepts are genuinely new to you.
Skipping the “Security and Privacy” module mentally. It’s a short section in the curriculum, which leads people to assume it’s a short section on the exam. There’s no evidence that’s true, and it’s an easy module to under-review.
Not reviewing wrong answers between attempts. With a mandatory 24-hour wait before a retake, that’s a full day you could spend diagnosing exactly which concepts cost you marks instead of just re-watching everything from the start.
Rushing because the exam “only takes most people 15 minutes.” That’s a anecdote from past test-takers, but it describes people who already knew the material cold. Going in assuming you’ll finish in a quarter of the allotted hour, and then panicking when question three stumps you, is a self-inflicted problem.
CBE Study Timeline by Starting Experience Level
Complete beginner to blockchain: Budget the full 6–10 hours of training content plus 3–4 additional hours of outside reinforcement (articles or videos on consensus mechanisms and tokenization specifically) before attempting the exam. Rushing this group’s timeline is the single biggest driver of first-attempt failure.
Has adjacent experience (crypto trading, fintech, general IT): You can likely compress this to one focused pass through the training modules — treat it as filling gaps rather than learning from zero — plus a practice-test session or two to confirm you’re not missing blockchain-specific terminology that overlaps confusingly with general fintech language.
Retaking after a failed attempt: Don’t restart the whole course. Isolate which module areas your wrong answers clustered around (the explanations in a good practice set will show you this), spend your mandatory 24-hour wait reviewing just those, and go back in. Candidates who retake blind, without this diagnosis step, tend to repeat the same mistakes