1Z0-1151-25 Question 69
Select 3A financial services company is rolling out a cross-cloud trading application with the backend database on Oracle Autonomous Database in OCI and analytics dashboards hosted in Azure. They want to use Oracle Interconnect for Azure to ensure low-latency, private connectivity between the two environments�bypassing the public internet. Which three steps must they include in their implementation so that application traffic flows privately over the interconnect?
- A
Create a Dynamic Routing Gateway (DRG) on OCI and attach a FastConnect virtual circuit to it.
- B
Configure an ExpressRoute circuit on Azure and peer it with an Azure Virtual Network Gateway.
- C
Establish an IPSec VPN between the Azure Virtual Network Gateway and the OCI VCN.
- D
Import all public IPs from Azure into the DRG route table on OCI for private routing.
- E
Update the route tables in both OCI and Azure to point relevant private IP CIDRs to the new interconnect.
Show answer and explanation
Correct answers: A, B, E
Explanation
When implementing the Oracle Interconnect for Azure, you typically provision FastConnect on the OCI side through a DRG and set up an ExpressRoute circuit in Azure. Configuring the route tables in both clouds to point to the interconnect ensures that traffic remains private and low-latency. IPSec VPNs or importing public IP addresses for private routing are not required or recommended for this dedicated interconnect solution. For further details, refer to the official Oracle documentation on �Connecting Oracle Cloud Infrastructure and Microsoft Azure with the Interconnect.�
- A. Correct.
Correct. You must create a DRG in OCI and attach FastConnect to enable a private inter-region connection. FastConnect is Oracle� dedicated network connectivity solution that works in tandem with Azure ExpressRoute for the interconnect.
- B. Correct.
Correct. On Azure, you configure an ExpressRoute circuit and link it with a Virtual Network Gateway. This sets up the Azure side of the private pathway that pairs with OCI� FastConnect.
- C. Incorrect.
Incorrect. An IPSec tunnel is a different solution for secure connectivity and not part of the Oracle Interconnect for Azure setup. The Interconnect relies on dedicated circuits (ExpressRoute and FastConnect), not VPN.
- D. Incorrect.
Incorrect. The Oracle Interconnect for Azure is designed to route private IP ranges across both clouds. Importing public IPs for private routing is not a standard requirement or best practice in this scenario.
- E. Correct.
Correct. You must update both OCI route tables and Azure route tables (e.g., user-defined routes in Azure) to direct relevant traffic toward the interconnect rather than using the public internet.