1Z0-1151-25 Question 55
Select 2Your organization is building a multicloud environment for a new analytics application that must process data from both Oracle Cloud Infrastructure (OCI) and Microsoft Azure. The environment must support low-latency, private, high-bandwidth communication between OCI compute instances in a Virtual Cloud Network (VCN) and an Azure Virtual Network (VNet), and you have decided not to rely on your on-premises data center for any routing. Which two configurations will allow you to establish direct, private connectivity between OCI and Azure in an optimal manner?
- A
Deploy a site-to-site IPsec VPN from the Azure VNet to the OCI Dynamic Routing Gateway (DRG)
- B
Provision an OCI FastConnect circuit in a region that supports Oracle�Azure Interconnect
- C
Enable Azure ExpressRoute with a private peering connection to the OCI DRG
- D
Configure local peering between the Azure VNet and the OCI VCN
- E
Use a public load balancer in front of the Azure VNet for inbound traffic from the OCI VCN
Show answer and explanation
Correct answers: B, C
Explanation
In this scenario, you need a private, high-bandwidth, and low-latency connection between Oracle Cloud Infrastructure and Azure without routing through on-premises networks. Oracle FastConnect and Microsoft Azure ExpressRoute, used in tandem via the Oracle�Azure Interconnect, allow you to configure a direct connection between a VCN and a VNet in regions where the interconnect is supported. This solution provides predictable performance and avoids the public internet. Refer to Oracle� documentation on FastConnect (docs.oracle.com/en-us/iaas/Content/Network/Concepts/fastconnectoverview.htm) and Microsoft� documentation on ExpressRoute (learn.microsoft.com/azure/expressroute/expressroute-introduction) for configuration details and best practices.
- A. Incorrect.
Option 1: Deploy a site-to-site IPsec VPN from the Azure VNet to the OCI DRG. (Incorrect) � While an IPsec VPN can establish connectivity, it typically relies on the public internet, may have higher latency, and does not provide guaranteed bandwidth the way FastConnect�ExpressRoute does. This does not match the requirement for low latency and high throughput without on-premises dependency.
- B. Correct.
Option 2: Provision an OCI FastConnect circuit in a region that supports Oracle�Azure Interconnect. (Correct) � FastConnect provides a dedicated, private connection to OCI with predictable performance. When used in a supported Oracle�Azure Interconnect region, it allows you to seamlessly pair OCI VCNs with Azure VNets for low-latency, high-bandwidth communications.
- C. Correct.
Option 3: Enable Azure ExpressRoute with a private peering connection to the OCI DRG. (Correct) � ExpressRoute in Azure offers a dedicated circuit similar to FastConnect. By configuring private peering from ExpressRoute to the OCI DRG, you establish a direct, private mode of connectivity, satisfying the low-latency and high-bandwidth requirements without traversing on-premises networks.
- D. Incorrect.
Option 4: Configure local peering between the Azure VNet and the OCI VCN. (Incorrect) � Local peering is an OCI concept used for connecting peered VCNs within OCI regions, and similarly, Azure has VNet peering for its own networks. However, OCI VCN local peering cannot directly connect to an Azure VNet, so this does not meet the multicloud requirement between OCI and Azure.
- E. Incorrect.
Option 5: Use a public load balancer in front of the Azure VNet for inbound traffic from the OCI VCN. (Incorrect) � A public load balancer in Azure or OCI routes traffic over the public internet, which can introduce latency, bandwidth constraints, and does not provide a fully private connection. This conflicts with the stated requirements for a private, direct link with minimal latency.