CBSA Blockchain Network Architectures 2

Question 1

In a federated blockchain network, who typically controls the consensus process?

Accepted Answer

A pre-selected group of nodes

Answer

A single central authority

Answer

Any node that joins the network

Answer

The node with the most computing power

Question 2

Which network topology is most resilient to single-node failures in a blockchain peer-to-peer network?

Accepted Answer

Mesh topology

Answer

Star topology

Answer

Bus topology

Answer

Ring topology

Question 3

What distinguishes a 'sidechain' from the main blockchain network?

Accepted Answer

It is a separate blockchain pegged to the main chain for specific use cases

Answer

It uses a different hash algorithm

Answer

It is an offline backup of the main chain

Answer

It is a chain with fewer validators

Question 4

In Hyperledger Fabric, what is the role of the 'orderer' node?

Accepted Answer

It sequences transactions into blocks and distributes them

Answer

It validates smart contract execution

Answer

It manages wallet keys for participants

Answer

It stores the world state database

Question 5

Which characteristic best defines a 'permissioned' blockchain network architecture?

Accepted Answer

It restricts participation to identities that have been granted access

Answer

It requires payment to participate

Answer

It limits the number of blocks that can be created

Answer

It prevents smart contract deployment

Question 6

What is the primary purpose of a 'bootnode' in an Ethereum network?

Accepted Answer

It helps new nodes discover and connect to peers in the network

Answer

To mine the first block in the chain

Answer

To store the genesis block configuration

Answer

To broadcast transactions to all nodes

Question 7

In a multi-cloud blockchain deployment, what is the main architectural challenge?

Accepted Answer

Ensuring data sovereignty and consistent latency across cloud providers

Answer

Generating enough hash power

Answer

Preventing duplicate token creation

Answer

Synchronizing smart contract versions