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

Creating three separate policies for each zone and then pointing them to a single group of collectors (if not strategically placed) could increase inter-zonal costs and adds unnecessary management overhead compared to a single regional policy.

Creating one packet mirroring policy for the entire `us-west2` region provides a single point of management, and deploying one group of collector instances (e.g., a regional Managed Instance Group with a regional Internal Load Balancer) across all zones ensures mirrored traffic is directed to the nearest collector, minimizing inter-zonal network egress costs.

While creating three zonal policies with three zonal collector groups effectively minimizes inter-zonal costs by containing traffic within zones, managing three separate policies for a single region is less efficient than a single regional policy.

Similar to option C, creating three zonal policies and three zonal collector groups is more administratively complex than a single regional policy, even if it helps minimize inter-zonal costs.