Match each enterprise address translation requirement or scenario on the left with the correct NAT/PAT implementation method or routing behavior on the right.
- Providing an inbound persistent public IP mapping for an internal DMZ web server requiring fixed external accessStatic NAT (1:1 Translation)
- Multiplexing thousands of internal client outbound sessions onto a single public IP address using unique transport layer portsPort Address Translation (PAT / NAT Overload)
- Assigning temporary, dynamic public IP addresses from a limited public subnet pool to active internal outbound hostsDynamic NAT (Pool Translation)
- Forwarding packets across internal subnets where host IP header addresses remain unchanged through transitNative IP Routing (No NAT)
Cevap
Inbound persistent web server hosting corresponds to Static NAT (1:1 Translation). Outbound session multiplexing using unique transport ports corresponds to Port Address Translation (PAT / NAT Overload). Assigning temporary public IPs from a defined subnet pool corresponds to Dynamic NAT (Pool Translation). Packet forwarding without address alteration corresponds to Native IP Routing (No NAT).
Each requirement directly aligns with standard network implementation terminology: Static NAT provides a fixed 1:1 public-to-private IP mapping ideal for inbound public services; PAT (NAT Overload) allows many hosts to share a single public IP via port multiplexing; Dynamic NAT draws temporary 1:1 public addresses from a pool; and Native IP Routing forwards packets without translating IP header address fields.
Adım Adım Çözüm
Anahtar Kavram
NAT and PAT address mapping types and operational requirements