What is a typical consequence for external entities when contacting a device behind NAT?

What is a typical consequence for external entities when contacting a device behind NAT?

• A. They reach the device via the NAT device's public IP.
• B. They reach the private IP address directly.
• C. Connection is impossible under any circumstance.
• D. Port numbers are not used in NAT.

Answer: (A)

When a device sits behind NAT, the outside world only sees the NAT device’s public IP. External systems attempting to reach that internal device send traffic to that public IP. The NAT then uses its translation table to forward the traffic to the correct private IP and port inside the local network. This is why the typical outcome is that the device is reached via the NAT’s public IP, not directly at its private address. Port numbers on the public side are part of how the NAT distinguishes multiple internal connections and routes responses back to the right internal device. The other statements don’t fit: you don’t reach the private IP directly from outside, a connection can occur if there’s a valid mapping (for example, via port forwarding), and NAT does rely on port numbers for its translations.

When a device sits behind NAT, the outside world only sees the NAT device’s public IP. External systems attempting to reach that internal device send traffic to that public IP. The NAT then uses its translation table to forward the traffic to the correct private IP and port inside the local network. This is why the typical outcome is that the device is reached via the NAT’s public IP, not directly at its private address. Port numbers on the public side are part of how the NAT distinguishes multiple internal connections and routes responses back to the right internal device. The other statements don’t fit: you don’t reach the private IP directly from outside, a connection can occur if there’s a valid mapping (for example, via port forwarding), and NAT does rely on port numbers for its translations.