122 lines
3.5 KiB
JSON
122 lines
3.5 KiB
JSON
[
|
|
{
|
|
"id": 1,
|
|
"question": "What is horizontal scaling?",
|
|
"options": {
|
|
"A": "Adding more CPU and RAM to one machine",
|
|
"B": "Reducing system load",
|
|
"C": "Upgrading the operating system",
|
|
"D": "Adding more machines to the network"
|
|
}
|
|
},
|
|
{
|
|
"id": 2,
|
|
"question": "In distributed systems, replication helps with:",
|
|
"options": {
|
|
"A": "Fault tolerance",
|
|
"B": "Increasing latency",
|
|
"C": "Reducing decentralization",
|
|
"D": "Removing consensus"
|
|
}
|
|
},
|
|
{
|
|
"id": 3,
|
|
"question": "A message broker provides:",
|
|
"options": {
|
|
"A": "Direct database access",
|
|
"B": "Temporal decoupling between producer and consumer",
|
|
"C": "Strong consistency",
|
|
"D": "Blockchain verification"
|
|
}
|
|
},
|
|
{
|
|
"id": 4,
|
|
"question": "Hardhat is:",
|
|
"options": {
|
|
"A": "An Ethereum development environment",
|
|
"B": "A cryptocurrency",
|
|
"C": "A blockchain",
|
|
"D": "A consensus algorithm"
|
|
}
|
|
},
|
|
{
|
|
"id": 5,
|
|
"question": "In Proof of Work, miners:",
|
|
"options": {
|
|
"A": "Stake coins",
|
|
"B": "Solve complex mathematical puzzles",
|
|
"C": "Vote on transactions",
|
|
"D": "Create smart contracts"
|
|
}
|
|
},
|
|
{
|
|
"id": 6,
|
|
"question": "In Ethereum, if two conflicting transactions attempt a double spend:",
|
|
"options": {
|
|
"A": "Both are accepted",
|
|
"B": "Neither is accepted",
|
|
"C": "A globally accepted order is selected and one is rejected",
|
|
"D": "The sender loses all Ether"
|
|
}
|
|
},
|
|
{
|
|
"id": 7,
|
|
"question": "A mnemonic (seed phrase) allows a user to:",
|
|
"options": {
|
|
"A": "Mine faster",
|
|
"B": "Recover private keys",
|
|
"C": "Increase gas fees",
|
|
"D": "Modify blockchain rules"
|
|
}
|
|
},
|
|
{
|
|
"id": 8,
|
|
"question": "In an AP (Availability + Partition tolerance) system, during a network partition the system:",
|
|
"options": {
|
|
"A": "Always returns consistent data",
|
|
"B": "Stops operating",
|
|
"C": "Removes inconsistent data",
|
|
"D": "Returns possibly stale data"
|
|
}
|
|
},
|
|
{
|
|
"id": 9,
|
|
"question": "Asynchronous communication primarily enables:",
|
|
"options": {
|
|
"A": "Tight coupling",
|
|
"B": "Temporal coupling",
|
|
"C": "Loose coupling",
|
|
"D": "Direct memory access"
|
|
}
|
|
},
|
|
{
|
|
"id": 10,
|
|
"question": "Why is Partition Tolerance (P) considered not-negotiable in real-world distributed systems?",
|
|
"options": {
|
|
"A": "Because users demand 100% availability",
|
|
"B": "Because network failures that split a system are inevitable in the real world",
|
|
"C": "Because it is the cheapest guarantee to implement",
|
|
"D": "Because data consistency is only important in areas like banking"
|
|
}
|
|
},
|
|
{
|
|
"id": 11,
|
|
"question": "How does Raft differ from basic Paxos in its approach to reaching consensus?",
|
|
"options": {
|
|
"A": "Raft was designed to work via a single elected leader",
|
|
"B": "Raft is used for strong consistency, while Paxos is for eventual consistency",
|
|
"C": "Raft does not require a majority of nodes to agree",
|
|
"D": "Raft is mathematically impossible to implement"
|
|
}
|
|
},
|
|
{
|
|
"id": 12,
|
|
"question": "Why are Paxos and Raft generally unsuitable for public blockchain networks?",
|
|
"options": {
|
|
"A": "They are too slow for blockchain use",
|
|
"B": "They do not support data synchronization",
|
|
"C": "They require specialized hardware to run",
|
|
"D": "They assume all nodes are *honest* and operate in a trusted environment"
|
|
}
|
|
}
|
|
] |