You are developing a multidimensional project that includes a dimension named
Organization. The dimension is based on the DimOrganization table in the data warehouse.
The following diagram illustrates the table design.
The Organization dimension includes a parent-child hierarchy named Organizations. The
dimension includes the following dimension attributes:
Organization, which is a key attribute
Organizations, which defines the parent-child hierarchy
Currency Code, which is a regular attribute
PercentageOfOwnership, which is a regular attribute
When users browse the dimension, four hierarchies are visible to them.
You need to ensure that the Organization and PercentageOfOwnership hierarchies are not
visible to users.
What should you do?
A.
Set the AttributeHierarchyVisible property to False for the Organization and
PercentageOfOwnership attributes.
B.
Set the AttributeHierarchyEnabled property to False for the Organization and
PercentageOfOwnership attributes.
C.
Delete the Organization and the PercentageOfOwnership attributes.
D.
Set the AttributHierarchyDisplayFolder property to Null for the Organization and
PercentageOfOwnership attributes.
http://www.200-120exam.com/wp-content/uploads/2015/02/clip_image0188.jpg
The correct answer is A.
You cannot set AttributeHierarchyEnabled property to False for the Organization (key attribute)
cause it is invalidates attribute relationships.
I agree.
Agree we are just hiding the hierarchy from the end user, not disabling the functionality behind the scenes
C also fit?
You cannot delete a key column. C is out.
Whats the answer?
A.
Set the AttributeHierarchyVisible property to False for the Organization and
PercentageOfOwnership attributes.
lingo mambo.
option A hides the hierarchy which does the job. But option B also disables the hierarchy. as there is no mention of use for this hierarchy in the text this could indeed be the better option. It’s also just a regular attribute so nothing is troubled by disabling it. )if it’s a key it’d be different.
So A or B
It’s A
The value of the AttributeHierarchyEnabled property determines whether an attribute hierarchy is created. If this property is set to False, the attribute hierarchy is not created and the attribute cannot be used as a level in a user hierarchy; the attribute hierarchy exists as a member property only. However, a disabled attribute hierarchy can still be used to order the members of another attribute. If the value of the AttributeHierarchyEnabled property is set to True, the value of the AttributeHierarchyVisible property determines whether the attribute hierarchy is visible independent of its use in a user-defined hierarchy.
https://docs.microsoft.com/en-us/sql/analysis-services/lesson-4-4-hiding-and-disabling-attribute-hierarchies