1Z0-1151-25 Question 74
Single answerYour organization needs to connect a production Virtual Cloud Network (VCN) in Oracle Cloud Infrastructure (OCI) to a Virtual Private Cloud (VPC) in Google Cloud using Oracle Interconnect for Google Cloud. You have created the required VLAN attachments and configured a Dynamic Routing Gateway (DRG) on the OCI side as well as a Cloud Router on the Google side. Which of the following steps is essential for establishing BGP adjacency between the two environments and enabling dynamic routing across the interconnect?
- A
A) Enable and configure the BGP session on both the OCI DRG attachment and the Google Cloud Router using the correct IPs and Autonomous System Numbers (ASNs).
- B
B) Configure static routes in the VCN route table and in the Google Cloud VPC's route table to exchange all necessary subnets.
- C
C) Attach the DRG only to your default VCN route table to ensure all outbound traffic is automatically forwarded to the Google Cloud Router.
- D
D) Enable IP packet forwarding on the VMs within OCI and Google Cloud, bypassing the need for a formal routing protocol.
Show answer and explanation
Correct answer: A
Explanation
To implement Oracle Interconnect for Google Cloud, you must configure dynamic routing (BGP) on both sides of the connection. On the OCI side, you use the DRG and a VLAN attachment with enabled BGP, while on the Google Cloud side, you configure a Cloud Router with the correct IP addresses and ASNs. Oracle� documentation (e.g., 'OCI Networking: Oracle Interconnect for Google Cloud') recommends using dynamic routing to simplify route changes and ensure a fault-tolerant connection. Merely attaching a DRG, relying on static routes, or enabling IP forwarding on the VMs does not fulfill the requirement for end-to-end dynamic routing across the interconnect.
- A. Correct.
A) Correct. In order for dynamic routing to function properly, you must configure a BGP session on both the OCI DRG and the Google Cloud Router. Ensuring that the ASN values match your design, and assigning the correct private IP addresses for BGP, is mandatory for a successful adjacency and dynamic route exchange.
- B. Incorrect.
B) Incorrect. While static routes might be used in certain test or limited scenarios, the purpose of Oracle Interconnect for Google Cloud is to leverage dynamic routing via BGP. Relying solely on static routes does not establish a BGP adjacency, nor does it provide full resiliency or scalability.
- C. Incorrect.
C) Incorrect. Simply attaching the DRG to a default route table will not establish dynamic routing or BGP. You must explicitly configure BGP peer addresses and ASN values to exchange routes across the interconnect.
- D. Incorrect.
D) Incorrect. Enabling IP forwarding on VMs is not sufficient to establish inter-network routing. BGP sessions at the DRG and Cloud Router levels are still required for propagating routes and ensuring reliable connectivity.