1Z0-997-25 Question 132
Select 2You have been tasked with creating a secure, low-latency connection between an Oracle Database instance running on Google Cloud and critical business applications hosted in Oracle Cloud Infrastructure (OCI). You plan to leverage Oracle Interconnect for Google Cloud to achieve direct, private connectivity. Which two actions should you take to ensure the Database instance in GCP and your OCI workloads can communicate privately and minimize latency?
- A
Set up a FastConnect virtual circuit in OCI, and use Dedicated or Partner Interconnect in GCP while configuring dynamic routing with BGP to exchange private subnets
- B
Use a public load balancer on Google Cloud to route traffic to the Oracle Database instance for lower latency and easier network configuration
- C
Deploy multi-region replication of the Oracle Database from Google Cloud to Oracle Cloud Infrastructure for maximum performance
- D
Assign a dedicated public IP range on GCP to bypass private subnets, ensuring direct connectivity to OCI
- E
Use non-overlapping CIDR blocks and update route tables in both OCI and GCP to forward traffic over the interconnect
Show answer and explanation
Correct answers: A, E
Explanation
When implementing Oracle Interconnect for Google Cloud, you set up a FastConnect virtual circuit on the OCI side and a Dedicated/Partner Interconnect on the GCP side to create private, low-latency links. BGP routing is configured so each cloud can exchange private subnet routes. Additionally, ensuring non-overlapping CIDRs and properly updating route tables in both clouds are critical steps for end-to-end connectivity. These practices align with official documentation and best practices for OCI-FastConnect and Google Cloud Interconnect.
- A. Correct.
CORRECT. Establishing a FastConnect virtual circuit in OCI alongside a Dedicated or Partner Interconnect in Google Cloud, then configuring BGP to exchange private routes, is the recommended approach for secure, low-latency connectivity between the two environments.
- B. Incorrect.
INCORRECT. Placing a public load balancer in front of your Oracle Database on GCP does not leverage the private interconnect for low latency. It introduces public IP traffic flow, potentially increasing latency and risk.
- C. Incorrect.
INCORRECT. Multi-region replication may help with disaster recovery or high availability, but it does not provide the direct, private connectivity needed for minimal latency between GCP and OCI environments.
- D. Incorrect.
INCORRECT. Using a dedicated public IP range for GCP bypasses private subnets and is not aligned with the Oracle Interconnect for Google Cloud best practices, which recommend private addressing to maintain performance and security.
- E. Correct.
CORRECT. Non-overlapping IP address spaces (CIDRs) in OCI and GCP are essential for routing. You must also configure route tables on both sides so traffic destined for resources in either cloud is directed over the Interconnect rather than the public internet.