Free Google Professional Cloud Network Engineer Actual Exam Questions - Question 7 Discussion
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?
A is better to avoid cross-zone egress by keeping collectors local per zone.
Maybe D, since one collector group could simplify things while still having zone-specific policies.
It’s A because per-zone collectors minimize egress and targeting by instance-tags is precise.
I’m thinking option D might be worth considering because having separate policies per zone still targets the right traffic locally, but using a single collector group in the whole region can simplify resource management. Sure, it might increase some inter-zone egress costs, but if the number of mirrored packets isn’t huge, this might be a good trade-off. Also, filtering TCP traffic fits since the question focuses on web app monitoring. Anyone else think a single collector could make ongoing maintenance easier despite slightly higher egress?
Option B also makes sense because matching traffic by subnet keeps zone-specific focus, and having collectors per zone cuts inter-zone egress costs. Filtering TCP traffic covers the web app without overloading collectors.
Maybe D since separate policies per zone but a central collector can simplify management despite some egress.
A seems right since mirroring within each zone reduces inter-zone costs and filtering TCP matches the web traffic. Makes sense to keep collectors close to mirrored traffic.