1Z0-1151-25 Question 5
Single answerYour company has deployed critical workloads on both Oracle Cloud Infrastructure (OCI) and AWS. They want to simplify user administration and enable single sign-on (SSO) so that administrators only need to log in once to manage resources across both clouds. Which approach most effectively meets these requirements?
- A
Establish identity federation to a central identity provider (e.g., Oracle Identity Cloud Service or an external SAML provider) that can be used by both OCI and AWS.
- B
Create dedicated local IAM user accounts in each cloud and manually synchronize passwords whenever changes occur.
- C
Migrate all workloads from AWS to OCI to unify identity management in a single cloud.
- D
Use a non-supported identity provider that does not integrate with SAML or OIDC, but rely on manual account provisioning for concurrency.
Show answer and explanation
Correct answer: A
Explanation
A primary objective when adopting a multi-cloud strategy is to streamline access management across different providers. Oracle and AWS both support federating to an external or central identity provider that handles authentication, ensuring consistent user access and SSO. According to Oracle� best practices, identity federation using open standards (SAML, OIDC) is recommended to facilitate seamless logins and limit the complexity of managing multiple user repositories. Refer to the OCI documentation on identity federation (docs.oracle.com/en-us/iaas/Content/Identity/Concepts/federation.htm) and AWS documentation on IAM identity providers (docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers.html) for more details.
- A. Correct.
By federating to a common identity provider that supports open standards (SAML/OIDC), administrators can authenticate once and seamlessly access both OCI and AWS resources. This approach is considered a best practice to simplify multi-cloud identity management and reduce administrative overhead.
- B. Incorrect.
Maintaining separate local accounts in multiple clouds increases complexity, as passwords and permissions need to be kept in sync manually, creating a higher risk of errors and security gaps.
- C. Incorrect.
Migrating all workloads to a single cloud may reduce complexity, but it does not solve the stated need for multi-cloud flexibility. It also could be disruptive if workloads are already established on AWS and need to remain there.
- D. Incorrect.
Using an identity provider that does not support modern federation protocols (like SAML or OIDC) makes it impossible to configure true single sign-on across the clouds, forcing manual or proprietary solutions that are typically cumbersome and error-prone.