To create custom data security beyond out-of-the-box security, which FDI settings provide this functionality?

To create custom data security beyond out-of-the-box security, which FDI settings provide this functionality?

• A. A combination of steps in the security console and security configurations in the semantic model extensions available in the FDI console.
• B. Only the security page in the FDI admin console.
• C. The semantic model extensions security tab alone.
• D. Custom data security is not supported in FDI.

Answer: (A)

Custom data security beyond what comes out of the box comes from using two coordinated areas in FDI: the security console and the semantic model extensions within the FDI console. The security console handles who can access the FDI environment—authentication, roles, and general access control. The semantic model extensions security tab lets you attach security policies directly to the semantic model elements (such as subject areas, attributes, and data elements), enabling granular control like row-level or column-level restrictions and data masking rules that apply when data is retrieved through mappings. By configuring both layers together, you enforce access rules at the system level and at the data-model level, achieving deeper, tailored security beyond default settings. The other options don’t provide that complete, layered approach: focusing only on a single page or tab misses the necessary combination of environment-wide security and semantic-model-specific policies, and saying custom data security isn’t supported is inaccurate.

Custom data security beyond what comes out of the box comes from using two coordinated areas in FDI: the security console and the semantic model extensions within the FDI console. The security console handles who can access the FDI environment—authentication, roles, and general access control. The semantic model extensions security tab lets you attach security policies directly to the semantic model elements (such as subject areas, attributes, and data elements), enabling granular control like row-level or column-level restrictions and data masking rules that apply when data is retrieved through mappings.

By configuring both layers together, you enforce access rules at the system level and at the data-model level, achieving deeper, tailored security beyond default settings. The other options don’t provide that complete, layered approach: focusing only on a single page or tab misses the necessary combination of environment-wide security and semantic-model-specific policies, and saying custom data security isn’t supported is inaccurate.