Which use case is not supported by the external application feature?

Which use case is not supported by the external application feature?

• A. Adding a custom metric or column to the out-of-the-box fact.
• B. Creating a new user in Fusion Application.
• C. Modifying the data load frequency.
• D. Enabling SSO between Fusion and FDI.

Answer: (A)

This question tests the limits of customizing the data model through the external application feature. The integration works with predefined data structures (facts) from Fusion, and altering an out-of-the-box fact by adding your own metric or column would change the schema and data semantics. The external application layer isn’t designed to support on-the-fly schema extensions, so that use case isn’t supported. In contrast, provisioning a new user in Fusion, adjusting how often data loads run, and enabling SSO between Fusion and the external application are within typical integration capabilities, making them supported paths.

This question tests the limits of customizing the data model through the external application feature. The integration works with predefined data structures (facts) from Fusion, and altering an out-of-the-box fact by adding your own metric or column would change the schema and data semantics. The external application layer isn’t designed to support on-the-fly schema extensions, so that use case isn’t supported. In contrast, provisioning a new user in Fusion, adjusting how often data loads run, and enabling SSO between Fusion and the external application are within typical integration capabilities, making them supported paths.