In FAW, when the out-of-the-box security model does not meet your needs, what is the recommended approach?

• A. There is no way to customize; adopt the available model.
• B. Use the security customization in FAW for both data security and object security to meet your requirements.
• C. Change database-level permissions only.
• D. Security customization is only in enterprise edition.

Answer: (B)

When you need more than the out-of-the-box security model, use FAW’s built-in security customization to tailor access. This approach lets you control both data security and object security within FAW itself. Data security handles who can see which rows of data (row-level access), while object security determines who can view or interact with FAW objects like dashboards, reports, datasets, and folders. By defining roles and policies that map to your organization’s requirements, you can enforce precise access controls without changing underlying database permissions.

This method is preferred because it keeps security management centralized, auditable, and aligned with FAW’s governance model, and it avoids the risks and maintenance headaches of altering database-level permissions. It also ensures your security customizations scale with changes in roles and datasets, and remain consistent across updates and different FAW components.