Oracle 1z0-1086-22 Oracle Enterprise Data Management Cloud 2022 Implementation Professional Exam Practice Test

“You can reuse viewpoints across views by pointing to an existing viewpoint when you create a new viewpoint.” This way, you can access the entity information in another view without duplicating data objects. 

When you want to map two general ledger systems, GL1 and GL2, to a single EPM Planning application, and it is time to synchronize changes by exporting the plan account mappings, the following statement about mapping keys is true: you need two mapping keys, one for GL1-to-Planning and one for GL2-to-Planning. When you export a mapping, you select the location with its associated mapping key. Mapping keys are used to specify the source node types mapped to target node types and to define a location name to export the mapping data. You need to define one mapping key for each source node type mapped to a target node type. For example, if you map two source applications to one target application, you need to define two mapping keys defining the mapping relationship from each source node type to the target node type. Each mapping key is identified by a unique location name that you enter. The location name is used to export the mapping data and by the consuming or external application to import the mapping data. You do not need only one mapping key and location to export the plan account mappings, because this would not specify the correct source-to-target relationships. You do not need to create shadow mapping keys in the target application or one location per mapping key, because these are not supported by Oracle Enterprise Data Management Cloud. References: Defining Mapping Keys - Oracle Help Center1; Exporting Mapping Data - Oracle Help Center2

Templates enable you to store application or dimension configurations in an offline file for use in other Oracle Enterprise Data Management Cloud environments. Use templates to transfer applications or dimensions and their metadata objects across environments (for example, from a test environment to a production environment) or to get a quick start in new implementations. Templates contain metadata only and do not include any data, requests, or transaction history. References: Working with Templates - Oracle Help Center1

• E. Creating views and viewpoints to configure custom validations to enforce business rules on your data: This option is not correct because creating views and viewpoints is not a task that involves configuring custom validations. Custom validations are configured at the node type level by defining validation rules and expressions that enforce business rules on your data.

“Inheritance can be overridden at lower levels; descendants from the overriding position inherit the override value.” and “Different values can be inherited for shared nodes under multiple parents.” The other statements are false. Nodes in lists cannot inherit property values from their ancestors, because lists do not have parent-child relationships. Values are not inherited from the top node, but from the nearest ancestor with a value.

• B. You need the Data Manager or Owner permission to the application to export its dimensions and mappings: This option is correct because the Data Manager or Owner permission is required to export enterprise data from an application to an external application or a file.
• C. For Planning and Universal applications, you can export enterprise data using either a connection or a comma-delimited file: This option is correct because Planning and Universal applications support both methods of exporting enterprise data.

• 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.

 All items in the request are validated using your data access except the enriched item, which is validated during the approval phase using the enricher’s data access: This option is correct because when a request is pushed back to the submitter, the enriched item is preserved and validated using the enricher’s data access during the approval phase. The rest of the items are validated using the submitter’s data access when the request is submitted again.

References:

• https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/edmra/approving-and-enriching-requests.html

• This option is correct because when you define an approval policy at the dimension level, it applies to all the node types and hierarchy sets that belong to the dimension. You can also define approval policies at the node type or hierarchy set level to override the dimension level policy.