厳密検証された1z0-1086-22試験問題集と解答で無料提供の1z0-1086-22問題と正解付き
あなたを合格させる1z0-1086-22問題集で無料最新Oracle練習テスト
質問 # 10
You have a source viewpoint with an entity hierarchy with top nodes defined for Departments and Geography.
Your target viewpoint only has departments.
If you define a subscription that is filtered by the Department top node, what happens when changes are made to the Geography hierarchy in the source viewpoint?
- A. The system notifies the request assignee that changes were made to the Geography hierarchy, but generates no request items.
- B. The system creates a subscription request and flags request items for the Geography hierarchy for deletion.
- C. The system creates an empty subscription request for tracking purpose, but does not notify the request assignees.
- D. The system does not create a subscription request.
正解：D
解説：
Explanation
When a data manager submits a request in a view that has subscriptions defined, the system only generates subscription requests for the viewpoints that match the filter criteria of the subscriptions. If changes are made to a viewpoint that does not match the filter criteria, the system does not create a subscription request for that viewpoint. References: Creating, Editing, and Validating Subscriptions - Oracle Help Center1
質問 # 11
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?
- A. Account Mapping dimension
- B. Account Mapping viewpoint in the default Planning application view
- C. A node type converter with the Account (GL) node type as source and Account Mapping (Planning) node type as target
- D. Account Mapping node set
- E. Account Mapping hierarchy set
正解：C、D、E
解説：
Explanation
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. References: Working with Map Bindings - Oracle Help Center; Working with Node Type Converters - Oracle Help Center
質問 # 12
Which two statements are true about hierarchy sets?
- A. You can manage multiple hierarchies in a single hierarchy set.
- B. Shared nodes exist when the same node type is used in multiple hierarchy sets.
- C. Hierarchy sets are always a component of a viewpoint's data chain.
- D. Hierarchy sets store the parent-child relationships between nodes of node types defined for a dimension.
正解：B、D
解説：
Explanation
Hierarchy sets store the parent-child relationships between nodes of node types defined for a dimension. You can use hierarchy sets to organize nodes into different hierarchies based on business needs or perspectives.
Hierarchy sets are not always a component of a viewpoint's data chain. A viewpoint can contain only one hierarchy set per dimension or none at all. You cannot manage multiple hierarchies in a single hierarchy set.
Each hierarchy set contains one or more hierarchies for one node type only. Shared nodes exist when the same node type is used in multiple hierarchy sets. A shared node is a node that belongs to more than one hierarchy set and has different parents in each hierarchy set. References: Working with Hierarchy Sets - Oracle Help Center2
質問 # 13
Which are two reasons for creating a migration snapshot?
- A. To refresh the test environment from the production environment
- B. To restore the artifacts and data to the snapshot state
- C. To export the enterprise data to an external application
- D. To download the enterprise data locally for offline work
- E. To migrate the enterprise data between different releases of the environment
正解：A、E
解説：
* B. To migrate the enterprise data between different releases of the environment: This option is correct because a migration snapshot can be used to export andimport enterprise data between different environments or instances of Enterprise Data Management Cloud, such as from test to production or vice versa.
* D. To refresh the test environment from the production environment: This option is correct because a migration snapshot can be used to refresh the test environment with the latest enterprise data from the production environment.
質問 # 14
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 add bound or partially bound data chains to the unbound dimension.
- C. You can convert the unbound dimension to a bound dimension.
- D. You can create bindings for the unbound dimension, or use it for importing and exporting data.
- E. You can select the unbound dimension in the application registration wizard or the import and export screens.
正解：D
解説：
"You can create bindings for unbound dimensions, or use them for importing and exporting data." The other options are not tasks that you can perform after you have created an unbound dimension.
質問 # 15
Which two methods are valid ways to create request items?
- A. By running a batch script with data changes
- B. By loading a text file
- C. By loading an Excel spreadsheet
- D. Manually in a view
正解：C、D
解説：
You can create request items manually in a view or by loading an Excel spreadsheet." You cannot create request items by loading a text file or by running a batch script with data changes.
質問 # 16
Which two things occur during application registration7
- A. The system generates connections to external applications.
- 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. You load dimension data from flat files.
正解：B、C
質問 # 17
In what order do you archive data chain objects?
- A. Viewpoint, node set, hierarchy set, node type
- B. Viewpoint, dimension, application
- C. Node type, hierarchy set, node set, viewpoint
- D. Application, dimension, viewpoint
- E. You can archive data chain objects in any order
正解：C
解説：
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
質問 # 18
A node exists in a hierarchy. Which three types of properties could be present7
- A. Relationship properties
- B. Inherited properties
- C. Shared properties
- D. Hierarchy properties
- E. Node properties
正解：A、B、E
解説：
"A node is an instance of a node type that represents a member in a hierarchy. A node has properties that describe its characteristics and behavior. There are three types of properties for nodes: Node properties; Relationship properties; Inherited properties." The other options are not types of properties for nodes.
質問 # 19
Which three statements are true about an alternate viewpoint in an unbound state7
- A. Unbound data objects in an alternate viewpoint enable you to model and evaluate potential changes to dimensions in cases where the changes would not conform to a dimension's current binding rules.
- B. You cannot use the alternate viewpoint to construct a what-if scenario that is isolated from production.
- C. The alternate viewpoint is not used in a binding, but all of the data chain objects that it contains have a binding status of Bound.
- D. The alternate viewpoint is not used in a binding and all of the data chain objects that it contains have a binding status of Unbound.
- E. The alternate viewpoint may be partially bound if it shares data chain objects with a bound viewpoint.
正解：D、E
解説：
Explanation
An alternate viewpoint is a viewpoint that lets you see enterprise data organized in a different way. Nodes can be aggregated, rolled up, or summarized using a hierarchy that differs from the hierarchy in the bound viewpoint. An alternate viewpoint can be in an unbound state or a partially bound state. The following statements are true about an alternate viewpoint in an unbound state: the alternate viewpoint is not used in a binding and all of the data chain objects that it contains have a binding status of Unbound; unbound data objects in an alternate viewpoint enable you to model and evaluate potential changes to dimensions in cases where the changes would not conform to a dimension's current binding rules; the alternate viewpoint may be partially bound if it shares data chain objects with a bound viewpoint. The following statements are false about an alternate viewpoint in an unbound state: the alternate viewpoint is not used in a binding, but all of the data chain objects that it contains have a binding status of Bound; you cannot use the alternate viewpoint to construct a what-if scenario that is isolated from production. An unbound alternate viewpoint does not have any bound data objects, because it is not related to any external applications. You can use an unbound alternate viewpoint to construct a what-if scenario that is isolated from production, because it does not affect the bound viewpoint or the external applications. References: Defining AlternateViewpoints - Oracle Help Center1; Understanding Bindings and Bound Data Objects - Oracle Help Center2
質問 # 20
Which task can you perform after you have created an unbound dimension?
- A. You can add bound or partially bound data chains to the unbound dimension.
- B. You can use the unbound dimension just like a bound dimension when creating viewpoints and other user defined data chain objects.
- C. You can convert the unbound dimension to a bound dimension.
- D. You can create bindings for the unbound dimension, or use it for importing and exporting data.
- E. You can select the unbound dimension in the application registration wizard or the import and export screens.
正解：B
解説：
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
質問 # 21
Which three tasks can be performed by a user with the Data Manager permission on an application?
- A. Assign permissions for the application data.
- B. Create and submit requests for dimensions in the application.
- C. Import, export, and update data for all dimensions in the application.
- D. Manage viewpoints and viewpoint subscriptions for all dimensions in the application.
- E. Manage the application's node sets, hierarchy sets, and node types.
正解：B、C、D
解説：
The Data Manager permission is the second highest level of permission that can be assigned to an application. Users with the Data Manager permission can perform various tasks such as: import, export, and update data for all dimensions in the application, create and submit requests for dimensions in the application, manage viewpoints and viewpoint subscriptions for all dimensions in the application, run business rules on dimensions in the application, copy data across dimensions in the application, etc. Users with the Data Manager permission cannot manage the application's node sets, hierarchy sets, and node types, because these are data objects that require Owner permission to manage. Users with the Data Manager permission cannot assign permissions for the application data, because this requires Owner permission as well. Reference: Working with Permissions - Oracle Help Center1; Working with Requests - Oracle Help Center3
質問 # 22
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 maintenance view with viewpoints for both the General Ledger account dimension and the Planning account dimension.
- B. Link the account dimension in the General Ledger application to the account dimension in the Planning application.
- C. 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.
- D. 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.
正解：A、B
解説：
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.
質問 # 23
Maintenance views contain viewpoints from multiple applications. What two types of sharing do these views facilitate?
- A. Copying hierarchies from one application to another
- B. Aligning nodes and property values between comparable dimensions in different applications
- C. Sharing workflows and approvals for comparable dimensions across applications
- D. Adding new nodes to comparable dimensions across multiple applications
正解：B、D
解説：
Explanation
Maintenance views are views that contain viewpoints from multiple applications that facilitate sharing data across applications. Maintenance views enable you to add new nodes to comparable dimensions across multiple applications by creating requests or subscriptions that include viewpoints from different applications.
Maintenance views also enable you to align nodes and property values between comparable dimensions in different applications by using compare functions or property derivations. Maintenance views do not facilitate sharing workflows and approvals for comparable dimensions across applications, because workflows and approvals are defined at the application level and are not shared across applications. Maintenance views do not facilitate copying hierarchies from one application to another, because hierarchies are defined by hierarchy sets and are not shared across applications. References: Working with Maintenance Views - Oracle Help Center2
質問 # 24
Which task is NOT part of the Enterprise Data Management process?
- A. Sharing, mapping, synchronizing, and governing data across registered applications
- B. Creating views and viewpoints to configure custom validations to enforce business rules on your data
- C. Using views to work with your data, and requests to modify your data
- D. Creating ad-hoc reports to inspect node locations, properties, and history
- E. Creating views and viewpoints to manage alternate business perspectives
正解：B
解説：
* 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.
質問 # 25
Approval Policy definition: Markfo
* Approval Method = Parallel
* One Approval Per Group = NOT selected
* Total Required approvals = 4
Approvers:
* Group 1: User1, User2, User3
* Group 2: User4, User5, User6
* Group 3: User3, User8, User9
Given the above approval policy and approvers, which statement correctly describes how the approvals workflow is enacted?
- A. Members of the three approval groups can approve in any order, and at least one approval is required from each group to meet the required number of approvals.
- B. Every member of the three approval groups must approve, but can do so in any order.
- C. Members of the three approval groups can approve in any order, and approvals are not required from all three groups as long as the total required number of approvals is met.
- D. Members of the first approval group can approve in any order, but must provide at least one approval before the workflow moves to the second approval group.
正解：C
解説：
This option is correct because when the approval method is parallel and one approval per group is not selected, the approvers from different groups can approve in any order and the request is approved when the total required number of approvals is met, regardless of which groups they belong to.
Reference:
https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/edmra/creating-approval-policies.html
質問 # 26
A node exists in a hierarchy. Which three types of properties could be present7
- A. Inherited properties
- B. Relationship properties
- C. Shared properties
- D. Hierarchy properties
- E. Node properties
正解：B、C、E
解説：
Explanation
A node can have different types of properties depending on its position and behavior in a hierarchy. The types of properties that a node can have are: relationship properties, node properties, shared properties, and inherited properties. Relationship properties are properties that define the relationship between a node and its parent node in a hierarchy. For example, the Core.Parent property specifies the parent node of a node in a hierarchy.
Node properties are properties that define the characteristics of a node itself. For example, the Core.Name property specifies the name of a node. Shared properties are properties that apply to shared nodes, which are nodes that can be included in different branches of a hierarchy. For example, the Core.Shared property indicates whether a node is shared or not. Inherited properties are properties that are inherited from ancestor nodes in a hierarchy. For example, the Core.Inherited property indicates whether a property value is inherited or not. Hierarchy properties are not a type of property that a node can have, because hierarchy properties are defined by hierarchy sets and apply to hierarchies rather than nodes. References: Working with Properties - Oracle Help Center
質問 # 27
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 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.
- B. You create shadow mapping keys in the target application to represent the values coming from GL1 and GL2, respectively.
- C. You need only one mapping key and location to export the plan account mappings.
- D. You create one location per mapping key, where a mapping key is a unique source-target combination.
正解：A
解説：
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
質問 # 28
Which task is NOT part of the Enterprise Data Management process?
- A. Sharing, mapping, synchronizing, and governing data across registered applications
- B. Creating views and viewpoints to configure custom validations to enforce business rules on your data
- C. Using views to work with your data, and requests to modify your data
- D. Creating ad-hoc reports to inspect node locations, properties, and history
- E. Creating views and viewpoints to manage alternate business perspectives
正解：B
解説：
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.
Reference:
https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/edmra/configuring-custom-validations.html
質問 # 29
In a list viewpoint, what are the related data chain objects?
- A. Node type, node set, properties
- B. Node type, node set
- C. Node type, hierarchy set, node set
- D. Node type, hierarchy set, node set, properties
- E. Node type, node set, dimension
正解：B
解説：
A list viewpoint is a viewpoint that contains only one node type and one node set. A list viewpoint does not contain any hierarchy sets or properties. A list viewpoint is used to manage flat lists of nodes without parent-child relationships or hierarchies. A list viewpoint is related to a dimension through its node type and node set. Reference: Working with List Viewpoints - Oracle Help Center3
質問 # 30
......
無料でゲット！高評価Oracle 1z0-1086-22試験問題集今すぐダウンロード！：https://jp.fast2test.com/1z0-1086-22-premium-file.html