Design Partner Interconnect for geo-redundancy across two region/metro pairs (region1/metro1 and region2/metro2). According to Google best practices, how should VLAN attachments and Cloud Routers be deployed?

The correct approach for geo-redundancy with Partner Interconnect involves distributing Cloud Routers and VLAN attachments across distinct metropolitan areas and zones. Each region (region1 and region2) should have its own Cloud Router. Within each region, the Cloud Router should be configured with two VLAN attachments, each connecting to a different zone within the respective metro (e.g., metro1-zone1-x and metro1-zone2-x for region1). This ensures that if one metro or zone experiences an outage, traffic can fail over to the other zone within the same metro, or to the other region's metro and zones, maintaining connectivity. Incorrect options propose configurations that lack full redundancy. For example, connecting all VLAN attachments to a single metro or zone creates a single point of failure. Similarly, having only one VLAN attachment per Cloud Router limits redundancy within that region.