Can you configure NAT for internal VM's on the Check Point Gateway in AWS?

Question

Options

• AYes, you can add public IP's to the Check Point
• BNo. ail the NAT is being done by the ELB
• CNo, the public IPs are defined directly on the in
• DYes, the NAT is only defined for internal LB

• A
  2% (1)
• B
  2% (1)
• C
  90% (46)
• D
  6% (3)

Explanation

In AWS, public IP addresses (Elastic IPs or auto-assigned IPs) are associated directly with EC2 instance network interfaces at the AWS hypervisor level - AWS itself performs the 1:1 NAT mapping, so the Check Point Gateway never sees or manages those public IPs. This is why option C is correct: you cannot configure NAT on Check Point for this purpose because the public IPs are already bound directly to the instances, bypassing the gateway's NAT table entirely.

Why the distractors fail:

• A is wrong because you don't "add" public IPs to Check Point and configure NAT through it - the IPs live at the AWS infrastructure layer, not the appliance.
• B is wrong because NAT isn't exclusively an ELB function; ELB handles load distribution, while the 1:1 public-to-private IP translation is handled by the AWS VPC fabric for all instances.
• D is wrong because NAT on Check Point is not scoped to internal load balancers - it simply isn't the mechanism AWS uses here at all.

Memory tip: Think of AWS public IPs as "welded to the instance" - AWS handles the NAT before traffic ever reaches Check Point, so the gateway is out of the loop entirely.

No community discussion yet for this question.