For my Distributed Systems module, can you generate some past paper questions based on…
- User
For my Distributed Systems module, can you generate some past paper questions based on these topics
Week 2 - RPC, RMI and SOAP (27 Jan - 31 Jan) Week 3 - REST (3 - 7 Feb) Week 4 - Multiplay Game Synchronization (10 - 14 Feb) Week 5 -Synchronization (17 - 21 Feb) Week 6 - RAFT and Cloud Computing (24 Feb - 28 Feb) Week 8 - Consensus and Paxos (10 - 14 Mar) Week 9 - P2P and DHT (17 - 21 Mar) Week 10 - Key Value Stores (24 - 28 Mar) Week 11 - Bitcoin (31 Mar - 4 Apr)Generate one exam question for each topic
- Assistant
Sure! Below are exam-style questions, one for each topic from your Distributed Systems module. These are suitable for use in a past paper or revision, and include a mix of conceptual, design, and analytical problem-solving types:
Week 2 - RPC, RMI, and SOAP
Question 1:
Compare and contrast Remote Procedure Call (RPC), Remote Method Invocation (RMI), and SOAP-based web services. In your answer, discuss the underlying communication mechanisms, programming language dependencies, and typical use cases for each technology.
Week 3 - REST
Question 2:
Design a RESTful web service for a simple task management application that allows users to create, read, update, and delete tasks. Explain how the core REST principles are applied in your API design, including resource naming, HTTP methods, and statelessness.
Week 4 - Multiplay Game Synchronization
Question 3:
In a real-time multiplayer game over the internet, maintaining a consistent state among all players is critical. Discuss at least two synchronization techniques used in multiplayer gaming (e.g., lockstep, client prediction). Explain the trade-offs involved in using each technique, especially under network latency or packet loss.
Week 5 - Synchronization
Question 4:
Explain the difference between logical clocks and vector clocks in distributed systems. Provide a scenario in which vector clocks are necessary to capture causality that logical clocks cannot. Draw an example to support your explanation.
Week 6 - RAFT and Cloud Computing
Question 5:
a) Describe how the RAFT consensus algorithm ensures safety and liveness in a distributed system.
b) Explain how cloud computing services (e.g., AWS, Azure) leverage consensus protocols to maintain consistency across distributed components. Use RAFT as an example where appropriate.
Week 8 - Consensus and Paxos
Question 6:
Paxos is known to be a correct but complex consensus algorithm. Describe the roles of Proposer, Acceptor, and Learner in the standard Paxos algorithm. Then, consider a scenario with message loss. Explain how Paxos still ensures safety even when some messages are not delivered.
Week 9 - P2P and DHT
Question 7:
Distributed Hash Tables (DHTs) are essential in peer-to-peer networks. Describe how a DHT such as Chord manages efficient data lookup. In your answer, include the concepts of consistent hashing and finger tables, and show how the lookup performance scales with the number of nodes.
Week 10 - Key Value Stores
Question 8:
Compare and contrast eventual consistency and strong consistency in the context of distributed key-value stores such as Amazon Dynamo and Apache Cassandra. Discuss specific mechanisms these systems use to achieve their consistency models, including read/write quorums, vector clocks, or hinted handoff.
Week 11 - Bitcoin
Question 9:
Explain how Bitcoin achieves consensus on the state of its blockchain in an open and adversarial network. In your answer, define the role of Proof of Work, mining, and longest chain rules. Discuss the trade-offs of using Proof of Work in terms of efficiency, security, and scalability.
Let me know if you'd like model answers or marking schemes, or if you'd like them adapted to multiple-choice or short-answer format!
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.