You would like to avoid creating Fusion Applications users and their assigned job roles in FAW. What options are available in FAW for synchronizing users and job roles between FAW and Fusion Applications?

You would like to avoid creating Fusion Applications users and their assigned job roles in FAW. What options are available in FAW for synchronizing users and job roles between FAW and Fusion Applications?

• A. Implement SSO and synchronization of users and job roles between FAW and Fusion Applications, before provisioning the FAW instance.
• B. Create FAW users manually after provisioning.
• C. Use manual provisioning only.
• D. Disable synchronization.

Answer: (A)

Synchronizing identities and their assigned job roles between FAW and Fusion Applications through SSO and automated provisioning is the way to go if you want to avoid manually creating FAW users. By setting up federated authentication (SSO) and a user/role synchronization mechanism before you provision the FAW instance, FAW can pull in the existing user accounts and their job-role mappings from Fusion Applications as part of the provisioning process. This means once FAW is up, it already has the correct users and access rights, reducing manual steps and keeping access control consistent across systems. Relying on manual provisioning after provisioning would require you to recreate users and assign roles by hand, which is error-prone and defeats the goal of seamless integration. Disabling synchronization eliminates the automatic import of users and roles, also not aligned with the objective. So the best approach is to configure SSO and synchronization upfront to ensure FAW and Fusion Applications stay in sync from the start.

Synchronizing identities and their assigned job roles between FAW and Fusion Applications through SSO and automated provisioning is the way to go if you want to avoid manually creating FAW users. By setting up federated authentication (SSO) and a user/role synchronization mechanism before you provision the FAW instance, FAW can pull in the existing user accounts and their job-role mappings from Fusion Applications as part of the provisioning process. This means once FAW is up, it already has the correct users and access rights, reducing manual steps and keeping access control consistent across systems.

Relying on manual provisioning after provisioning would require you to recreate users and assign roles by hand, which is error-prone and defeats the goal of seamless integration. Disabling synchronization eliminates the automatic import of users and roles, also not aligned with the objective. So the best approach is to configure SSO and synchronization upfront to ensure FAW and Fusion Applications stay in sync from the start.