Q.ABC Consultants are setting up a secure network for their office campus at Noida for their day-to-day office and web-based activities. They are planning to have connectivity between three buildings and the head office situated in Bengaluru. As a network consultant, 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 →ABC Consultants need a LAN for their Noida campus (three buildings) and a WAN link to Bengaluru; the server goes in Building 3 (most computers), switches in each building, repeaters for longer runs, optical fibre for the 1500 km link, and SSH/Telnet for remote login.
Network design begins with understanding traffic patterns and resource placement. ABC Consultants face a classic scenario: a local campus network (LAN) spanning three buildings in Noida, plus a long-haul connection (WAN) to a head office 1500 km away in Bengaluru. The goal is efficiency, security, and cost-effectiveness. Each decision—where to put the server, how to lay cables, which devices to deploy—flows from the physical layout, the number of users, and the distances involved.
(i) Server Placement
The server should be installed in Building 3. This is not arbitrary. Building 3 houses 150 computers, far more than Building 1 (25) or Building 2 (51). In a client-server architecture, most network traffic flows between clients and the server—file requests, database queries, application access. Placing the server where the majority of users sit minimizes the distance data must travel, reduces congestion on inter-building links, and cuts latency. If the server were in Building 1, every request from Building 3's 150 machines would have to cross 120 m of cable, creating a bottleneck. Centrality in terms of user density, not geographic midpoint, is what matters.
Server placement should prioritize the location with the highest number of computers to minimize network traffic on backbone links and improve response times.
(ii) Cable Layout
The most economical and efficient layout connects the buildings in a logical chain, avoiding redundant cable runs. Given the distances:
- Building 1 to Building 2: 50 m
- Building 2 to Building 3: 65 m
- Building 1 to Building 3: 120 m
The optimal layout is Building 1 → Building 2 → Building 3. This uses only two cable segments (50 m + 65 m = 115 m total) instead of three. Connecting Building 1 directly to Building 3 (120 m) and then to Building 2 would add unnecessary length and cost. The linear topology (also called a bus or daisy-chain for inter-building links) is standard practice when buildings are not equidistant: you connect them in sequence, minimizing total cable length while ensuring all buildings reach the server in Building 3.
This layout assumes Ethernet over twisted-pair (Cat 6) or fibre. For the 120 m run (if a direct link were needed), fibre would be preferable, but the two-segment chain keeps all runs under 100 m, within Cat 6 range if repeaters or switches are used.
(iii) Device Placement
Switch: A switch should be installed in each building. Switches operate at the data link layer, intelligently forwarding frames only to the destination port, which reduces collisions and broadcasts within each building's local segment. Building 3, with 150 computers, especially needs a high-capacity switch (or multiple switches in a stack) to handle internal traffic. Switches in Building 1 and Building 2 serve their local users and connect to the backbone leading to Building 3. This segmentation improves performance and security—each building becomes its own collision domain.
Repeater: Repeaters (or more commonly today, repeater functionality within switches) are needed on any cable run approaching or exceeding 100 m. Ethernet over Cat 5e/Cat 6 has a maximum segment length of 100 m before signal attenuation degrades data. The Building 1 to Building 3 distance is 120 m; if a direct link were used, a repeater would be essential at the midpoint to regenerate the signal. However, with the proposed layout (Building 1 → Building 2 → Building 3), each segment is under 100 m, so repeaters are not strictly necessary unless the internal cabling within a building (from switch to farthest workstation) pushes the limit. In practice, the switch in Building 2 acts as a repeater for traffic passing from Building 1 to Building 3.
Modern networks often use managed switches with built-in signal regeneration, so standalone repeaters are rare. The key principle remains: no single cable segment should exceed 100 m without signal boosting.
(iv) High-Speed Wired Medium to Bengaluru …
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.