1Z0-997-25 Question 133
Select 2A retail company plans to run its Oracle Database on Google Cloud using Oracle Database@Google Cloud, while keeping key backend microservices in Oracle Cloud Infrastructure (OCI). They want to establish private, low-latency communication between the microservices in OCI and the database in Google Cloud via Oracle Interconnect for Google Cloud. Which two steps are required to achieve this setup?
- A
- Configure BGP sessions between an OCI DRG and a Google Cloud Router over the Interconnect, ensuring non-overlapping IP ranges on both sides.
- B
- Enable a NAT gateway in Google Cloud and translate the Oracle Database private IP to a public IP for inbound connections from OCI.
- C
- Use the same CIDR block in both OCI and Google Cloud to simplify interconnect routing rules.
- D
- Set up route tables in both OCI and Google Cloud to direct Oracle Database traffic over the Interconnect using private IP addresses.
- E
- Deploy a separate public load balancer in OCI to forward all database queries to the Oracle Database@Google Cloud.
Show answer and explanation
Correct answers: A, D
Explanation
To implement Oracle Interconnect for Google Cloud with Oracle Database@Google Cloud, you must establish private connectivity between OCI and Google Cloud. This requires configuring BGP sessions between an OCI DRG and a Google Cloud Router, using non-overlapping IP ranges. You also need to ensure each environment� route tables forward traffic specifically for the database subnets over the private interconnect. Refer to Oracle documentation on 'Configuring Oracle Interconnect for Google Cloud' and Google Cloud documentation on 'Using Cloud Router for IP routing' for detailed steps and best practices.
- A. Correct.
Option 1: CORRECT. Configuring BGP sessions between OCI's Dynamic Routing Gateway (DRG) and Google Cloud Router is a key requirement. Both environments must use distinct CIDR blocks so that routes can be advertised without conflict.
- B. Incorrect.
Option 2: INCORRECT. Using a NAT gateway in Google Cloud would expose your database traffic to the public internet, defeating the purpose of a secure interconnect. The goal is to leverage private connectivity for reduced latency and improved security.
- C. Incorrect.
Option 3: INCORRECT. Using overlapping CIDR blocks can cause route conflicts and break communication between OCI and Google Cloud. Non-overlapping IP ranges on each side are mandatory.
- D. Correct.
Option 4: CORRECT. Properly configured route tables on both the OCI and Google Cloud sides ensure traffic is directed over the private interconnect, enabling the microservices in OCI to reach the Oracle Database on Google Cloud.
- E. Incorrect.
Option 5: INCORRECT. A public load balancer introduces unnecessary external exposure and would not leverage the private interconnect path. Additionally, Oracle Database@Google Cloud uses private IP communication for secure connectivity.