1Z0-1072-25 Question 114
Single answerYour organization has three separate Virtual Cloud Networks (VCNs) named Dev, Test, and Production in the same OCI region. The Production VCN is already attached to a Dynamic Routing Gateway (DRG) and connected to on-premises over IPSec. You need to allow traffic from the Dev and Test VCNs to reach on-premises using the same DRG attachment on the Production VCN. Which action is required to implement this transit routing scenario?
- A
Create local peering gateways in the Dev and Test VCNs, peer them with the Production VCN, and update the relevant route tables to forward traffic to on-premises through the Production VCN.
- B
Detach the Production VCN from the DRG and reattach it individually to each new VCN so that Dev and Test can route on-premises traffic through their own DRG attachments.
- C
Create a remote peering gateway in each of the Dev and Test VCNs and connect them to the Production VCN� remote peering gateway to enable transit routing within the same region.
- D
Implement a NAT Gateway in both the Dev and Test VCNs to forward all private subnet traffic to on-premises through the DRG.
Show answer and explanation
Correct answer: A
Explanation
In Oracle Cloud Infrastructure, transit routing in a single region typically involves a Dynamic Routing Gateway (DRG) and local peering gateways (LPGs). You create LPGs in each of the additional VCNs (Dev and Test) and peer them with the Production VCN, which terminates the DRG connection to on-premises. This setup allows traffic from Dev and Test to be forwarded to the DRG through the Production VCN. Refer to the Oracle documentation on transit routing (e.g., 'VCN Peering' and 'Using a DRG and a Peering for Transit') for detailed implementation steps and best practices.
- A. Correct.
Option 1 is correct. For transit routing within the same OCI region, the standard approach involves creating local peering gateways (LPGs). You would create LPGs in both Dev and Test, peer them with an LPG in Production, and configure route tables in each VCN to forward on-premises traffic to the Production VCN, which is already attached to the DRG. This ensures all traffic from Dev and Test passes through the Production VCN to reach the on-premises environment.
- B. Incorrect.
Option 2 is incorrect. Detaching the Production VCN from the DRG and then attaching a dedicated DRG for each VCN is not required. OCI allows you to create a single DRG attachment and use local peering for transit routing to the on-premises environment through the Production VCN.
- C. Incorrect.
Option 3 is incorrect. A remote peering gateway is used for connecting VCNs across different regions, not within the same region. Since all three VCNs are in the same region, local peering gateways are the recommended method.
- D. Incorrect.
Option 4 is incorrect. A NAT Gateway handles outbound internet traffic for private subnets and does not forward on-premises traffic via a DRG. You must configure local peering gateways and correct route table entries for transit routing to on-premises.