合格保証付きクイズ2023年最新の実際に出る検証済みの1z0-1086-22無料試験問題集
無料Enterprise Data Management 1z0-1086-22究極な学習ガイド（更新されたのは60問があります)
試験を受験するには、Oracle Cloud InfrastructureやOracle Databaseなどの関連分野で有効なOracle認定資格を持っていることを含め、特定の前提条件を満たす必要があります。さらに、候補者は、Oracle Enterprise Data Management Cloud 2022での実践的な経験を持ち、その機能や能力に精通している必要があります。
質問 # 16
Consider a hierarchy: A parent node, "Core Products", has a child node "100", which has children "101" and "102". In the same hierarchy, you insert "100" under another parent, "New Products".
What happens?
- A. Node "100" and its children are inserted as shared nodes under "New Products".
- B. Node "100" is inserted as a unique node under "New Products", with a qualifier to indicate that it's a separate node from the original.
- C. Only node "100" is inserted as a shared node under "New Products".
- D. Node "100" cannot be inserted under another parent in the same hierarchy.
正解：A
解説：
According to the Oracle Help Center1, shared nodes are nodes that exist under different parents within a hierarchy set or viewpoint. When you insert a node that has children under another parent in the same hierarchy, the node and its children are inserted as shared nodes.
質問 # 17
You want to enforce the "four-eyes" principle for your approval policy. How can you do this?
- A. Use a serial approval method.
- B. Use any approval method with at least three different approval groups.
- C. Use any approval method and do not select "Include Submitter".
- D. Use a parallel approval method.
正解：C
解説：
Explanation
* C. Use any approval method and do not select "Include Submitter": This option ensures that the
* submitter of the request cannot also be an approver of the request, which enforces the "four-eyes" principle that requires at least two different people to review and approve a request.
* A. Use a serial approval method: This option does not guarantee that the submitter is not also an approver, unless the "Include Submitter" option is deselected.
* B. Use any approval method with at least three different approval groups: This option does not guarantee that the submitter is not also an approver, unless the "Include Submitter" option is deselected.
* D. Use a parallel approval method: This option does not guarantee that the submitter is not also an approver, unless the "Include Submitter" option is deselected.
References:
* https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/edmra/creating-approval-policies
質問 # 18
Which two things occur during application registration7
- A. You load dimension data from flat files.
- B. You select an Enterprise Data Management Cloud application type.
- C. The system generates default data objects based on your selections in the registration wizard.
- D. The system imports external application data to determine the application configuration.
- E. The system generates connections to external applications.
正解：B、C
質問 # 19
You want to map two general ledger systems, GL1 and GL2, to a single EPM Planning application. It is time to synchronize changes by exporting the plan account mappings. Which statement about mapping keys is true?
- A. You create shadow mapping keys in the target application to represent the values coming from GL1 and GL2, respectively.
- B. You create one location per mapping key, where a mapping key is a unique source-target combination.
- C. You need only one mapping key and location to export the plan account mappings.
- D. You need two mapping keys, one for GLl-to-Planning and one for GL2-to-Planning. When you export a mapping, you select the location with its associated mapping key.
正解：D
解説：
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. Reference: Defining Mapping Keys - Oracle Help Center1; Exporting Mapping Data - Oracle Help Center2
質問 # 20
Which two statements are true about Inherited properties7
- A. Different values can be inherited for shared nodes under multiple parents.
- B. Values are inherited from the top node.
- C. Nodes in lists can inherit property values from their ancestors.
- D. Inheritance can be overridden at lower levels; descendants from the overriding position inherit the override value.
正解：B、D
解説：
Explanation
Inherited properties are properties that are inherited from ancestor nodes in a hierarchy. The following statements are true about inherited properties: inheritance can be overridden at lower levels; descendants from the overriding position inherit the override value; different values can be inherited for shared nodes under multiple parents; values are inherited from the top node. The following statement is false about inherited properties: nodes in lists can inherit property values from their ancestors. Nodes in lists cannot inherit property values from their ancestors, because lists do not have parent-child relationships or hierarchies. References:
Working with Properties - Oracle Help Center
質問 # 21
Which three are use case examples of node type validations?
- A. Hierarchy levels must match specific node types.
- B. Start date must occur before end date.
- C. Rollup nodes must have enabled base nodes below them.
- D. Node type names must conform to naming conventions.
- E. Property values must be in a certain format.
正解：B、C、E
解説：
Explanation
Node type validations are validations that check whether nodes meet certain criteria based on their actions or properties. Node type validations can be used for various use case examplessuch as: start date must occur before end date, property values must be in a certain format, rollup nodes must have enabled base nodes below them, etc. Node type validations cannot be used to check hierarchy levels or node type names, because these are not related to node actions or properties. Hierarchy levels are defined by hierarchy sets and node type names are defined by node types. References: Working with Node Type Validations - Oracle Help Center
質問 # 22
Which statement is true about permissions?
- A. Permissions assigned to a dimension do not also apply to the hierarchy sets and node types that they contain.
- B. The Owner permission on a view enables a user to configure the view and grants full access to the data objects in that view.
- C. By default, when you assign the Participant permission to a user or group, their data access is set to Write.
- D. When you grant a permission at a higher level, such as Owner, it includes all of the permissions at lower levels, such as Participant.
正解：D
解説：
Explanation
Permissions secure access to applications, dimensions, data chain objects, and data. There are four levels of permissions: Owner, Data Manager, Participant (Write), and Participant (Read). When you grant a permission at a higher level, such as Owner, it includes all of the permissions at lower levels. For example, if you grant a user Owner permission on an application, they also have Data Manager and Participant permissions on that application. Permissions assigned to a dimension also apply to the hierarchy sets and node types that they contain. By default, when you assign the Participant permission to a user or group, their data access is set to Read. References: Working with Permissions - Oracle Help Center
質問 # 23
For which application type can you NOT export mappings?
- A. Financial Consolidation and Close
- B. Oracle E-Business Suite General Ledger
- C. Universal
- D. Financials Cloud General Ledger
- E. Planning
正解：A
解説：
This option is correct because Financial Consolidation and Close applications do not support exporting mappings to external applications or files.
Reference:
https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/edmra/exporting-enterprise-data.html
質問 # 24
In what order do you archive data chain objects?
- A. Viewpoint, dimension, application
- B. You can archive data chain objects in any order
- C. Viewpoint, node set, hierarchy set, node type
- D. Application, dimension, viewpoint
- E. Node type, hierarchy set, node set, viewpoint
正解：E
解説：
When you archive data chain objects, you need to follow a specific order based on their dependencies. The order that you archive data chain objects is: node type, hierarchy set, node set, viewpoint. You need to archive node types first, because they are independent of other data chain objects. Then you need to archive hierarchy sets that use those node types. Then you need to archive node sets that use those hierarchy sets or node types. Then you need to archive viewpoints that use those node sets or hierarchy sets. You cannot archive data chain objects in any other order or in any order, because this would cause errors or inconsistencies in your data chain. You cannot archive applications or dimensions directly, because they are not data chain objects. Reference: Archiving and Unarchiving Data Chain Objects - Oracle Help Center
質問 # 25
What conditions should be met to enable a custom validation?
- A. A valid expression and a failure message are defined, at least one trigger action and/or a trigger property is configured.
- B. An expression that returns a Boolean value and a failure message are defined.
- C. A trigger property and a trigger action for a node set or hierarchy set is configured.
- D. A derived property of the Custom Validation node type that returns a Boolean value is defined.
正解：A
解説：
A custom validation is a validation that checks whether nodes meet certain criteria based on their actions or properties using an expression that returns a Boolean value. To enable a custom validation, you need to meet the following conditions: define a valid expression and a failure message for the custom validation; configure at least one trigger action and/or a trigger property for a node set or hierarchy set that uses the custom validation. You do not need to define a derived property of the Custom Validation node type or an expression that returns a Boolean value and a failure message, because these are not supported by Oracle Enterprise Data Management Cloud. Reference: Working with Custom Validations - Oracle Help Center
質問 # 26
You want to enforce the "four-eyes" principle for your approval policy. How can you do this?
- A. Use a serial approval method.
- B. Use any approval method with at least three different approval groups.
- C. Use any approval method and do not select "Include Submitter".
- D. Use a parallel approval method.
正解：C
解説：
1. Use any approval method and do not select "Include Submitter": This option ensures that the submitter of the request cannot also be an approver of the request, which enforces the "four-eyes" principle that requires at least two different people to review and approve a request.
2. Use a serial approval method: This option does not guarantee that the submitter is not also an approver, unless the "Include Submitter" option is deselected.
3. Use any approval method with at least three different approval groups: This option does not guarantee that the submitter is not also an approver, unless the "Include Submitter" option is deselected.
4. Use a parallel approval method: This option does not guarantee that the submitter is not also an approver, unless the "Include Submitter" option is deselected.
Reference:
https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/edmra/creating-approval-policies.html
質問 # 27
Which three tasks can you automate with EPM Automate?
- A. Create and auto-submit change requests
- B. Import and export dimensions
- C. Archive backups
- D. Recreate service
- E. Export and import snapshots
正解：B、C、E
解説：
Explanation
EPM Automate enables users to remotely perform tasks within Oracle Enterprise Performance Management Cloud environments. Some of the tasks that can be automated are: archive backups, import and export metadata, data, artifact and application snapshots, templates, and Data Management mappings; upload and download files; run business rules; copy data; and export and import snapshots. References: About EPM Automate - Oracle Help Center1
質問 # 28
You need nodes added to your General Ledger application's account dimension to be shared to your Planning application's account dimension.
Which two steps can you take to facilitate this?
- A. Create a node type converter for the Account node type in the General Ledger application that uses the Planning Account node type as a source.
- B. Create a node type converter for the Account node type in the Planning application that uses the General Ledger Account node type as a source.
- C. Create a maintenance view with viewpoints for both the General Ledger account dimension and the Planning account dimension.
- D. Link the account dimension in the General Ledger application to the account dimension in the Planning application.
正解：C、D
解説：
These are two steps that can facilitate sharing nodes between applications. The other options are not valid. You do not need to create node type converters for this scenario, because both applications use the same node type for accounts.
質問 # 29
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?
- A. Views are a collection of node sets and hierarchy sets.
- B. Node types manage nodes and properties.
- C. Node sets define the group of nodes available in viewpoints.
- D. A hierarchy uses all the data chain objects.
- E. You can define your own hierarchy sets when you want to create alternate hierarchies using different relationships between the same or different node types.
- F. A viewpoint is the interface you use to display and edit information, and work with data.
正解：D
解説：
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.
Reference:
https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/edmra/understanding-data-chains.html
質問 # 30
Which two statements are true about requests?
- A. You cannot make multiple changes to the same node in the same request.
- B. When you create a request, data changes are not applied immediately.
- C. Requests are the mechanism that you use to apply changes to data.
- D. You can perform data changes across multiple views and submit all those changes together in the same request.
正解：B、C
解説：
* Requests are the mechanism that you use to apply changes to data: This option is correct because requests are the way that you make changes to enterprise data in Enterprise Data Management Cloud.
Requests can contain various types of data changes, such as adding, deleting, or editing nodes or properties.
* When you create a request, data changes are not applied immediately: This option is correct because when you create a request, the data changes are not applied to the viewpoints until the request is submitted and approved. You can review and modify the request items before submitting them.
質問 # 31
You are mapping nodes from dimensions in two source applications to a dimension in a single target application.
How do you set up the mapping hierarchy sets?
- A. Target nodes as parents and converted source nodes as children
- B. Target nodes in one hierarchy set and converted source nodes in a separate hierarchy set
- C. Separate hierarchy sets for each source-to-target relationship
- D. Target nodes and converted source nodes in two separate hierarchies
正解：C
解説：
When you are mapping nodes from dimensions in two source applications to a dimension in a single target application, you need to set up separate hierarchy sets for each source-to-target relationship. This way, you can define the mapping rules and node type converters for each source node type and target node type pair. You cannot use target nodes and converted source nodes in two separate hierarchies, because this would not establish a mapping relationship between them. You cannot use target nodes in one hierarchy set and converted source nodes in a separate hierarchy set, because this would not allow you to export the mappings to the target application. You cannot use target nodes as parents and converted source nodes as children, because this would create a hierarchical relationship instead of a mapping relationship. Reference: Working with Hierarchy Sets - Oracle Help Center1; Creating Mapping Viewpoints - Oracle Help Center2
質問 # 32
Which task can you perform after you have created an unbound dimension?
- A. You can use the unbound dimension just like a bound dimension when creating viewpoints and other user defined data chain objects.
- B. You can convert the unbound dimension to a bound dimension.
- C. You can create bindings for the unbound dimension, or use it for importing and exporting data.
- D. You can select the unbound dimension in the application registration wizard or the import and export screens.
- E. You can add bound or partially bound data chains to the unbound dimension.
正解：A
解説：
Explanation
After you have created an unbound dimension, you can use it just like a bound dimension when creating viewpoints and other user defined data chain objects and properties. You can also create extracts for the dimension, and add permissions, policies, and custom validations. However, you cannot convert an unbound dimension to a bound dimension, because this is not supported by Oracle Enterprise Data Management Cloud.
You cannot create bindings for an unbound dimension, or use it for importing and exporting data, because unbound dimensions are not related to any external applications. References: Working with Unbound Dimensions - Oracle Help Center
質問 # 33
Which two statements are true about the Participant permission?
- A. Granting the Participant (Read) permission at the application level lets users browse viewpoints that contain data for any dimension in the application.
- B. The Participant permission enables you to specify which actions users can take and which properties they can view or edit for node types and hierarchy sets.
- C. You can assign the Participant permission at the application, dimension, hierarchy set, node type, and property level.
- D. When you grant a user Participant (Write) permission on a hierarchy set, that user is also granted implicit Participant (Write) permission on any node type in that hierarchy set.
正解：A、B
解説：
Explanation
The Participant permission enables users to create requests or act as request assignees for data objects such as hierarchy sets and node types. You can assign the Participant permissionat different levels of granularity:
application, dimension, hierarchy set, node type, and property. You can also specify whether users have Read or Write access to data objects. Granting the Participant (Read) permission at the application level lets users browse viewpoints that contain data for any dimension in the application. However, they cannot create requests or act as request assignees unless they have Participant (Write) permission on specific data objects.
When you grant a user Participant (Write) permission on a hierarchy set, that user is not granted implicit Participant (Write) permission on any node type in that hierarchy set. They can only insert, move, remove, and reorder nodes in that hierarchy set. To add or delete nodes or update node properties, they need Participant (Write) permission on the node type as well. References: Working with Permissions - Oracle Help Center1
質問 # 34
You have a maintenance view that consists of the following viewpoints from different applications: GL Accounts, Consolidation Accounts, and Planning Accounts. You open a request and manually add a new account to GL Accounts.
In the same request, which two methods can you use to add the account to the other two viewpoints7
- A. Share manually: Drag and drop the new node from the GL Accounts viewpoint to the Consolidation and Planning viewpoints, after manually identifying the appropriate parents.
- B. Automatic insert: Select the new node and run the auto-insert tool to automatically identify comparable parents in the other viewpoints and insert the new node under them.
- C. Master alignment: Create a fourth viewpoint that represents a master combined account dimension and add the node there to insert it into all three applications.
- D. Compare and align: Run a comparison between the viewpoints to identify missing nodes. Search for the appropriate parents in the other viewpoints before dragging and dropping the new node to insert it into the other viewpoints.
正解：A、B
解説：
"You can share nodes manually or automatically between viewpoints in a maintenance view. To share nodes manually, you drag and drop nodes from one viewpoint to another. To share nodes automatically, you use the auto-insert tool." The other options are not valid methods to add the account to the other two viewpoints.
https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/dmcaa/subscriptions_admin_step1_maint_view.html
質問 # 35
......
今すぐトップクラスを試そう1z0-1086-22練習試験問題：https://jp.fast2test.com/1z0-1086-22-premium-file.html