MyCorp has the following NAT rules. You need to disable the NAT function when Alpha-internal networks try to reach the Google DNS (8.8.8.8) server. What can you do in this case?

Manual NAT rules define explicit translation entries but cannot override or create exceptions to automatic NAT rules that are already matched; the network object exception method is the correct approach for suppressing automatic NAT for a specific destination.

Global Properties NAT settings configure gateway-level behaviors such as IP pool NAT and merge of manual and automatic rules, but do not support specifying per-destination exceptions for individual network objects.

Disabling NAT within a VPN community removes address translation only for traffic traversing that VPN tunnel, and would not affect standard internal-to-internet traffic destined for a public IP like 8.8.8.8.

In Check Point, a network object that has automatic Hide NAT configured also exposes a NAT exception list where specific destination IP addresses can be excluded from translation. By adding 8.8.8.8 as an exception inside the Alpha-internal network object, traffic from that network destined for Google DNS will pass through the gateway without any address translation applied. This is the purpose-built mechanism for creating per-destination NAT exceptions without disrupting the broader NAT rule set.