How can you modify security for subject areas in FDI?

How can you modify security for subject areas in FDI?

• A. You should disable security to expose data.
• B. Oracle secures FDI subject areas by using application duty roles. The security for subject areas can be modified using security configurations in Semantic Model Extension.
• C. You must modify the underlying database permissions.
• D. Security is fixed and cannot be changed.

Answer: (B)

In FDI, security for subject areas is managed at the application level using duty roles. To modify who can access and what they can see, you use the Security Configurations in the Semantic Model Extension. This is where you map application roles to access rights on subject areas, measures, and related objects, shaping what end users can view without touching the underlying database permissions. Disabling security would expose sensitive data and violate governance policies, so that’s not a viable approach. Likewise, changing underlying database permissions isn’t how FDI controls access at the semantic layer—the subject area security lives in the semantic model, not in the database layer. Security isn’t fixed; you can adjust it through the Security Configurations in the Semantic Model Extension to align with evolving roles and data access needs.

In FDI, security for subject areas is managed at the application level using duty roles. To modify who can access and what they can see, you use the Security Configurations in the Semantic Model Extension. This is where you map application roles to access rights on subject areas, measures, and related objects, shaping what end users can view without touching the underlying database permissions.

Disabling security would expose sensitive data and violate governance policies, so that’s not a viable approach. Likewise, changing underlying database permissions isn’t how FDI controls access at the semantic layer—the subject area security lives in the semantic model, not in the database layer. Security isn’t fixed; you can adjust it through the Security Configurations in the Semantic Model Extension to align with evolving roles and data access needs.