Which statement best describes the recommended SSO implementation scenario for FAW?

Which statement best describes the recommended SSO implementation scenario for FAW?

• A. Activating FAW in the same cloud account as Fusion Application
• B. Activating FAW in a different cloud account from Fusion Application
• C. Implementing SSO requires separate accounts for each service
• D. SSO implementation is optional and unnecessary

Answer: (A)

The main idea here is that SSO works best when FAW and the Fusion Application share the same cloud account. When both services live under the same tenancy, you can configure a single trust relationship with your identity provider, use the same user directory, and apply consistent access policies across both systems. This makes provisioning, de-provisioning, and role mapping straightforward and reduces the complexity of cross-account authorization. Users benefit from a seamless experience: sign in once and gain access to both FAW and Fusion Application without extra sign-ins or complex redirects. It also minimizes latency and potential points of failure that can arise from trusting and syncing identities across separate cloud accounts. Putting FAW in a different cloud account would require configuring cross-account SSO, managing additional trust relationships, and handling more intricate access policies, which increases setup effort and the chance of misconfigurations. And SSO isn’t something you’d typically treat as optional in this integrated scenario, nor is there a need to insist on separate accounts for each service when they can share one.

The main idea here is that SSO works best when FAW and the Fusion Application share the same cloud account. When both services live under the same tenancy, you can configure a single trust relationship with your identity provider, use the same user directory, and apply consistent access policies across both systems. This makes provisioning, de-provisioning, and role mapping straightforward and reduces the complexity of cross-account authorization.

Users benefit from a seamless experience: sign in once and gain access to both FAW and Fusion Application without extra sign-ins or complex redirects. It also minimizes latency and potential points of failure that can arise from trusting and syncing identities across separate cloud accounts.

Putting FAW in a different cloud account would require configuring cross-account SSO, managing additional trust relationships, and handling more intricate access policies, which increases setup effort and the chance of misconfigurations. And SSO isn’t something you’d typically treat as optional in this integrated scenario, nor is there a need to insist on separate accounts for each service when they can share one.