An administrator publishes an internal web server (10.10.1.50:443) to the internet using a virtual IP that maps the WAN interface IP to the server on the same port. A firewall policy from wan1 to the internal LAN uses this VIP as the destination address with the action set to ACCEPT. Which translation does the FortiGate apply to the inbound traffic, and where in the policy is it configured?
- ASource NAT, configured by enabling the NAT toggle and selecting an IP pool in the same firewall policy.
- BDestination NAT, performed automatically by the virtual IP referenced as the destination address of the firewall policy. Correct
- CDestination NAT, performed only after the NAT toggle is enabled and central NAT mode is turned on for the VDOM.
- DSource NAT, performed by a static one-to-one IP pool that maps the server address to the WAN interface address.
Why A is wrong: SNAT rewrites the source address of outbound sessions and is enabled with the NAT toggle plus an optional IP pool; this is tempting because both NAT types are policy-related, but inbound publishing of a server uses destination translation through the VIP, not source translation.
Why B is correct: A virtual IP is a DNAT object; once it is selected as the policy destination, the FortiGate rewrites the external destination address and port to the mapped internal server, so the translation is inherent to the VIP rather than the NAT toggle.
Why C is wrong: The NAT toggle governs source translation and central NAT changes where SNAT and DNAT rules live, not whether a VIP works; a VIP referenced as a destination performs DNAT regardless of the NAT toggle, making this a plausible but incorrect conflation.
Why D is wrong: A one-to-one IP pool does translate addresses, but it operates on the source of egress traffic; using it to describe inbound server publishing reverses the direction of translation, which is the common error this distractor captures.