1Z0-997-25 Question 111
Single answerYour company has deployed Oracle Database@Azure in a private subnet of an Azure Virtual Network (VNet) and set up Oracle Interconnect for Azure to enable low-latency communication with applications running in Oracle Cloud Infrastructure (OCI). You are tasked with ensuring that your OCI-based applications can connect securely and privately to the Oracle Database@Azure across the Interconnect. Which approach should you choose?
- A
Expose the Oracle Database@Azure using a public IP address and configure the OCI NAT Gateway for outbound traffic to Azure
- B
Set up a private IP-based route in both the Azure VNet and OCI VCN, ensuring the subnets are properly peered over the Interconnect
- C
Use a site-to-site VPN connection over the public Internet to connect the Azure VNet and OCI VCN
- D
Establish an inbound security rule in Azure that allows any public IP traffic from OCI to reach the Azure Database subnet
Show answer and explanation
Correct answer: B
Explanation
The Oracle Interconnect for Azure establishes a dedicated private link between an OCI Virtual Cloud Network (VCN) and an Azure Virtual Network (VNet), allowing private IP-based communication. To leverage this capability with Oracle Database@Azure, you must configure private IP routes, appropriate subnets, and matching security rules on both sides. These settings ensure secure, low-latency traffic flow. Refer to the official Oracle and Microsoft documentation on 'Oracle Interconnect for Azure' and 'Oracle Database@Azure' for network configuration best practices.
- A. Incorrect.
Incorrect. Assigning a public IP for the database and routing through the OCI NAT Gateway introduces internet-facing exposure and bypasses Interconnect advantages. This defeats the purpose of a private, low-latency link.
- B. Correct.
Correct. When using Oracle Interconnect for Azure, you should configure private IP-based routing on both the Azure side (VNet) and the OCI side (VCN). By ensuring correct routing in both environments and peering the private subnets, the application can securely connect to Oracle Database@Azure over the private Interconnect without exposing services to the public Internet.
- C. Incorrect.
Incorrect. While a VPN can connect the two clouds, it introduces unnecessary complexity and higher latency. The primary goal of Oracle Interconnect for Azure is to establish a dedicated, private, high-bandwidth connection without relying on the public internet.
- D. Incorrect.
Incorrect. Allowing any public IP traffic is too broad and insecure. Moreover, this approach circumvents the private connectivity and security benefits provided by Oracle Interconnect for Azure.