Which statement is FALSE about unbound dimensions?
Unbound dimensions are created outside of the application registration process and do not get imported or exported. You can use unbound dimensions to manage complex data sets such as related value sets, account combinations, and multi-dimensional mappings in Oracle Enterprise Data Management Cloud. You can extract data from unbound dimensions using extracts and load data into unbound dimension viewpoints by using request load files. You cannot use unbound dimensions for importing and exporting data, because they are not bound to any external applications. Reference: Working with Unbound Dimensions - Oracle Help Center
A request was submitted that triggered an approval policy. However, there are not enough approvers available to satisfy the terms of the policy.
What are two resolutions?
1. The request is escalated to a data manager, who grants an exceptional approval and commits the request: This option is correct because when there are not enough approvers available to satisfy the terms of the approval policy, the request is escalated to a data manager after exceeding the defined number of approval notifications. The data manager can then grant an exceptional approval and commit the request.
2. The request is escalated to an application owner, who changes the approval policy to require fewer approvers, at which point the request is committed: This option is correct because when there are not enough approvers available to satisfy the terms of the approval policy, the request is escalated to an application owner after exceeding the defined number of approval notifications. The application owner can then change the approval policy to require fewer approvers, and then approve and commit the request.
https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/edmra/approving-and-enriching-requests.html
You need to map accounts from a GL application to a Planning application. You have already registered the source and target applications, and imported the source and target Account dimensions. In the Planning Account dimension, you create a map binding called Account Mapping.
Which three objects are created in the Planning application?
When you create a map binding in a dimension, you are creating a mapping relationship between a source node type and a target node type within that dimension. This enables you to transform properties or derive values from source nodes to target nodes when sharing data across applications. When you create a map binding called Account Mapping in the Planning Account dimension, three objects are created in the Planning application: an Account Mapping hierarchy set that contains hierarchies for mapping accounts from GL to Planning; an Account Mapping node set that contains nodes for mapping accounts from GL to Planning; and a node type converter with the Account (GL) node type as source and Account Mapping (Planning) node type as target that defines how properties are transformed or derived from source nodes to target nodes. A map binding does not create a new dimension or a viewpoint in a view. Reference: Working with Map Bindings - Oracle Help Center; Working with Node Type Converters - Oracle Help Center
At the end of the registration process, each dimension generates a data chain, which is a group of data objects within the information model.
Which statement is FALSE regarding the data chain object?
This option is false because a hierarchy does not use all the data chain objects, but only a node type and a hierarchy set. A node type defines the nodes and properties that are used in the hierarchy, and a hierarchy set defines the relationships between the nodes.
https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/edmra/understanding-data-chains.html
