New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Professional Cloud Network Engineer Exam - Topic 4 Question 91 Discussion

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

You are designing a packet mirroring policy as pan of your network security architecture for your gaming workload. Your Infrastructure is located in the us-west2 region and deployed across several zones: us-west2-

a. us-west2-b. and us-west2-c The Infrastructure Is running a web-based application on TCP ports 80 and 443 with other game servers that utilize the UDP protocol. You need to deploy packet mirroring policies and collector instances to monitor web application traffic while minimizing inter-zonal network egress costs.

Following Google-recommended practices, how should you deploy the packet mirroring policies and collector instances?

Show Suggested Answer Hide Answer
Suggested Answer: D

Create Packet Mirroring Policies:

You need to create three packet mirroring policies, one for each zone (us-west2-a, us-west2-b, and us-west2-c). This ensures that each zone's traffic is mirrored appropriately without unnecessary cross-zone traffic.

Create Collector Instances:

Set up one group of collector instances for the us-west2 region. Having a single group of collector instances for the entire region minimizes the number of instances required and simplifies the management while keeping egress costs low since the collectors are within the same region.

Configuration of Policies:

Each packet mirroring policy should be configured to match traffic for its specific zone. Use instance-tags to identify and match the relevant instances within each zone. This helps in correctly capturing the traffic from the appropriate sources.

Filter for TCP Traffic:

Create a filter for TCP traffic (ports 80 and 443). This step ensures that only the relevant web application traffic is mirrored, reducing the amount of data processed and improving efficiency.

Cost Efficiency:

By having packet mirroring policies specific to each zone and a regional collector group, you reduce inter-zonal network egress costs. The data remains within the same region, avoiding extra charges associated with cross-zone traffic.


Google Cloud Packet Mirroring Documentation

Best Practices for Packet Mirroring

Cost Management in Google Cloud

This solution aligns with Google-recommended practices by ensuring efficient traffic capture, minimal inter-zonal costs, and streamlined management of the packet mirroring setup.

Contribute your Thoughts:

0/2000 characters
Willow
3 months ago
C simplifies things, but not sure if it covers all zones properly.
upvoted 0 times
...
Stephanie
4 months ago
Wait, why would you create three policies? Isn't that overkill?
upvoted 0 times
...
Sabrina
4 months ago
D looks good too, but why only one collector group?
upvoted 0 times
...
Jean
4 months ago
I think B is better, subnets are more reliable for traffic matching.
upvoted 0 times
...
Lashonda
4 months ago
Option A seems solid, matching by instance-tags is smart.
upvoted 0 times
...
Nan
5 months ago
I’m leaning towards option B, but I’m not entirely confident. I remember something about using subnets, but I’m not sure if that’s the best way to go for this scenario.
upvoted 0 times
...
Ivette
5 months ago
I think option D sounds right because it mentions creating separate policies for each zone, which seems to align with best practices we covered.
upvoted 0 times
...
Nadine
5 months ago
I'm a bit unsure about whether to use instance-tags or subnets for matching traffic. I feel like we practiced something similar, but I can't recall the details.
upvoted 0 times
...
Elinore
5 months ago
I remember we discussed the importance of minimizing egress costs, so I think using one group of collector instances for the entire region might not be the best approach.
upvoted 0 times
...
Melvin
5 months ago
This is a good test of my understanding of packet mirroring and network security best practices. I'm confident that option D is the way to go - it aligns with the requirements and the Google-recommended practices.
upvoted 0 times
...
Arlene
5 months ago
Hmm, I'm a bit confused about the subnet-based approach in option B. Wouldn't that be more complex to manage than the instance-tag approach? I'm leaning towards option A or C.
upvoted 0 times
...
Jesus
5 months ago
Okay, I think I've got this. The key is to create separate policies for each zone to minimize inter-zonal network egress costs, and use instance-tags to filter the traffic. I'm going with option A.
upvoted 0 times
...
Walton
5 months ago
This question seems straightforward, but I want to make sure I understand the requirements correctly. I'll need to review the Google-recommended practices to determine the best approach.
upvoted 0 times
...
Ty
5 months ago
Implementing standard setup and teardown functions at the test case level could be a good solution. It would help reduce duplication and make the test suite more maintainable.
upvoted 0 times
...
Emiko
5 months ago
This is a good question to test our knowledge of the login process. I think the key is to focus on the definition of identification - it's about verifying the user's identity, not their authorization or authentication. I'll go with option B.
upvoted 0 times
...
Van
1 year ago
Hmm, maybe I should reconsider my choice then.
upvoted 0 times
...
Gwenn
1 year ago
I agree with Gilbert, A seems to be the most logical choice.
upvoted 0 times
...
Olene
1 year ago
Option B seems a bit overkill with the separate policies and collectors for each zone. Unless there are specific requirements to segregate the traffic, I'd lean towards Option C.
upvoted 0 times
...
Gilbert
1 year ago
But A seems to be following Google-recommended practices.
upvoted 0 times
...
Margarita
1 year ago
Hah, these cloud networking questions can really make your head spin sometimes. I'd probably go with Option C - keep it simple, stupid, right?
upvoted 0 times
Elke
1 year ago
Definitely. Option C minimizes complexity and still gets the job done.
upvoted 0 times
...
Wade
1 year ago
I think Option C makes sense too. Less room for error that way.
upvoted 0 times
...
Cordelia
1 year ago
Yeah, I agree. Keeping it simple is usually the best approach.
upvoted 0 times
...
Reuben
1 year ago
Option C seems like the most straightforward choice.
upvoted 0 times
...
...
Stephanie
1 year ago
Hmm, Option D looks good. Separating the policies by zone will give more visibility, and having a single collector group is a smart way to keep costs down.
upvoted 0 times
...
Dino
1 year ago
I like the efficiency of Option C, but I'm concerned about the ability to differentiate between the zones. Perhaps Option D would provide more granular control while still keeping the collector instances centralized.
upvoted 0 times
Loren
1 year ago
That's true, Option D might be a better choice for granular control while still keeping collector instances centralized.
upvoted 0 times
...
Stacey
1 year ago
I agree, but Option D could offer more control over traffic in each specific zone.
upvoted 0 times
...
Angelyn
1 year ago
Option C seems like a good choice for centralized monitoring of web server traffic.
upvoted 0 times
...
...
Kent
2 years ago
Option C seems the most straightforward. One policy and one group of collector instances for the whole region should be sufficient to monitor the web traffic while minimizing costs.
upvoted 0 times
Taryn
1 year ago
I agree, having one policy for the entire region simplifies management and reduces complexity.
upvoted 0 times
...
Melvin
1 year ago
Option C seems the most straightforward. One policy and one group of collector instances for the whole region should be sufficient to monitor the web traffic while minimizing costs.
upvoted 0 times
...
...
Van
2 years ago
I disagree, I believe the answer is C.
upvoted 0 times
...
Gilbert
2 years ago
I think the answer is A.
upvoted 0 times
...

Save Cancel