What is the difference between the security page available from the FDI admin console and the security configurations tab available in semantic model extensions?

What is the difference between the security page available from the FDI admin console and the security configurations tab available in semantic model extensions?

• A. The admin console security page provides custom security.
• B. The admin console security page provides out-of-the-box security, while the semantic model extensions enable custom security.
• C. Both pages provide identical security options.
• D. Custom security is not possible in FDI.

Answer: (B)

The key idea is that there are two security surfaces with different purposes. The security page in the admin console provides the built-in, out-of-the-box security that ships with FDI—ready-to-use roles and permissions with minimal setup. The security configurations tab in semantic model extensions is a development surface that lets you implement custom security policies tailored to your specific data model, going beyond the defaults. So the admin console offers baseline security, while semantic model extensions enable you to define custom security rules for your models. The other options don’t fit because the admin page isn’t about custom security by itself, the two pages don’t offer identical options, and custom security is indeed possible through semantic model extensions.

The key idea is that there are two security surfaces with different purposes. The security page in the admin console provides the built-in, out-of-the-box security that ships with FDI—ready-to-use roles and permissions with minimal setup. The security configurations tab in semantic model extensions is a development surface that lets you implement custom security policies tailored to your specific data model, going beyond the defaults. So the admin console offers baseline security, while semantic model extensions enable you to define custom security rules for your models. The other options don’t fit because the admin page isn’t about custom security by itself, the two pages don’t offer identical options, and custom security is indeed possible through semantic model extensions.