During Fusion Data Intelligence (FDI) instance creation, which step is critical to ensure a successful single sign-on (SSO) implementation?

• A. Sign in to OCI from the default domain of the Fusion Application tenancy you want to specify as the source and enable Single Sign-On on the Create Instance page.
• B. Install the Fusion Application in a new tenancy.
• C. Enable off-peak data load scheduling.
• D. Assign the Functional Administrator role to the user.

Answer: (A)

Enabling SSO during Fusion Data Intelligence instance creation hinges on authenticating to OCI from the Fusion Application tenancy’s default domain and turning on Single Sign-On on the Create Instance page. This ensures you are configuring SSO within the correct tenancy context, and it triggers the setup that creates the necessary identity provider metadata and trust between OCI and the Fusion instance for that source tenancy. Without signing in from the proper domain and enabling SSO at creation, the SSO configuration won’t be established for the new instance, so users wouldn’t be able to sign in via the configured identity provider. The other steps don’t drive the SSO integration: installing Fusion in a new tenancy is just deployment, off-peak data load scheduling is about timing data processes, and assigning a Functional Administrator role affects permissions but not the actual SSO setup.