Answer-first summary for fast verification
Answer: An external IP address has been configured on the instance.
The most likely cause is that the instance has an external IP address configured. Cloud NAT is designed to provide outbound NAT for instances without external IPs. If an instance has an external IP (ephemeral or static), it will use that IP for outbound traffic instead of Cloud NAT, bypassing the NAT gateway entirely. Options A (multiple interfaces) and C (static routes) are unrelated to Cloud NAT's primary function of providing NAT for instances lacking external IPs. Option D (load balancer external IP) affects inbound traffic, not outbound NAT usage.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
One of your instances is not using Cloud NAT for outbound traffic after configuration. What is the most likely reason for this issue?
A
The instance has been configured with multiple interfaces.
B
An external IP address has been configured on the instance.
C
You have created static routes that use RFC1918 ranges.
D
The instance is accessible by a load balancer external IP address.