A network engineer is configuring address translation policies on an enterprise edge firewall. Match each specific technical mapping requirement on the left with its corresponding address translation implementation type on the right.
- Providing a permanent, one-to-one mapping between a private IP address of an internal web server () and a dedicated public IP address ().Static NAT
- Allowing 200 internal workstations on a private subnet () to access external resources simultaneously using a single public IP address ().Port Address Translation (PAT / NAT Overload)
- Mapping internal hosts on demand to available external IP addresses from a pre-allocated public address pool () without port modification.Dynamic NAT
- Redirecting inbound traffic sent to an external public IP on port 8080 () to an internal database management interface ().Port Forwarding (Static PAT)
Answer
Static NAT pairs with permanent 1-to-1 server mapping; Port Address Translation (PAT / NAT Overload) pairs with many workstations sharing a single public IP address; Dynamic NAT pairs with mapping hosts to a pool of public IP addresses on demand; Port Forwarding (Static PAT) pairs with redirecting a specific external port to an internal IP address and port.
Each NAT implementation serves a distinct networking use case: Static NAT provides a fixed 1-to-1 mapping for external server accessibility; PAT multiplexes multiple private IP addresses onto one public IP using Layer 4 port tracking; Dynamic NAT draws 1-to-1 public IP mappings temporarily from a pool; and Port Forwarding directs specific inbound external port traffic to an internal target host.
Step-by-Step Solution
Key Concept
NAT and PAT Implementation Types and Selection Criteria
Estimated Time:1m 30s