Which statement best describes the purpose of custom data security in FDI?

Which statement best describes the purpose of custom data security in FDI?

• A. It cannot be combined with out-of-the-box security.
• B. It enables complex, user-specific data access using custom data roles and filters.
• C. It replaces all existing security configurations.
• D. It only affects non-sensitive data.

Answer: (B)

Custom data security in FDI focuses on controlling what each user can see by applying targeted access rules. It lets you define custom data roles and filters to express complex, user-specific data visibility—for example, restricting a user to a particular region, department, or data set while allowing broader access for others. This approach works alongside existing security configurations, adding fine-grained, row- and column-level control rather than replacing what’s already in place. It applies to sensitive data as well, ensuring governance across the board. That’s why the best description is that it enables complex, user-specific data access using custom data roles and filters. The other statements don’t fit because custom data security is designed to complement—not block or replace—out-of-the-box security, it doesn’t eliminate existing configurations, and it isn’t limited to non-sensitive data.

Custom data security in FDI focuses on controlling what each user can see by applying targeted access rules. It lets you define custom data roles and filters to express complex, user-specific data visibility—for example, restricting a user to a particular region, department, or data set while allowing broader access for others. This approach works alongside existing security configurations, adding fine-grained, row- and column-level control rather than replacing what’s already in place. It applies to sensitive data as well, ensuring governance across the board. That’s why the best description is that it enables complex, user-specific data access using custom data roles and filters. The other statements don’t fit because custom data security is designed to complement—not block or replace—out-of-the-box security, it doesn’t eliminate existing configurations, and it isn’t limited to non-sensitive data.