BLOCKCHAINF EXIN Blockchain Foundation Exam Topics and Questions

At 38% of the exam, this topic is where the test is won or lost. The domain covers the mechanical reality of how a blockchain operates: the data structures, the participants, the cryptographic glue, and the rules by which nodes agree. If you are soft on any of those four areas, you will feel it across multiple items. Get the mechanics right here and every later topic becomes easier to reason through.

– How a blockchain is built and who participates

A blockchain is a chain of blocks where each block references the one before it through a hash. That referencing is what makes tampering detectable, and understanding exactly why is what the exam tests. A node is any participant that holds a copy of the chain and enforces its rules. The exam asks you to distinguish what different node types actually do, not just that they exist. Tokens represent value or rights on the chain, and the exam expects you to say what they represent in a given context. The distinction between public, private, and hybrid blockchains comes up in scenario-style items: a public chain is permissionless, a private chain restricts who can participate, and a hybrid sits between them. Knowing the label is not enough; you need to match the right type to a described situation and explain the trade-offs each carries.

– Cryptography, keys, hashes, ledgers, and mining

Cryptography is the mechanism that makes a blockchain trustworthy without a central authority. Private and public keys work as an asymmetric pair: the private key signs a transaction, the public key lets anyone verify that signature. Confusing which key does which job is a common source of errors. Hashes serve two purposes simultaneously: they fingerprint data and they chain blocks together, so altering any block breaks every subsequent hash. The ledger is the shared record of all transactions; its distributed nature means no single party controls it, and that property drives most of the use-case reasoning you will do in later topics. Mining is the process by which new blocks are added under proof-of-work consensus, and it is worth distinguishing from the validation role that nodes play in non-mining consensus models.

– Consensus algorithms and their trade-offs

Consensus is the mechanism by which a network of untrusting nodes agrees on a single version of the ledger. The exam asks you to recognise consensus types from a description, so you need to know what each one looks like in practice, not just its name. Proof of Work requires computational effort and makes attacks expensive but consumes energy. Proof of Stake ties influence to held value rather than computation. Delegated variants and Byzantine Fault Tolerant approaches each make different assumptions about the honesty of participants and the speed of finality. The advantages-and-disadvantages question is explicit in the syllabus, which means you should be ready to weigh throughput, energy cost, centralisation risk, and finality speed against each other for whichever algorithm a scenario describes. A candidate who can only name algorithms, but cannot say what breaks under each one, will drop marks here.

How 1 Blockchain Basics is tested

With 38% of the exam sitting here, you will see more items from this topic than from any other. The items are a mix of definitional recall and applied reasoning. Recall items ask you to identify what a hash does, what a node's role is, or what distinguishes a private from a public chain. Applied items give you a scenario and ask which blockchain type fits, or which consensus algorithm has a named disadvantage. The trap on definitional items is that the options are often close: a hash and a digital signature both involve cryptography, but they do different jobs. The trap on consensus items is that candidates memorise names without memorising what breaks. Items reward precision: the strongest option names the mechanism and its consequence, not just the concept. Mining questions reward knowing that mining is specific to certain consensus models, not universal to all blockchains. Keys questions reward knowing which key is used at which end of a transaction.

Where the previous topic built the technical picture of how a blockchain works, this one asks what can go wrong with it. The domain covers vulnerabilities in the technology itself, the human and community risks that can destabilise a chain, and the mechanisms that push back against those risks. At 17%, it is a meaningful slice, and candidates who treated it as light reading often find themselves uncertain on items that require them to connect a risk to its mitigation.

– Vulnerabilities, community fractures, and fraud

Technical vulnerabilities in a blockchain include attack vectors that exploit the consensus mechanism or the network's node distribution. The 51% attack is the canonical example: if one entity controls the majority of a network's consensus power, it can rewrite recent history. The exam expects you to identify vulnerabilities from a description, so you need to recognise the conditions that make an attack feasible, not just its name. Community fractures are a different category of risk. When participants disagree on protocol changes, a chain can fork, splitting the network and its history. Forks can be contentious or cooperative, and the exam asks you to identify what risk a fracture poses rather than narrate blockchain history. Fraud and scams operate at the application layer: phishing for private keys, fake token sales, and exit scams are real threats that the technology alone does not prevent. Knowing that the chain is immutable does not mean that what is written on it is honest.

– Mitigating risk through blockchain elements and public witnesses

Risk mitigation in this context means using the features covered in Topic 1 to limit exposure to the threats covered above. Cryptographic signing makes it hard to impersonate a participant; hashing makes tampering detectable; distributed ledgers remove single points of failure. The exam asks you to connect a specific mitigation to a specific risk, so rote recall of features is not enough. The public witness concept is the one most candidates under-prepare. A public witness is an external party that attests to events on the chain, adding a layer of verification that is independent of the chain's own participants. Its role matters in scenarios where the chain's own participants have a conflict of interest. Items in this area reward knowing what the public witness does that internal consensus cannot, and why that distinction matters in a given context.

How 2 Blockchain Challenges is tested

Items here tend to be scenario-based. You are given a situation describing a network condition, a community dispute, or a fraudulent act, and asked to identify the risk or name the appropriate mitigation. The difficulty is that the options often pair a real risk with a plausible-sounding but wrong mitigation, or vice versa. Items reward matching the category of threat to the category of control: a technical vulnerability calls for a technical control, a community risk calls for governance awareness, a fraud risk calls for user-level vigilance or cryptographic verification. The public witness question is almost always framed as a scenario where you must decide what role it plays, so candidates who only know the definition without understanding the function will lose that mark. Watch for items that use the blockchain elements from Topic 1 as answer options: the exam tests whether you can apply those elements in a risk context, not just recall them in isolation.

After the mechanics and the risks, the exam shifts to what blockchain technology is actually used for. At 33%, this is the second-largest topic, and its breadth is what catches candidates off guard. The sub-topics span cryptocurrencies, smart contracts, decentralised applications, identity, IoT, AI, supply chains, and cross-border payments. The exam does not go deep on any one of them, but it does expect you to reason about which blockchain capability fits which real-world problem.

– When a blockchain is useful and how cryptocurrencies work

Knowing when a blockchain adds value is a judgement call the exam asks you to make explicitly. The key question is whether a use case actually benefits from a distributed, immutable, trustless ledger, or whether a conventional database would do the job better. Scenarios that involve multiple untrusting parties, a need for audit trails, or the removal of intermediaries tend to favour blockchain. Scenarios with a single trusted authority, a need for frequent updates, or high throughput requirements often do not. Cryptocurrencies are the most visible blockchain application, and the exam expects you to explain how they function as a medium of exchange on a blockchain, including the role of wallets, addresses, and transactions. Identifying which blockchain network underlies a described scenario, and differentiating between networks by their properties, is also tested here.

– Smart contracts, DApps, and DAOs

Smart contracts are self-executing agreements written in code and stored on a blockchain. Their defining property is that they run automatically when conditions are met, without requiring a trusted intermediary to enforce them. The exam asks you to explain their use, so you need to know what they enable, not just what they are. Decentralised applications, or DApps, sit on top of smart contracts and expose their logic through a user interface. The distinction between a DApp and a conventional application is that a DApp's back-end logic runs on the blockchain rather than on a server controlled by one party. Decentralised Autonomous Organisations, or DAOs, take this further by encoding governance rules into smart contracts, so that decisions about how an organisation operates are made by token holders through on-chain voting rather than by a central board. The exam groups DAOs with sophisticated smart contracts, and items reward knowing how the two concepts relate.

– Identity, IoT, AI, and decentralised marketplaces

Blockchain-based identity applications give individuals control over their own credentials without relying on a central identity provider. The exam asks you to describe possible applications in this area, so you need to understand what the blockchain property of self-sovereignty enables rather than name specific products. Combining blockchain with IoT means that sensor data can be written to an immutable ledger, which is valuable where the provenance or integrity of that data matters. Combining blockchain with AI is less mature, but the exam asks you to identify the possibilities, which is a lower bar than explaining a working implementation. Decentralised marketplaces and exchanges let buyers and sellers transact directly, with smart contracts replacing the escrow or settlement functions that a centralised platform would otherwise provide. Items here ask you to identify what the blockchain contributes to the marketplace model.

– Supply chains and cross-border money transfers

Supply chain is one of the most-cited enterprise blockchain use cases, and the exam reflects that. A blockchain in a supply chain creates a shared, tamper-evident record of a product's journey from origin to end customer. Every participant, whether a manufacturer, shipper, or retailer, can verify the record without trusting any single other party. Items ask you to describe the role a blockchain plays, so the answer should point to transparency, traceability, and the elimination of paper-based reconciliation. Cross-border money transfers are another area where blockchain removes intermediaries. Traditional correspondent banking is slow and expensive because it routes payments through multiple institutions. A blockchain-based transfer can settle directly between parties in a fraction of the time and cost. The exam expects you to describe that role at a conceptual level, not to name specific payment networks or quote settlement times.

How 3 Applications of a Blockchain is tested

The breadth of this topic means items span a wide range of scenarios. Most are applied: you are given a business situation and asked to identify which blockchain application fits, which technology is being described, or whether a blockchain is even the right tool. The trap is that many scenarios could plausibly involve blockchain, and the item rewards the candidate who can identify the specific property that justifies the choice, not just the candidate who recognises a blockchain keyword. Smart contract and DApp items reward knowing the boundary between on-chain logic and off-chain interface. DAO items reward knowing how governance is encoded. Supply chain items reward knowing what the shared ledger solves, not just that blockchain is used in supply chains. Candidates lose marks by giving generic answers that would apply to any distributed system. The strongest option in each item points to the specific blockchain property that makes the application work in the described context.

The final topic looks at where blockchain technology is heading rather than where it already is. At 12%, it carries the smallest share of the exam, but it is not a throwaway section. The items here test whether you can reason about emerging and speculative applications across banking, insurance, intellectual property, government, and internet infrastructure. The challenge is that the concepts are less settled than those in earlier topics, so the exam focuses on what blockchain could change rather than what it has already replaced.

How 4 Blockchain Innovations is tested

Items in this topic tend to ask what blockchain enables in a given sector, rather than how a specific technology works. Digital fiat currency items reward knowing how a central-bank-issued digital currency differs from a decentralised cryptocurrency in terms of control and trust. Insurance items reward understanding that smart contracts can automate claims processing by triggering payouts when verifiable conditions are met. Intellectual property items reward knowing that an immutable ledger can establish provenance and timestamp creation, which matters in disputes over ownership. Government items reward knowing which public-sector functions benefit from a transparent, auditable record. Email and internet trust-layer items are the most conceptual: they reward understanding that blockchain can provide a decentralised attestation layer rather than relying on certificate authorities. Candidates lose marks by over-specifying, naming features that belong to other topics rather than focusing on the sector-level change the item describes. The strongest options explain the mechanism of change, not just the fact that change is possible.