1Z0-1151-25 Question 86
Single answerYour organization wants to onboard Oracle Database@Azure to support a new mission-critical application hosted on Microsoft Azure. The solution must provide secure, low-latency connectivity to the Oracle databases and enable single sign-on through Azure Active Directory. Which of the following steps is required to properly configure the environment for these requirements?
- A
Provision the databases entirely within Azure Virtual Machines and use manual credential synchronization for authentication.
- B
Link your Azure subscription to your Oracle tenancy, configure the Oracle Database@Azure environment using the private interconnect, and enable single sign-on via Azure Active Directory federation.
- C
Create an external database in Azure Data Factory for Oracle Database@Azure and rely solely on public internet routing for connectivity.
- D
Use the on-premises Gateway in Azure to link to Oracle Cloud Infrastructure without configuring Azure Active Directory federation.
Show answer and explanation
Correct answer: B
Explanation
To properly onboard Oracle Database@Azure, you must link your Azure subscription to your Oracle Cloud Infrastructure tenancy, use the private cross-cloud interconnect for secure and high-throughput networking, and configure Azure Active Directory as the identity provider for single sign-on. This architecture ensures a streamlined, enterprise-grade environment with minimal latency and integrated identity management. Refer to official Oracle and Microsoft documentation on Oracle Database@Azure onboarding and identity federation for detailed configuration steps.
- A. Incorrect.
Incorrect. Deploying Oracle Databases only in Azure VMs misses the entire Oracle Database@Azure integrated architecture. You would lose benefits like automated connectivity, single sign-on, and high-performance interconnect.
- B. Correct.
Correct. A critical onboarding step for Oracle Database@Azure is linking your Azure subscription to Oracle Cloud Infrastructure, using the low-latency private interconnect for secure data transfer, and configuring Azure Active Directory as the federated identity provider for single sign-on. This approach meets the requirement for seamless authentication and minimal latency.
- C. Incorrect.
Incorrect. Simply creating an external database reference in Azure Data Factory does not set up the secure, low-latency path via the private interconnect, nor does it enable single sign-on with Azure AD. This option also uses public routing, which is less secure and higher latency.
- D. Incorrect.
Incorrect. The on-premises Gateway in Azure is not designed for direct Oracle Database@Azure connectivity or identity federation. You must specifically enable the private interconnect and federated identity to fulfill the integration requirements.