Oracle 1Z0-1115-23 Exam

Oracle Database Service for Azure (OracleDB for Azure) is an Oracle managed service delivering Oracle Database services in Oracle Cloud Infrastructure (OCI) directly to Microsoft Azure custom-ers through the OCI Azure Interconnect (a capability available between the two cloud environments in regions located around the world).

OracleDB for Azure uses a service-based approach, and is an alternative to manually creating complex cross-cloud deployments using the Interconnect.

FastConnect: With an Oracle Partner:

You can establish a FastConnect connection from your on-premise or remote data center to the data center where your Oracle Cloud resources are provisioned by requesting cloud connectivity services from any of Oracle's FastConnect partners. Oracle has integrated the FastConnect service with a geographically diverse set of IP, VPN, and Ethernet network providers and cloud exchanges to make it easy for you to establish a connection to Oracle Cloud services.

FastConnect: Colocation with Oracle:

If you have purchased colocation space from a data center provider, you can use Oracle FastCon-nect to establish connectivity from your network equipment in that colocation facility to your Oracle Cloud services provisioned at this location. Oracle will provide you a letter of authorization (LOA) that the data center provider will need in order to establish a direct cross-connect into Oracle's FastConnect edge devices provider will need in order to establish a direct cross

A fault domain is a grouping of hardware and infrastructure within an availability domain.

Fault domains provide anti-affinity: they let you distribute your instances so that the instances are not on the same physical hardware within a single availability domain.

To control the placement of your compute instances, bare metal DB system instances, or virtual machine DB system instances, you can optionally specify the fault domain for a new instance or instance pool at launch time.

If you closely look at the options, you can start eliminating some of them.

We can easily eliminate 'An Azure VNet with subnets and a virtual network gateway, and an OCI VCN with subnets and an attached service gateway' as we don't require service gateway to setup OCI-Azure Interconnect.

On similar lines, we can also eliminate the options where internet gateway and NAT gateway is pre-sent.

Hence 'An Azure VNet with subnets and a virtual network gateway, and an OCI VCN with sub-nets and an attached internet gateway' and 'An Azure VNet with subnets and a virtual network gateway, and an OCI VCN with subnets and an attached NAT gateway'.

As you can see in the architecture below, on the OCI side you require a Dynamic Routing Gate-way and on the Azure side you need a Virtual Network Gateway.

Hence the option 'An Azure VNet with subnets and a virtual network gateway, and an OCI VCN with subnets and an attached dynamic routing gateway' is CORRECT.

A fault domain is a grouping of hardware and infrastructure within an availability domain.

Fault domains provide anti-affinity: they let you distribute your instances so that the instances are not on the same physical hardware within a single availability domain.

To control the placement of your compute instances, bare metal DB system instances, or virtual machine DB system instances, you can optionally specify the fault domain for a new instance or instance pool at launch time.