1Z0-1151-25 Question 76
Single answerYour organization is implementing Oracle Interconnect for Google Cloud to establish secure, private connectivity between an Autonomous Database in OCI and an application running on Google Cloud. You have created a VCN in OCI, attached a Dynamic Routing Gateway (DRG), and configured both public and private peering on the Google Cloud side with Cloud Router. Despite these configurations, the application on Google Cloud is unable to reach the private IP address of the Autonomous Database in OCI. Which action must you take to enable successful end-to-end connectivity?
- A
Add a route to the DRG route table so that traffic from your VCN is forwarded to the Google Cloud peering attachment.
- B
Enable VCN Flow Logs in OCI to record traffic flows between the VCN subnets and Google Cloud.
- C
Enable cross-region routing in the Cloud Router to distribute routes across different Google Cloud regions.
- D
Update the Google Cloud route table to send traffic bound for the Oracle Autonomous Database private IP to an Internet Gateway.
Show answer and explanation
Correct answer: A
Explanation
In an Oracle Interconnect for Google Cloud scenario, you need to configure routing on both the OCI side and the Google Cloud side for private connectivity. Ensuring that the DRG route table has the correct route to the Google Cloud peering attachment is essential. This configuration, along with Cloud Router� BGP-based route exchanges, enables traffic to flow securely between the two clouds. Refer to the official OCI documentation on DRG route configuration and Google Cloud documentation on Cloud Router for best practices.
- A. Correct.
Correct. Even if you have established peering connections and Cloud Router configurations, you must ensure your DRG route table contains a rule that points traffic from OCI networks toward the Google Cloud peering attachment. Without this route, traffic cannot flow from OCI to GCP over the interconnect.
- B. Incorrect.
Incorrect. Flow Logs help troubleshoot or analyze traffic but do not affect the underlying routing configuration required to forward traffic between OCI and Google Cloud.
- C. Incorrect.
Incorrect. Cross-region routing within Google Cloud does not address the requirement to configure forwarding rules on the OCI side. You still need correct DRG routes in OCI to enable connectivity.
- D. Incorrect.
Incorrect. Sending traffic directly to an Internet Gateway would bypass private connectivity. Oracle Interconnect for Google Cloud is specifically designed to keep traffic private, so routing to an Internet Gateway would be a misconfiguration.