📝 Chord protocol in peer to peer networks (9 MCQs)
📖 From Data Communication and Networks • 29. Peer to Peer Paradigm • 9 questions available
What is Chord protocol in peer to peer networks?
The Chord protocol is a structured P2P system that organizes nodes into a logical ring to efficiently locate data by using consistent hashing, ensuring that any node can find any piece of information in logarithmic time relative to network size.
📝 All Chord protocol in peer to peer networks MCQs
Q1. A new node with identifier 18 joins a Chord ring where node 14’s successor is node 20. Which statement correctly describes the immediate effect on node 14’s routing information?
📖 Explanation: When node 18 inserts itself between 14 and 20, the ring ordering forces node 14 to update its successor pointer to the newly adjacent node 18. The predecessor of 14 remains unchanged, and finger table entries are only adjusted during the stabilization phase, not instantly.
Q2. In a Chord network with identifier space modulo , a lookup for key 27 starts at node 5. Which sequence of nodes is most likely visited before reaching the key’s successor?
📖 Explanation: The identifier space is –. Node 5’s finger table contains entries that jump to the closest preceding nodes. The most efficient path follows the power‑of‑two steps: from 5 to 8, then 16, then 24, and finally reaches the node responsible for key 27. This matches option D.
Q3. If nodes 2, 7, and 15 are present in a Chord ring of size , and node 7 fails unexpectedly, what is the most immediate inconsistency that can arise in node 2’s finger table?
📖 Explanation: Node 2’s finger table entry for start 4 should point to the first node that succeeds identifier 4, which was node 7. After node 7 crashes, that entry still contains the stale identifier of the failed node, causing an immediate inconsistency until stabilization repairs it.
Q4. Which of the following best contrasts the finger table with the successor list in Chord?
📖 Explanation: The finger table contains entries that give logarithmic‑size shortcuts, enabling fast lookups, while the successor list holds a small set of immediate successors to tolerate failures. This distinction directly matches option A.
Q5. In a Chord system with identifier length bits, how does increasing from 8 to 12 affect the average lookup path length, assuming the number of nodes remains constant?
📖 Explanation: Lookup cost in Chord depends primarily on the number of active nodes , not on the size of the identifier space. Expanding merely enlarges the potential key space, leaving the average number of hops—approximately —unchanged, which is captured by option B.
Q6. Consider two maintenance strategies: (1) Chord’s periodic stabilization where each node contacts its successor; (2) a naive approach where nodes broadcast their full finger tables after every join. Which statement correctly captures a key difference?
📖 Explanation: Chord’s stabilization is designed to be lightweight: each node periodically sends a small number of messages (constant‑time) to its successor, leading to overall traffic. Broadcasting full finger tables after every join would generate a message count that grows linearly with the number of nodes, i.e., , making option A the accurate comparison.
Q7. Given a Chord ring with 1024 nodes (), what is the expected number of hops for a lookup if finger tables are perfectly populated?
📖 Explanation: When finger tables are complete, the expected lookup length is about . For , , so the average number of hops is roughly 5, matching option D.
Q8. If three consecutive nodes in a Chord ring fail simultaneously, how does the network ensure continued correct routing for lookups?
📖 Explanation: Chord nodes maintain a successor list of several immediate successors. When a block of consecutive nodes disappears, each surviving node can still reach a live node via its successor list, effectively bypassing the gap and preserving routing correctness, which is described in option A.
Q9. In Chord, what is the primary purpose of a finger table?
📖 Explanation: A finger table contains entries that point to nodes at exponentially increasing distances around the identifier circle. This structure gives each node a logarithmic‑size set of shortcuts, enabling lookups to be performed in hops, which is the purpose stated in option B.