What can address your security requirements in FAW when FAW does not move and replicate your entire security implementation?

What can address your security requirements in FAW when FAW does not move and replicate your entire security implementation?

• A. Set up SSO between FAW and Fusion Applications and synchronize user and job roles.
• B. Create a custom data role and set up data filters that specify values for specific dimensions.
• C. Modify security configuration in Semantic Model Extensions.
• D. Implement a manual user provisioning process.

Answer: (A)

Centralize authentication and role mapping. When FAW doesn’t move or replicate your entire security system, using single sign-on with Fusion Applications lets users authenticate through your existing identity provider, while synchronizing user accounts and job roles ensures FAW enforces access exactly as defined in your enterprise security model. This keeps security consistent across systems without duplicating permissions inside FAW, and it automatically reflects changes in Fusion Applications (new users, role changes) without manual work. The other options would require recreating or maintaining security inside FAW itself, which undermines the goal of not moving your full security implementation. Creating custom data roles and filters, or modifying the Semantic Model Extensions, adds internal security logic that can diverge from the enterprise model. Manual user provisioning adds overhead and delays in reflecting changes, defeating the idea of a synchronized, centralized security posture.

Centralize authentication and role mapping. When FAW doesn’t move or replicate your entire security system, using single sign-on with Fusion Applications lets users authenticate through your existing identity provider, while synchronizing user accounts and job roles ensures FAW enforces access exactly as defined in your enterprise security model. This keeps security consistent across systems without duplicating permissions inside FAW, and it automatically reflects changes in Fusion Applications (new users, role changes) without manual work.

The other options would require recreating or maintaining security inside FAW itself, which undermines the goal of not moving your full security implementation. Creating custom data roles and filters, or modifying the Semantic Model Extensions, adds internal security logic that can diverge from the enterprise model. Manual user provisioning adds overhead and delays in reflecting changes, defeating the idea of a synchronized, centralized security posture.