CLOUD-NETWORK practice question 7 of 30

You are designing a packet mirroring policy as pan of your network security architecture for your gaming workload. Your Infrastructure is located in…

Full set: 233 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?
Answer options
A: Create three packet mirroring policies: one for each zone. Create three groups of collector instances: one group for each zone. Configure each policy to match traffic for Its zone based on instance-tags, and create a filter for TCP traffic. Correct answer
B: Create three packet mirroring policies: one for each zone. Create three groups of collector instances: one group for each zone. Configure each policy to match traffic for its zone based on subnets, and create a filter for TCP traffic
C: Create one packet mirroring policy for the us-west2 region. Create one group of collector instances for the us-west2 region Configure the packet mirroring policy to match traffic for web server instances based on instance-tags, and create a filter for TCP traffic.
D: Create three packet mirroring policies: one for each zone. Create one group of collector instances for the us-west2 region. Configure each packet mirroring policy to match traffic for its zone based on instance-tags, and create a filter for TCP traffic
Correct Answer:
A. Create three packet mirroring policies: one for each zone. Create three groups of collector instances: one group for each zone. Configure each policy to match traffic for Its zone based on instance-tags, and create a filter for TCP traffic.
Explanation

The primary goal is to minimize inter-zonal network egress costs. Packet Mirroring egress costs are incurred when mirrored traffic is sent from a source VM in one zone to a collector VM in a different zone. To eliminate this cost, the collector instances must be located in the same zone as the source instances being mirrored. The best practice is to create a separate collector instance group (e.g., behind a zonal Internal Load Balancer) in each zone (us-west2-a, us-west2-b, us-west2-c). Then, create a separate packet mirroring policy for each zone, configured to send traffic from sources in that zone only to the collectors in the same zone.

Why Incorrect

B. Using instance tags is more flexible and granular for selecting specific web servers than using subnets, which might contain non-web server instances.
C. A single regional policy and collector group would send traffic across zones, incurring the exact egress costs the question seeks to avoid.
D. Using a single regional collector group forces traffic from at least two of the zones to cross zonal boundaries, incurring egress costs.

References

1. Google Cloud Documentation, "Packet Mirroring pricing". This page states, "You are charged for the amount of data that is processed by Packet Mirroring... Standard network egress pricing applies to traffic between zones or regions." This confirms the cost model.

2. Google Cloud Documentation, "Packet Mirroring overview". Section: "Collector destinations". It notes, "For the collector destination, we recommend that you use an internal load balancer... To avoid inter-zonal egress charges, you can create a forwarding rule and backend service for each zone where you have mirrored sources." This directly supports the architecture in option A.

Scroll to Top