An enterprise firewall receives traffic from a subnet that must be translated using Dynamic IP and Port (DIPP) Source NAT. The administrator needs to ensure that port allocation for a specific high-traffic server is predictable and does not get exhausted. Which NAT feature should be configured?
Trap 1: No-NAT rule with Universal translation
A No-NAT rule disables translation completely, which does not provide port management.
Trap 2: Destination NAT with Port Mapping
Destination NAT maps inbound ports to internal servers, whereas the scenario specifies Source NAT outbound traffic.
Trap 3: Static IP Source NAT with bi-directional mapping
Static IP Source NAT maps a 1:1 IP address without port translation, which does not solve port conservation or DIPP management.
- A
No-NAT rule with Universal translation
Why wrong: A No-NAT rule disables translation completely, which does not provide port management.
- B
Dynamic IP and Port (DIPP) Source NAT with Port Distribution or Block Allocation
DIPP block allocation reserves specific blocks of ports for individual source IPs, preventing port starvation and ensuring predictable usage.
- C
Destination NAT with Port Mapping
Why wrong: Destination NAT maps inbound ports to internal servers, whereas the scenario specifies Source NAT outbound traffic.
- D
Static IP Source NAT with bi-directional mapping
Why wrong: Static IP Source NAT maps a 1:1 IP address without port translation, which does not solve port conservation or DIPP management.