1Z0-1080-25 practice question 24 of 25

Which two statements are true about using anchor and nonanchor dimensions with cell-level security?

Full set: 120 questions
Answer options
A:

A. Anchor dimensions are always required in the cube that is used in the cell-level security definition.

B:

B. Anchor dimensions are never required in the cube that is used in the cell-level security definition.

C:

C. By default, nonanchor dimensions are not required.

D:

D. By default, nonanchor dimensions are required. You can change this setting later.

Correct Answer:
<P>A; C</P>
Explanation

In Oracle Essbase cell-level security, a filter is defined by selecting members from specific dimensions, which are called anchor dimensions. It is mandatory to use at least one anchor dimension to define the scope of the security rule. Dimensions not used in the filter definition are nonanchor dimensions. By default, Essbase grants access to all members of nonanchor dimensions, meaning you are not required to explicitly define access for them. This simplifies filter creation by assuming permissive access for unspecified dimensions, which can be changed to be more restrictive if needed.

Why Incorrect

B. Anchor dimensions are essential; without them, a security filter has no defined scope and cannot be created. D. The default setting for nonanchor dimensions is permissive (not required); they can be made required, but this is not the default behavior.

References

1. Oracle Essbase 21c Documentation, Administering Oracle Essbase, Chapter 10: Essbase Security, Section: "Creating and Managing Filters".

This section states, "The dimensions from which you select members are called anchor dimensions. The dimensions from which you do not select members are called non-anchor dimensions." It further explains the process of creating a filter, which requires selecting members, thus establishing anchor dimensions. This supports option A.

2. Oracle Essbase 21c Documentation, Administering Oracle Essbase, Chapter 10: Essbase Security, Section: "Creating and Managing Filters", Subsection: "About Anchor and Non-Anchor Dimensions".

This part of the documentation explicitly clarifies the default behavior: "By default, users have access to all members of non-anchor dimensions." This directly supports option C and refutes option D. It also mentions the "Require in non-anchor dimensions" option, confirming that the default is "not required."

3. Oracle Essbase Cloud Service Documentation, Administering Oracle Essbase Cloud, Chapter 8: Managing Essbase Security and User Access, Section: "About Filters".

This documentation for the cloud version confirms the same principle: "For dimensions not included in the filter definition (non-anchored dimensions), access is granted to all members by default." This reinforces the correctness of option C.

Scroll to Top