1Z0-997-25 Question 116
Single answerYour company is deploying a data analytics platform that spans Oracle Cloud Infrastructure (OCI) and another public cloud. The solution will rely on OCI for high-performance database services and use the second cloud for machine learning workloads. Management requires secure, low-latency connectivity and unified identity management across both environments. Which design approach best fulfills these requirements in a multi-cloud architecture?
- A
Implement a dedicated interconnect between OCI and the other cloud, federate identity across both cloud IAM solutions, and leverage secure replication for shared data.
- B
Use a generic IPsec VPN connection between clouds without a formal identity federation plan, relying on separate local accounts for each platform.
- C
Maintain distinct cloud environments by synchronizing databases manually and using a separate Single Sign-On (SSO) solution for each environment.
- D
Configure high-speed private network connections within a single region in OCI and build a parallel environment on the other cloud without sharing identity or data.
Show answer and explanation
Correct answer: A
Explanation
Oracle Cloud Infrastructure multi-cloud best practices recommend using a private, dedicated connection to ensure high performance and security between OCI and other clouds. Identity federation across both cloud IAM systems centralizes user management and access policies, reducing complexity and risk. Refer to OCI's 'Multi-Cloud Network Connectivity and Identity Guide' for recommended patterns and in-depth technical guidance.
- A. Correct.
Correct. A dedicated interconnect offers low latency and a stable, secure connection, while federating identity across both clouds ensures unified access control. Replicating data securely helps preserve consistency for machine learning and database workloads.
- B. Incorrect.
Incorrect. While IPsec VPN can connect environments, it may not provide the performance or reliability of a dedicated interconnect. Also, failure to establish a formal identity federation plan can lead to inconsistent user management and security gaps.
- C. Incorrect.
Incorrect. Keeping environments separate with manual database synchronization is error-prone and can introduce data inconsistencies. Running separate SSO solutions creates additional overhead and security complexity.
- D. Incorrect.
Incorrect. Building isolated networks and environments on each cloud without sharing identity or data undermines the core principle of multi-cloud integration and negates the benefits of cross-cloud collaboration.