Static NAT establishes a permanent, one-to-one mapping between a specific private IP address and a specific public IP address. This configuration is required when an internal device, such as a server, must be accessible from the public network using a consistent, dedicated public IP address. The mapping is bidirectional, allowing connections to be initiated from either the internal or external network. This directly addresses the scenario's need for one-to-one mappings for a set of servers.

A. source NAT with PAT: This is a many-to-one mapping, translating multiple private IPs to a single public IP using different ports. It is unsuitable for providing dedicated public IPs to servers.

B. destination NAT: While static NAT uses a destination NAT component for inbound traffic, "static NAT" is the more precise term describing the complete, persistent, one-to-one mapping required by the scenario.

C. NAT-T: NAT Traversal (NAT-T) is a method used to allow IPsec VPN traffic to pass through a NAT device; it is not a type of address mapping configuration.

1. Juniper Networks TechLibrary

"Static NAT Overview": "Static NAT provides a one-to-one mapping of a local address to a global address. Because the mapping is static

static NAT allows external devices to initiate connections to internal hosts..." Juniper Networks

"Static NAT Overview

" Junos OS Documentation

2. Juniper Networks TechLibrary

"Source NAT Overview": "Source NAT translates the source IP address of packets that leave a private network... Source NAT is most often used to translate private source IP addresses to public IP addresses." (This describes outbound

typically many-to-one translation). Juniper Networks

"Source NAT Overview

" Junos OS Documentation

3. Juniper Networks TechLibrary

"Understanding NAT Traversal for IPsec": "NAT-T is a method for getting around the IP address translation problems encountered when IPsec traffic passes through a NAT device..." Juniper Networks

"Understanding NAT Traversal for IPsec

" Junos OS Documentation