1Z0-1072-25 Question 106
Select 2Your organization has two VCNs in the same region (VCN-A and VCN-B), which you have successfully connected with a local peering gateway. You now need to connect these two VCNs to a third VCN (VCN-C) in a different region so that all three VCNs can communicate. Which two actions must you take to enable traffic between the local-peered VCNs and the remote VCN?
- A
Create a Remote Peering Gateway (RPG) in each region and establish peering between these gateways
- B
Use the existing local peering gateway in VCN-A and VCN-B to directly connect to VCN-C
- C
Configure the route tables in the local VCNs and the remote VCN to direct traffic to their respective Remote Peering Gateways
- D
Deploy a NAT Gateway in the remote VCN and route all local traffic through it
Show answer and explanation
Correct answers: A, C
Explanation
To enable communication between VCNs in different regions, you must create Remote Peering Gateways and peer them across the regions. Local Peering Gateways are used only when both VCNs reside in the same region. After establishing the remote peering connection, remember to update your route tables so that traffic is correctly directed to the Remote Peering Gateways. For reference, see the official Oracle documentation on local peering (https://docs.oracle.com/en-us/iaas/Content/Network/Tasks/localVCNpeering.htm) and remote peering (https://docs.oracle.com/en-us/iaas/Content/Network/Tasks/remoteVCNpeering.htm).
- A. Correct.
Correct. For remote VCN communication across different regions, each region needs its own Remote Peering Gateway. You then connect (peer) these gateways to allow traffic to traverse regions.
- B. Incorrect.
Incorrect. A local peering gateway only facilitates communication within the same region. You cannot connect to a VCN in a different region using a local peering gateway.
- C. Correct.
Correct. After creating and peering the Remote Peering Gateways, each VCN� route table must send traffic destined for the remote VCN to its own Remote Peering Gateway, ensuring end-to-end connectivity.
- D. Incorrect.
Incorrect. A NAT Gateway covers outbound internet-bound traffic or specific translation requirements, not private VCN-to-VCN communication. Remote peering does not rely on NAT Gateways.