What happens when a private VM instance in Google Cloud tries to access the internet without Cloud NAT configured?
Think about how private IP addresses work and what is needed to reach the internet.
Private VM instances do not have external IP addresses. Without Cloud NAT, they cannot translate their internal IP to a public IP, so they cannot reach the internet.
You have multiple private VM instances in different subnets within the same VPC. You want all of them to access the internet using Cloud NAT. Which Cloud NAT configuration is best?
Cloud NAT can serve multiple subnets from one gateway.
One Cloud NAT gateway can be configured to serve multiple subnets in the same VPC, simplifying management and reducing costs.
Which Cloud NAT IP allocation mode allows you to specify a fixed set of external IP addresses for NAT instead of using automatically assigned ones?
One mode lets you pick your own external IPs.
Manual IP allocation mode lets you specify your own external IP addresses for Cloud NAT instead of letting Google assign them automatically.
Which of the following is a recommended security best practice when configuring Cloud NAT for private instances?
Think about controlling traffic flow even with NAT.
Firewall rules should be used to restrict outbound traffic from private instances to only allowed destinations, enhancing security even when Cloud NAT is used.
During a sudden high volume of outbound connections from private instances using Cloud NAT, what behavior should you expect from Cloud NAT?
Cloud NAT is designed to handle scaling transparently.
Cloud NAT automatically scales its capacity to handle bursts of outbound connections from private instances without dropping packets, ensuring smooth connectivity.