Is it necessary to create custom data roles to apply filters to the objects you want to secure?

Is it necessary to create custom data roles to apply filters to the objects you want to secure?

• A. It is mandatory to create custom data roles.
• B. It's optional; you can choose out-of-the-box or custom data roles.
• C. Filters are automatic and require no roles.
• D. You cannot apply filters to secure objects.

Answer: (B)

In this security model, data access is controlled by roles that carry data filters. You can rely on the out-of-the-box data roles that come with predefined filters for common scenarios, so you don’t have to create anything extra if those fit your needs. If a specific access requirement isn’t covered by the built-in roles, you can create a custom data role and attach the exact filters you need (or start from an existing role and modify its filters). That flexibility means creating custom data roles is optional, not mandatory. For example, if the standard Sales role already restricts data to a particular territory, you’re good to go; if you need a more specific or different restriction, you’d define a new custom role with those filters.

In this security model, data access is controlled by roles that carry data filters. You can rely on the out-of-the-box data roles that come with predefined filters for common scenarios, so you don’t have to create anything extra if those fit your needs. If a specific access requirement isn’t covered by the built-in roles, you can create a custom data role and attach the exact filters you need (or start from an existing role and modify its filters). That flexibility means creating custom data roles is optional, not mandatory. For example, if the standard Sales role already restricts data to a particular territory, you’re good to go; if you need a more specific or different restriction, you’d define a new custom role with those filters.