GATE CSE Computer Networks (CN) PYQs
Medium Access Control (MAC) in GATE CS is predominantly tested through quantitative numerical problems and conceptual protocol comparisons. GATE CS tests TCP ac… Read the guide
- Topics
- 11
- Questions
- 133
- Marks / paper
- 7.6
- Asked
- since 2011
These are the 133 GATE CSE Computer Networks PYQs (since 2011), grouped topic-wise with solutions. See all GATE CSE PYQs or GATE CSE question papers by year.
Topics
Open a topic to browse its questions, or practice it as a timed test.
By year
Jump to the first question from each year’s paper.
What GATE tests in Computer Networks
Concepts, patterns, formulas and traps distilled from past papers.
Medium Access Control (MAC) in GATE CS is predominantly tested through quantitative numerical problems and conceptual protocol comparisons. GATE CS tests TCP across three primary areas: congestion control dynamics (window growth phases, timeout recovery, and round-by-round segment tracking), sequence number wrap-around time and bit-budget calculations against MSL, and connection lifecycle mechanics (3-way handshake flags, state transitions during active/passive close, and crash recovery with RST segments). IPv4 testing in GATE CS focuses heavily on numerical datagram mechanics (fragmentation offset, payload size, header scaling factors), CIDR subnetting (subnet allocation, host ranges, bitwise masking, and longest prefix match forwarding), and IP header architecture (field modifications during transit, option field capacity, and encapsulated protocol numbers).
Core concepts
- Stop-and-Wait Protocol and ARQ efficiency
- Sliding Window Protocols (Go-Back-N, Selective Repeat)
- Bandwidth-Delay Product (BDP) and Channel Utilization
- Sequence Number Field sizing and wrap-around time constraints
- Error Detection using Cyclic Redundancy Check (CRC) modulo-2 division
- Transmission delay vs. Propagation delay vs. Processing delay trade-offs
- Selective Repeat (SR) ARQ Mechanics
- Propagation Delay (Tp) vs Transmission Time (Tt)
- Link Utilization and Efficiency ( )
- Window Sizing (Ws, Wr)
- Sequence Number Space Sizing (2k ≥ Ws + Wr)
- Cyclic Redundancy Check (CRC) mechanism
How questions show up
Stop-and-Wait Protocol Efficiency and Parameter Sizing
Commonmixed2 marks2025, 2017, 2015Calculations involving link utilization , determining minimum frame size for target utilization, or finding efficiency with detailed parameters including ACK transmission time, processing overheads, and packet headers.
Sliding Window Sizing and Sequence Number Constraints
Commonmixed2 marks2026Calculating optimal sender window size for 100% link utilization, or determining the sequence number bit width under dual constraints of maximum link utilization and sequence number wrap-around time.
Cyclic Redundancy Check (CRC) Modulo-2 Division
OccasionalMCQ2 marks2026Given a data bit sequence and a generator polynomial bit pattern of length , finding the -bit CRC remainder appended to the frame by performing XOR-based modulo-2 division.
Qualitative Analysis of Protocol Utilization
OccasionalMCQ1 marks2023Identifying the relationship between protocol efficiency and physical parameters like link distance, bandwidth, frame size, and propagation velocity.
Sequence Number Field Sizing for Sliding Window Protocols
OccasionalNAT2 marks2016Given channel bandwidth, one-way propagation delay, frame length, and protocol type (e.g., Selective Repeat), compute the frame transmission time, required sender window size for target link utilization (often 100%), total sequence number space size (), and the minimum number of sequence number bits required.
CRC Remainder / Checkbit Calculation
CommonMCQ2 marks2021Given a generator polynomial of degree and a binary data word / message , calculate the -bit CRC code (remainder) generated by modulo-2 polynomial division of by .
High-yield formulas
Transmission Time and Propagation Delay
Used to compute data/ACK packet transmission times and one-way propagation delays from frame length , bandwidth , distance , and signal speed .
Stop-and-Wait Efficiency (Standard / Ideal)
Used when processing delay and ACK transmission time are negligible.
Stop-and-Wait ARQ Efficiency (Detailed with Overheads)
Used when ACK size, node processing time, or header/payload byte separations are explicitly specified.
Sliding Window Optimal Window Size for 100% Utilization
Used to find the minimum sender window size (in frames) needed to achieve full link utilization.
Sequence Number Space and Wrap-around Time
and
Used when determining the minimum sequence number bits under maximum throughput and lifetime/wrap-around constraints.
CRC Modulo-2 Arithmetic
Used to compute CRC checksum/FCS bits for an error-detecting generator of length .
Frame Transmission Time
Used to find the time taken to transmit a data frame of size over a link of bandwidth .
Normalized Propagation Delay (a-parameter)
Used to relate one-way propagation delay to packet transmission delay .
Examiner traps in Computer Networks
- Unit mismatch: Failing to convert between bytes and bits (multiplying or dividing by 8) for frame size or bandwidth.
- Metric prefixes: Confusing 1 kbps = 103 bps (networking convention) with 210 bps, or mixing milliseconds (10-3 s) with microseconds (10-6 s) and nanoseconds (10-9 s).
- One-way vs. Round-Trip Time: Forgetting that total cycle time includes 2 × Tp (round-trip propagation) rather than single Tp.
- Useful vs. Total Transmission Time: Neglecting to subtract header/overhead bytes when computing useful transmission efficiency if distinct overheads are specified.
- CRC 0-padding: Appending k zeros instead of (k - 1) zeros for a generator pattern of length k bits.
- Confusing Selective Repeat sequence space (N ≥ 2Ws) with Go-Back-N sequence space (N ≥ Ws + 1).
- Failing to ceil the continuous value of window size 1 + 2a to an integer before multiplying by 2 for Selective Repeat sequence space.
- Unit conversion errors between bits and bytes (e.g., 1 KB = 1024 × 8 bits or 1000 × 8 bits) and milliseconds to seconds.
Paper trends
Questions have evolved from basic Stop-and-Wait formulas to realistic multi-parameter accounting (considering ACK transmission time, processing delay, data vs. overhead bytes) and dual-constraint window/sequence number design problems.
2026, 2017, 2015
High prevalence of numerical answer type (NAT) and 2-mark computational MCQs that test unit conversions (e.g., bits vs. bytes, kbps vs. bps, nanoseconds per meter).
2026, 2025, 2017, 2015
Emphasis is placed on end-to-end exact integer calculation formatted as Numerical Answer Type (NAT), ensuring candidates understand ceil operations at discrete window sizing and bit-allocation stages.
2016
Direct calculation of CRC checkbits via polynomial division has appeared as a high-weightage 2-mark MCQ requiring careful step-by-step XOR arithmetic.
2021