Network Topologies Explained: Types, Link-Count Formulas and Exam Traps

Learn how physical and logical topology differ, derive link-count formulas, and solve star, ring and full-mesh calculations for eight devices.

KnowledgeGate Team

Exam prep & CS education

Updated 16 Nov 20265 min read
Network Topologies Explained: Types, Link-Count Formulas and Exam Traps

A learner can recognise a star-shaped drawing and still lose marks by counting links, ports, or failure points under the wrong assumptions. Physical arrangement differs from logical communication, and the major topologies have different link-count and failure patterns. In computer science, careful definitions matter as much as formulas.

What a network topology actually describes

A network topology is the arrangement of nodes and links. Physical topology is the actual device and cabling layout. Logical topology is the path followed by frames or data.

Eight computers cabled to one central device form a physical star. An Ethernet hub repeats bits onto a shared medium, while a switch forwards frames over point-to-point computer links. The drawing alone does not settle collision behaviour or logical forwarding.

Topology is not an addressing scheme, transport protocol, or routing algorithm. It shows which connections exist, while route selection chooses an available path.

For the broader survey of layers, switching, and delay, start with Introduction to Computer Networks: Layers, Topologies, Switching and Delay Formulas with Worked Examples. Topology questions then narrow the job to proving link and interface counts, checking degree sums, and stating failure assumptions explicitly.

Bus, star, ring, mesh, tree and hybrid topologies

A point-to-point topology joins two nodes by one dedicated link. A bus attaches devices to a shared backbone. A classic coaxial bus needs a terminator at each end.

In a star, every endpoint connects to a central hub or switch. A ring gives each node two neighbours in a closed cycle. A full mesh links every node pair directly; a partial mesh links only selected pairs.

A tree is a connected, acyclic hierarchy. A hybrid combines structures, such as access stars joined by a backbone.

There is no universal best topology. A star supports easy expansion and branch isolation but depends on its centre. A mesh offers alternate paths at the cost of more cabling and interfaces. A bus depends on its backbone, while a high-level tree failure can remove a branch. The choice depends on scale, redundancy, distance, and budget.

For n end devices in a star, one device-to-centre link per device gives n links and n used centre ports.

In a simple ring, every node has two neighbours. Its degree sum is 2n; since each link contributes two, it has 2n/2 = n links and two interfaces per node.

In a full mesh, each node connects to n - 1 others. The count n(n - 1) includes both A to B and B to A for one link, so divide by two:

Full-mesh links = n(n - 1)/2

Each mesh node needs n - 1 direct-link interfaces.

The tree rule requires a connected, acyclic network: V total vertices give V - 1 edges. V includes internal switches or routers, so eight end devices do not automatically mean seven links.

A bus has no universal n - 1 rule. A question may count the backbone, drops, segments, connectors, or interfaces differently. Identify links, cable runs, ports, or link endpoints before calculating.

Worked example: compare an eight-device network step by step

Let the endpoints be A, B, C, D, E, F, G, H, so n = 8.

For a star with centre S, the links are SA, SB, SC, SD, SE, SF, SG, SH.

  1. Number of links: n = 8.

  2. Used ports at S: 8.

  3. Link endpoints across both ends: 2 x 8 = 16.

For the simple ring, use AB, BC, CD, DE, EF, FG, GH, HA.

  1. Number of links: n = 8.

  2. Interfaces at each endpoint: 2.

  3. Total link endpoints: 8 x 2 = 16.

For the full mesh:

  1. Links: 8(8 - 1)/2 = 8 x 7/2 = 28.

  2. Direct-link interfaces per device: 8 - 1 = 7.

  3. Total link endpoints: 2 x 28 = 56.

  4. Degree-sum check: 8 x 7 = 56 = 2E, so E = 56/2 = 28.

Add device I. The star reaches 9 links, so the increment is 1. Replacing one ring edge with two gives 9 links, also +1. The mesh reaches 9 x 8/2 = 36, so it adds 36 - 28 = 8. A classic bus with eight drops needs two terminators, but n alone gives neither cable length nor segment count.

Three-panel topology comparison shows a star with 8 links, a ring with 8 links, and a complete K8 mesh with 28 links.

Failure behaviour and redundancy under stated assumptions

In the star, failure of SA isolates only A. Failure of centre S stops communication through the star for all eight endpoints.

Full mesh K8 has edge connectivity 7. Any set of at most 6 failed links leaves it connected, while seven failures can isolate one device by removing its incident links.

Ring behaviour depends on the model. Removing one edge from an undirected eight-node cycle leaves a connected path. In simple unidirectional token passing, one break can stop circulation without bypass or recovery. Always state the assumption.

A classic bus can be partitioned by a backbone break, and incorrect termination can cause reflections. A failed higher-level tree link disconnects its descendants. Compare fault isolation and redundancy without declaring an absolute winner.

Failure map compares star and K8 resilience: one failed star edge isolates A, center failure disconnects all nodes, while K8 and ring remain connected via alternate paths.

How exams turn topology concepts into questions

Questions may ask for links or ports, identify a topology from node degree or its centre, test a specified failure, or contrast physical and logical topology.

Use this 20-second routine:

  1. Underline exactly what is being counted.

  2. Write the topology and failure assumptions.

  3. Choose the formula before substituting n.

  4. Check the result with sum of degrees = 2E where appropriate.

For the mesh, 8 x 7 = 56, then 56/2 = 28. This catches the mistake of reporting ordered endpoint connections as physical links.

After the concept pass, practise Network Topologies in CS Fundamentals for Exams & Placements. For a structured route through the wider syllabus, use GATE Guidance by Sanchit Sir.

Common traps, the short version and what to study next

Topology

Defining structure

Link-count rule

Shared or central failure risk

Expansion implication

Bus

Shared backbone

Depends on counting convention

Backbone or termination can affect many devices

A drop changes the shared medium

Star

Endpoints connect to a centre

n links

Centre affects all; branch affects one

Add one link and centre port

Ring

One cycle

n links

Depends on direction and recovery

Replace one link with two

Full mesh

Every pair linked

n(n - 1)/2

Alternate paths; minimum cut n - 1

New node needs n links

Tree

Connected and acyclic

V - 1 edges

High-level failure removes a branch

Preserve acyclic connectivity

Hybrid

Combined structures

No universal formula

Depends on design

Follow each component topology

Remember the traps: full mesh is not partial mesh; ordered pairs double-count links; hub and switch stars differ logically; ring recovery varies; tree counts include internal devices; bus counts need a convention.

Recalculate the eight-to-nine-device example unaided. Next study IP Addressing and Subnetting Explained, then TCP versus UDP. For networks alongside DBMS and operating systems, use the placement-focused CS Fundamentals for Placements by Sanchit Sir. GATE aspirants can follow the broader path above.