RTU Kota B.Tech 6th Semester Distributed Systems Question Paper 2022 (IT)

RTU Distributed Systems 2022 Paper Review

The Distributed Systems course is a cornerstone of the 6th-semester curriculum for Information Technology students at Rajasthan Technical University (RTU). This subject moves beyond the basic principles of single-node operating systems to explore the complexities of multi-node coordination, inter-process communication, and the persistence of system integrity despite partial failures. Mastering this course is essential for understanding modern cloud architectures and large-scale web services.

The 2022 examination paper emphasized the transition from theoretical transparency models to practical algorithmic implementation. Success in this exam requires a firm grasp of network communication, concurrency control, and the inherent challenges of maintaining state in a decentralized environment.

Understanding the Exam Pattern

The RTU theory examination is a three-hour paper worth 70 marks, organized into three parts:

• Part A (20 Marks): Ten compulsory questions, two marks each. These test your foundational grasp of concepts. Expect definitions covering transparency, client-server models, Remote Procedure Calls (RPC), and the difference between synchronous and asynchronous systems. Keep your answers concise, typically under 25 words.
• Part B (20 Marks): Seven questions; answer five. Each is worth four marks. These are analytical questions. Prepare to explain design goals, compare different message-passing models, or describe the mechanics of distributed file systems (DFS).
• Part C (30 Marks): Five major questions; answer three. Each is worth ten marks. These require detailed technical explanations or calculations. Anticipate long-form questions on logical clocks (Lamport’s), deadlock detection, consensus protocols, and global state recording.

Core Topics Evaluated in the 2022 Curriculum

Focus your study time on these specific modules to maximize your performance:

1. Foundations of Distributed Systems

Understand the primary design goals: transparency, openness, reliability, and performance. You must clearly distinguish between different types of transparency, such as location, migration, and replication transparency.

2. Communication and Coordination

This is a high-yield area. Master the mechanics of Remote Procedure Call (RPC) and Remote Method Invocation (RMI). Know the lifecycle of an RPC—from the client stub to the server stub and back—including how parameter marshaling works.

3. Synchronization and Logical Time

Global time does not exist in distributed systems, so you must understand how to order events. Practice calculating logical clock values using Lamport’s algorithm and Vector clocks. Study the Chandy-Lamport algorithm for recording a consistent global state of a distributed system.

4. Agreement and Fault Tolerance

This section tests your ability to solve critical distributed problems:

• Mutual Exclusion: Compare centralized, distributed (Ricart-Agrawala), and token-ring algorithms.
• Deadlock Handling: Explain distributed deadlock detection using wait-for graphs and path-pushing/edge-chasing algorithms.
• Consensus: Understand the impossibility of consensus in asynchronous systems and how Paxos or Byzantine fault-tolerant (BFT) protocols work at a high level.

Answer Writing Strategy for High Marks

RTU evaluators prioritize logical rigor and visual clarity:

• Visual Aids: If asked to explain an algorithm like the Bully Election or a snapshot process, draw the node interactions clearly. Use consistent symbols for messages, nodes, and failures. A ruler and black pen are essential for professional diagrams.
• Formatting: Use headings and bullet points for your explanations. For Part C, always start with an introduction of the algorithm, followed by the technical steps, and end with the practical application or security/limitation context.
• Precision: When explaining synchronization, always state the underlying assumption (e.g., "assuming a reliable communication channel").
• Comparative Tables: For questions like "Centralized vs. Distributed Operating Systems" or "At-least-once vs. Exactly-once RPC semantics," always use a table to show your technical understanding.

Time Management During the Exam

• Part A (20 minutes): Complete these early to secure your initial marks. Aim for roughly two minutes per question.
• Part B (40 minutes): Spend approximately eight minutes per question. If a question requires a comparison, draw the table first and then fill in the points to stay organized.
• Part C (120 minutes): Devote 40 minutes to each of the three major questions. Use this time to carefully draw diagrams and explain the multi-step processes involved in coordination algorithms or complex deadlock detection cycles.