Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional-Cloud-Network-Engineer Topic 7 Question 72 Discussion

Actual exam question for Google's Professional Cloud Network Engineer exam
Question #: 72
Topic #: 7
[All Professional Cloud Network Engineer Questions]

You are deploying an application that runs on Compute Engine instances. You need to determine how to expose your application to a new customer You must ensure that your application meets the following requirements

* Maps multiple existing reserved external IP addresses to the Instance

* Processes IP Encapsulating Security Payload (ESP) traffic

What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: C

The correct answer is C. Configure a target instance, and create a protocol forwarding rule for each external IP address to be mapped to the instance.

This answer is based on the following facts:

A target instance is a Compute Engine instance that handles traffic from one or more forwarding rules1. You can use target instances to forward traffic to a single VM instance from one or more external IP addresses2.

A protocol forwarding rule specifies the IP protocol and port range for the traffic that you want to forward3. You can use protocol forwarding rules to forward traffic of any IP protocol, including ESP4.

The other options are not correct because:

Option A is not possible. You cannot create protocol forwarding rules for a target pool. A target pool is a group of instances that receives traffic from a network load balancer5.

Option B is not suitable. You do not need to create an external network load balancer for each external IP address. An external network load balancer distributes traffic among multiple backend instances based on the destination IP address and port. You can use a single load balancer with multiple forwarding rules to map multiple external IP addresses to the same backend service.

Option D is not feasible. You cannot add multiple external IP addresses to a single network interface of a Compute Engine instance. Each network interface can have only one external IP address that is either ephemeral or static. You can use alias IP ranges to assign multiple internal IP addresses to a single network interface, but not external IP addresses.


Contribute your Thoughts:

Lavelle
10 days ago
Haha, I was just about to suggest option D, but then I realized that would probably be a terrible idea. Ephemeral IP addresses? No way, we need those static reserved IPs to meet the requirements.
upvoted 0 times
...
Roslyn
11 days ago
You know, I was initially thinking option C, but after reconsidering, I think B is the way to go. Creating a target instance and forwarding rules might work, but a load balancer seems like a more robust and scalable solution for this scenario.
upvoted 0 times
...
Lashawn
12 days ago
I agree, option B does seem the most appropriate choice here. Setting up a backend service and an external network load balancer would allow us to map the multiple external IP addresses to the instance and handle the ESP traffic requirements.
upvoted 0 times
...
Glendora
13 days ago
Hmm, this question seems a bit tricky. We need to find a way to map multiple existing reserved external IP addresses to the Compute Engine instance and handle ESP traffic. I'm leaning towards option B, as a backend service with an external network load balancer seems like the best fit for this requirement.
upvoted 0 times
...

Save Cancel