Q.Quickdev, an IT based firm, located in Delhi is planning to set up a network for its four branches within a city with its Marketing department in Kanpur. As a network professional, give solutions to the questions
You're viewing a preview — the full solution, concept, methods & PYQ mapping are locked.
Start your 14-day free trial to unlock the full solution →The server for the Delhi branch should be placed at Branch D because it has the highest number of computers (115) and is centrally located with the shortest average distance to other branches. The ideal layout is a star topology with Branch D as the hub. Each branch needs a switch to connect its computers internally. The network between Delhi and Kanpur is a WAN (Wide Area Network) because the distance is 300 km. FTP (File Transfer Protocol) is the suitable protocol for file transfers between the two cities.
Let’s walk through this network design problem step by step, keeping in mind the practical constraints of an IT firm setting up a multi-branch network.
Setting the scene – Quickdev has four branches in Delhi (A, B, C, D) and a separate Marketing department in Kanpur, 300 km away. The goal is to connect all computers efficiently, both within Delhi and across cities. The distances between Delhi branches are small (15 m to 80 m), while the Kanpur link is a long-haul connection. The number of computers varies significantly: Branch D has 115 computers, which is nearly as many as the other three branches combined (15+25+40 = 80). This imbalance is a key factor in server placement.
(i) Where should the server be installed in Delhi?
The server is the heart of the network – it stores data, runs applications, and manages user requests. Placing it optimally reduces cable costs, improves response times, and simplifies maintenance.
Branch D is the best choice. Here’s why:
- Highest number of computers (115): The server should be close to the largest concentration of users to minimise network traffic and latency. If the server were at Branch A (15 computers), every request from Branch D’s 115 computers would have to travel across the network, creating congestion. Placing it at Branch D means the majority of users get near-instant access.
- Central location: Look at the distances: Branch D is 15 m from Branch C, 35 m from Branch B, and 65 m from Branch A. The average distance from D to other branches is (15+35+65)/3 ≈ 38.3 m. Compare this to Branch A, whose average distance to others is (40+80+65)/3 ≈ 61.7 m. Branch D is more centrally located, reducing cable lengths and signal degradation.
- Scalability: With 115 computers, Branch D likely has the physical space and power infrastructure to host a server room. Adding more computers in the future would be easier if the server is already there.
In a real-world scenario, you might also consider redundancy (e.g., a backup server at another branch), but the question asks for the most suitable single location. Branch D is the clear winner.
(ii) Ideal layout for connecting Delhi branches
The distances between branches are all under 100 m, which means we can use twisted pair Ethernet cables (Cat 5e or Cat 6) – these work reliably up to 100 m. The best topology for this setup is a star topology with Branch D as the central hub.
Why star topology?
- Fault isolation: If a cable between Branch D and Branch A breaks, only Branch A is affected. The other branches continue working. In a bus or ring topology, a single break could bring down the entire network.
- Easy troubleshooting: The central switch at Branch D can monitor traffic and pinpoint problems quickly.
- Scalability: Adding a new branch is simple – just run a cable from the new branch to the central switch at D.
- Cost-effective: Since all distances are short, the cable cost is low, and the central switch at D can handle all traffic.
Layout details:
- Place a main switch at Branch D.
- Run direct Ethernet cables from Branch D to each of the other branches (A, B, C). The longest cable is 65 m (to A), well within the 100 m limit.
- Each branch will have its own local switch (see part iii) to connect its internal computers.
The star topology is the most reliable and manageable for a small campus network like this. Avoid daisy-chaining branches (e.g., A→B→C→D) because a failure at B would cut off A and C.
(iii) Devices needed in each branch
To connect all computers within a branch, you need a switch (or a hub, but switches are far superior). A switch is a networking device that forwards data only to the specific computer it is intended for, unlike a hub which broadcasts to all ports. This reduces unnecessary traffic and improves speed.
For each branch:
- Branch A (15 computers): A 16-port or 24-port switch (to allow for future expansion).
- Branch B (25 computers): A 24-port or 48-port switch.
- Branch C (40 computers): A 48-port switch.
- Branch D (115 computers): A 48-port switch plus additional switches (e.g., two 48-port switches stacked or a modular switch). Since 115 computers exceed the ports on a single typical switch, you’ll need multiple switches interconnected.
Additional device: At Branch D, you’ll also need a router to connect the Delhi network to the Kanpur branch (see part iv). The router will handle traffic between the two cities.
A switch works at Layer 2 (Data Link layer) of the OSI model. For a small branch, an unmanaged switch is sufficient; for Branch D, a managed switch gives better control over traffic.
(iv) Type of network between Delhi and Kanpur …
Unlock everything free for 14 days
- Full step-by-step solutions
- Concept-first explanations
- Methods, shortcuts & mistakes
- PYQ mapping + timed mock tests
Full access for 14 days. No credit card required.