When merging an external application into FDI, what does exporting the semantic model template provide?

When merging an external application into FDI, what does exporting the semantic model template provide?

• A. It encrypts credentials.
• B. It creates a new data source.
• C. It includes a copy of FDI base semantic model.
• D. It triggers sandbox cleanup.

Answer: (C)

Exporting the semantic model template gives you a portable artifact that carries the definitions of how the external application's data is represented in FDI. It includes a copy of the FDI base semantic model, which is the standard set of entities, attributes, and relationships that define how FDI understands data. Having this base model included ensures the merged integration can reuse established semantics and has the foundational definitions available when imported elsewhere, keeping things consistent and compatible across environments. This export isn’t about encrypting credentials, creating a data source, or triggering sandbox cleanup; those are separate tasks in the integration lifecycle.

Exporting the semantic model template gives you a portable artifact that carries the definitions of how the external application's data is represented in FDI. It includes a copy of the FDI base semantic model, which is the standard set of entities, attributes, and relationships that define how FDI understands data. Having this base model included ensures the merged integration can reuse established semantics and has the foundational definitions available when imported elsewhere, keeping things consistent and compatible across environments. This export isn’t about encrypting credentials, creating a data source, or triggering sandbox cleanup; those are separate tasks in the integration lifecycle.