Effective Study Techniques for the Blockchain CBSA Exam

The hash of the previous block is written to the header of the current block

The ID of the previous block is stored in the current block

A public key is stored in each block for data decryption

The hash of the genesis block is kept in all block headers

1. User uses Dapp/web3 to start transaction2. User signs the transaction with their private key3. Transaction validated on locally running node4. Transaction broadcast to entire network5. Miners choose to accept or pass on the transaction6. Miner takes each accepted transaction and writes it to the current block

1. User uses Dapp/web3 to start transaction2. Transaction broadcast to entire network3. If accepted by the network, user signs transaction with private key4. Miners choose to accept or pass on the transaction5. Miner takes each accepted transaction and writes it to the current block

Both of these ordering sequences can occur

None of the above

Centralization is to be avoided

Databases should never be used over blockchain

Full history is needed for all data

High performance is required

Centralization of blockchain control

Only use case for computational power is blockchain

Large expenditures for computational power

Not profitable for miners

51% attack mitigation

Business logic

Business Requirements

Integration

Accessibility

Security

They cannot be deleted

Filing a request with the Ethereum Foundation

Recalling the transaction of Etherscan.io

Deleting the transaction from the app that sent it

Use a template from AWS

Audited Implementation

Start a new one

Copy from existing token

Each blockchain software specifies its own data storage rules

Any data that is within the UTC-8 standard

Unencrypted textual and numerical data

Encrypted textual and numerical data

RSA

AES

MD5

PGP

FALSE

TRUE