Which statement best describes security customization in FAW?

Which statement best describes security customization in FAW?

• A. It allows customization to meet specific requirements by combining data security and object security.
• B. It does not affect object security.
• C. It requires external tools outside FAW.
• D. It is not supported.

Answer: (A)

Security customization in FAW enables tailoring who can see what by using both data security and object security. Data security controls access to the actual data itself—things like row-level or column-level restrictions, masking, and policy-based access. Object security controls who can access and interact with FAW content—reports, dashboards, folders, and data models. When you combine these two layers, you can meet specific requirements: a user can see only the data they’re allowed to and only the FAW objects they’re permitted to use. This built-in capability doesn’t require external tools and is supported in FAW. For example, a regional analyst might access only their regional data and the dashboards assigned to their region, while a global user can access everything.

Security customization in FAW enables tailoring who can see what by using both data security and object security. Data security controls access to the actual data itself—things like row-level or column-level restrictions, masking, and policy-based access. Object security controls who can access and interact with FAW content—reports, dashboards, folders, and data models. When you combine these two layers, you can meet specific requirements: a user can see only the data they’re allowed to and only the FAW objects they’re permitted to use. This built-in capability doesn’t require external tools and is supported in FAW. For example, a regional analyst might access only their regional data and the dashboards assigned to their region, while a global user can access everything.