You activate FDI in the cloud account containing a Fusion Application.Which step is critical to follow during FDI instance creation to ensure a successful Single Sign-On implementation?

• A. Turn off SSO during creation, then enable later.
• B. Create the instance in a separate domain.
• C. Use a third-party SSO provider only.
• D. Sign in to OCI from the default domain of the Fusion Application tenancy you want to specify as the source while creating your FDI instance. Also, select the "Enable Single Sign-On" option on the Create Instance page.

Answer: (D)

The essential idea is that Single Sign-On for an FDI instance must be established within the correct identity domain context and wired into the provisioning process. Sign in to OCI using the default domain of the Fusion Application tenancy you want to designate as the source ensures the FDI instance is created with the proper domain relationship and trust settings. Then selecting Enable Single Sign-On on the Create Instance page configures the SSO integration at provisioning time, so the FDI instance is prepared to participate in the SSO flow with the Fusion Application’s identity provider. If you skip this or sign in from another domain, the instance won’t be bound to the correct identity domain and SSO metadata won’t be properly set up, leading to login and token issues. The other options don’t align with the need to anchor the FDI instance to the correct domain and to enable SSO during creation for a functional SSO setup.