In TCP/IP networking, which component commonly performs Network Address Translation (NAT) to map many private IP addresses to one public address (or a small pool) for Internet access and policy control?

Introduction:
Network Address Translation (NAT) is a foundational technique that enables multiple devices using private IPv4 addresses to share a smaller set of public IPv4 addresses. It is central to home, campus, and enterprise edge connectivity and is frequently implemented on purpose-built networking equipment at the boundary between a private network and the Internet.

Given Data / Assumptions:

• We are discussing practical, production deployments of NAT at the network edge.
• Private addressing (for example, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) is used inside the LAN.
• Public connectivity requires translation to routable public IPv4 addresses.

Concept / Approach:
NAT modifies packet headers as traffic crosses a boundary device. In the typical “many-to-one” or Port Address Translation (PAT) case, the device rewrites the source IP and source port of outbound flows to a public address and a unique port, tracking the mapping in a translation table. Return traffic is de-NATed back to the original internal host. Because this operation must inspect and rewrite IP and transport-layer fields at line rate, it is implemented on routers, firewalls, or gateway appliances designed for such tasks.

Step-by-Step Solution:
1) Identify where private-to-public boundary exists → at the LAN/WAN edge device.2) Determine which device class rewrites IP headers and maintains state tables → routers/firewall-routers.3) Exclude devices that merely repeat signals (hubs) or expose per-host drivers (NIC drivers).4) Conclude that routers typically perform NAT.

Verification / Alternative check:
Consumer “Wi-Fi routers,” enterprise edge routers, and firewalls all advertise NAT or PAT features. Operating systems can offer software NAT, but the canonical, exam-appropriate answer remains “routers.”

Why Other Options Are Wrong:

• Network adapter drivers: per-host software; not the standard perimeter NAT function.
• Hubs: layer-1 repeaters without header awareness.
• Windows 95: an operating system, not the network edge device; ICS existed later but is not the best-fit answer.
• None of the above: invalid because routers are correct.

Common Pitfalls:
Confusing DHCP (address assignment) with NAT (address translation), or assuming switches/hubs can rewrite IP headers—they cannot at layer 1/2.

Final Answer:
Routers