1Z0-997-25 Question 108
Select 3Your company is deploying a multi-tier application that spans Oracle Cloud Infrastructure (OCI) and Microsoft Azure. The front-end services run on Azure VMs, the business logic layer is deployed in an OCI Compute instance, and Oracle Database@Azure is used as the primary data store. You plan to set up Oracle Interconnect for Azure to enable low-latency and secure connectivity between OCI and Azure. Which three actions must you perform to ensure private communication between the OCI instances and Oracle Database@Azure via the Interconnect?
- A
Configure a Virtual Cloud Network (VCN) in OCI and attach a Dynamic Routing Gateway (DRG) to it
- B
Set up a Virtual Network (VNet) in Azure and connect it to Oracle Interconnect for Azure
- C
Assign a public IP address to Oracle Database@Azure to simplify inbound traffic
- D
Use overlapping IP address spaces across OCI and Azure for easier route management
- E
Update both OCI and Azure route tables to direct traffic over the interconnect
Show answer and explanation
Correct answers: A, B, E
Explanation
To set up Oracle Interconnect for Azure in a hybrid architecture, you must configure both OCI (VCN + DRG) and Azure (VNet + Interconnect) correctly, ensuring non-overlapping IP addresses and appropriate route-table entries. This design allows secure, low-latency communication between services in OCI and Oracle Database@Azure. For more details, refer to Oracle Cloud Infrastructure documentation on Interconnect for Azure and Microsoft Azure documentation regarding ExpressRoute connectivity.
- A. Correct.
Correct. For private communication over Oracle Interconnect for Azure, you must configure an OCI VCN and attach a DRG. The DRG acts as a gateway for routing traffic between your OCI VCN and Azure VNet via the Interconnect.
- B. Correct.
Correct. On the Azure side, you need to create a VNet and establish connectivity to OCI using the Oracle Interconnect for Azure. This typically involves configuring Azure ExpressRoute linking to OCI FastConnect behind the scenes.
- C. Incorrect.
Incorrect. Oracle Database@Azure should remain private. Assigning a public IP would expose the database endpoints to the internet, going against the purpose of the private, low-latency interconnect.
- D. Incorrect.
Incorrect. You must avoid overlapping IP address ranges between the OCI VCN and the Azure VNet. Overlapping ranges complicate routing and violate best practices for cross-cloud connections.
- E. Correct.
Correct. Both sides must be properly configured to route traffic through the interconnect. You need to set routing rules in OCI� route tables and the Azure VNet to ensure private traffic flows between the business logic in OCI and the Oracle Database@Azure.