A Department Manager requires access to all accounts in their own department, but only a certain account in all other departments. With the usual…

Cell-level security is the appropriate mechanism for this scenario because it allows for defining access rights at the intersection of dimension members. It can grant or deny read/write access to specific data cells or slices of data. This provides the necessary granularity to create a rule granting the manager access to all accounts within their specific department, while simultaneously creating another rule that restricts their access to only a single, specific account across all other departments. Standard dimension (member) security is insufficient as it applies to the entire member, not specific intersections.

A. Member security: This grants access to an entire dimension member (e.g., an account or a department), which is too broad for the specified requirement of mixed access across different intersections. B. Artifact security: This controls access to application components like forms, dashboards, and business rules, not the underlying data within the cube's cells. D. Access control: This is a general, high-level term for security. Cell-level security is a specific type of access control feature within Oracle Planning that solves this problem.

1. Oracle Cloud, Administering Planning, EPM-SA, "Securing Data" chapter, "About Cell-Level Security" section.

"Cell-level security enables you to define security on a cell or a slice of data in a database. A cell is an intersection of a member from each dimension. You can use cell-level security to further refine access to data that is not available with dimension security." This directly supports the use of cell-level security for intersection-based access.

2. Oracle Cloud, Administering Planning, EPM-SA, "Securing Data" chapter, "About Dimension Security" section.

"Dimension security defines access to members of a dimension. When you assign access rights to a dimension, you also assign access rights to all of its members." This explains why member security (Option A) is too broad for the scenario.

3. Oracle Cloud, Administering Planning, EPM-SA, "Securing Artifacts" chapter.

"You can assign access permissions to artifacts such as forms, rules, and dashboards." This confirms that artifact security (Option B) is for application objects, not data cells.