1z0-588 Oracle Hyperion Data Relationship Management Essentials Questions and Answers

Provides faster performance

Easier to find a group of related properties when creating an Export

Prevents conflicts when a property definition in two target or source dimensions have the same name

The prefix can be used as criteria when creating a filter for a Query

DRM sorts property definitions alphabetically by default

Nothing changes in DRM, because the action script will fail to import due to formatting issues.

A hierarchy called "Product" will be created in the Reorganization version in DRM.

The top node in the hierarchy is All Products.

Products 100, 200, 300, and 400 are first created under the incorrect parent but are subsequently moved in the action script.

The two lines with the "Move" command will fail, because a value is missing from the last column for those lines.

Products 100-10, 100-20, 100-30, 200-10, 200-20, 200-40, 400-10, and 400-30 are some of the leaf nodes in the hierarchy.

Because most of the states are in the South, set the default value to South.

Turn on inheritance for the property.

Set up the property to derive the "South" value.

Set the property to Global.

Create a lookup property so that users can easily select "South" from a drop down menu.

Version

Property category

Hierarchy group

Node type

Hierarchy master

Use the Orphan List to identify and load discontinued products to the active product list when youneed the complete Product hierarchy.

Use the Inactivate feature to flag discontinued products and then use the Node Inactive propertyto filter products accordingly during exports.

Use the Delete feature to remove discontinued products from the Product Hierarchy.

Maintain the full product hierarchy with both active and discontinued products. Create a customproperty called "Product Status" that users can update to Active or Discontinued. Use this property to filter products accordingly during exports.

Use the Blend feature to blend inactive products; this allows inactive nodes to be loaded with active nodes when you need the complete Product hierarchy.

They are used to sort hierarchies in ascending order.

They are used to help maintain one-to-one or one-to-many mappings.

Associated nodes do not need to exist prior to import of the hierarchy.

They can reference nodes in different hierarchies.

They should be used with local node—level properties.

They pull in the node hierarchy and the node name.

They support bidirectional references.

1, 2 only

3, 5 only

1, 2, 3, 4 only

1, 3, 5 only

1, 2, 3, 4, 5