Google Professional Cloud Network Engineer Exam - 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?

AConfigure a target pool, and create protocol forwarding rules for each external IP address.

BConfigure a backend service, and create an external network load balancer for each external IP address

CConfigure a target instance, and create a protocol forwarding rule for each external IP address to be mapped to the instance.

DConfigure the Compute Engine Instances' network Interface external IP address from None to Ephemeral Add as many external IP addresses as required

Show Suggested 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.

by Ernest at Nov 22, 2023, 11:39 AM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Network Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Miriam

4 months ago

B is definitely the way to go for handling multiple IPs efficiently!

upvoted 0 times

...

Geraldine

4 months ago

I think D is too limiting with just ephemeral IPs.

upvoted 0 times

...

Viva

4 months ago

Wait, can we really use protocol forwarding for ESP traffic?

upvoted 0 times

...

Eladia

4 months ago

I disagree, A might work better for multiple IPs.

upvoted 0 times

...

Alline

4 months ago

Option B seems like the best choice for load balancing.

upvoted 0 times

...

Toshia

5 months ago

I don’t recall much about configuring network interfaces for external IPs. Option D seems like it could work, but I’m not confident about the specifics.

upvoted 0 times

...

Alonzo

5 months ago

I’m a bit confused about the protocol forwarding rules. I feel like option C could be the right choice, but I need to double-check how it works with ESP traffic.

upvoted 0 times

...

Nadine

5 months ago

I think option B sounds familiar; it might be related to backend services and external load balancers, which we practiced in class.

upvoted 0 times

...

Ilene

5 months ago

I remember something about using target pools for load balancing, but I'm not sure if that's the right approach for multiple IPs.

upvoted 0 times

...

Danica

5 months ago

Hmm, I'm not sure about D. Changing the instance's external IP to ephemeral and adding more doesn't seem like it would map the existing reserved IPs as required. I think I'll rule that one out.

upvoted 0 times

...

Sheron

5 months ago

This seems straightforward enough. I'd go with option B - configuring a backend service and creating an external network load balancer for each IP address. That should meet the requirements.

upvoted 0 times

...

Ryan

5 months ago

I'm a bit confused by the wording of the question. Does "protocol forwarding rule" mean something specific in the context of Compute Engine? I'll need to double-check the documentation to make sure I understand that part.

upvoted 0 times

...

Margarita

5 months ago

Okay, I think I've got this. The key is mapping multiple existing reserved external IP addresses to the instance, and handling ESP traffic. I'm pretty confident option C is the way to go here.

upvoted 0 times

...

Dylan

5 months ago

Hmm, this looks like a tricky one. I'll need to carefully read through the requirements and think through the different options.

upvoted 0 times

...

Ailene

5 months ago

Wait, I'm a little confused. Is a "what-if scenario" the same as a "process" in this context? I need to make sure I'm clear on the terminology before I answer.

upvoted 0 times

...

Gail

6 months ago

Transactions seem like the most relevant option based on the description, but I want to double-check the others just to be sure.

upvoted 0 times

...

Devora

6 months ago

This seems like a straightforward question about file systems. I'll think through the key features of FAT32 and see which one best matches the question.

upvoted 0 times

...

Lavelle

2 years 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

2 years 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

2 years 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

Mitsue

2 years ago

Great, that should ensure the application meets the necessary requirements.

upvoted 0 times

...

Francoise

2 years ago

Yes, let's go ahead and implement option B for exposing the application to the new customer.

upvoted 0 times

...

James

2 years ago

Should we proceed with configuring a backend service and creating external network load balancers?

upvoted 0 times

...

Velda

2 years ago

Exactly, it meets both requirements effectively.

upvoted 0 times

...

Crissy

2 years ago

That's true, it also allows us to handle the IP Encapsulating Security Payload (ESP) traffic.

upvoted 0 times

...

Suzi

2 years ago

Yes, setting up a backend service and an external network load balancer would help map the multiple external IP addresses.

upvoted 0 times

...

Carlene

2 years ago

Option B does seem like the most appropriate choice for this scenario.

upvoted 0 times

...

Glendora

2 years 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

...