A Fully Updated 2024 1z0-1086-22 Exam Dumps – PDF Questions and Testing Engine [Q14-Q35]

1z0-1086-22 Oracle

admin -

January 5, 2024

4.5/5 - (2 votes)

A Fully Updated 2024 1z0-1086-22 Exam Dumps – PDF Questions and Testing Engine

Easy Success Oracle 1z0-1086-22 Exam in First Try

Oracle 1z0-1086-22 exam is an excellent opportunity for professionals who want to demonstrate their expertise in Oracle Enterprise Data Management Cloud solutions. By passing the exam, professionals can differentiate themselves from their peers and demonstrate their commitment to their profession. Additionally, the Oracle 1z0-1086-22 exam is a valuable credential that can help professionals advance their careers and increase their earning potential.

To earn the Oracle 1z0-1086-22 certification, candidates must pass a 120-minute exam consisting of 60 multiple-choice questions. 1z0-1086-22 exam is available in English and Japanese and can be taken online or in-person at a Pearson VUE testing center. Candidates must achieve a passing score of 63% or higher to receive the certification. Oracle recommends that candidates have a strong understanding of Oracle Enterprise Data Management Cloud and real-world experience working with the solution before attempting the exam.

QUESTION 14
You have account dimensions in two different applications that must be kept in sync.
Given a business requirement that nodes added to either application must be shared with the other, what should you do?

Create one bi-directional node type converter between the two applications.

Create two node type converters: one with Application 1 accounts as the source and Application2 accounts as the target, and another with Application2 accounts as the source and Application 1 accounts as the target.

Create one node type converter with Application! accounts as the source and Application2 accounts as the target, and specify a reverse conversion in requests when sharing in the opposite direction.

Create three node type converters: one with Application! accounts as the source and Application2 accounts as the target, another with Application2 accounts as the source and Application! accounts as the target, and a third for bi-directional sharing.

According to the reference, “A node type converter is a data object that enables you to share nodes between different node types in different applications.” To keep account dimensions in sync between two applications, you need to create two node type converters, one for each direction of sharing. You cannot create a bi-directional node type converter, or specify a reverse conversion in requests.
To keep account dimensions in two different applications in sync and share nodes added to either application with the other, you can create two node type converters. One node type converter can have application 1 accounts as the source and application 2 accounts as the target, and the other node type converter can have application 2 accounts as the source and application 1 accounts as the target. This will ensure that nodes added to either application are shared with the other. (Reference: Oracle Enterprise Data Management Cloud 2022 Implementation Essentials, Module 3)

QUESTION 15
Maintenance views contain viewpoints from multiple applications. What two types of sharing do these views facilitate?

Sharing workflows and approvals for comparable dimensions across applications

Adding new nodes to comparable dimensions across multiple applications

Copying hierarchies from one application to another

Aligning nodes and property values between comparable dimensions in different applications

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

QUESTION 16
In your application, you have nodes for cost centers. You want to group them two ways: by department and geography.
What are two ways to accomplish this?

Create two hierarchy sets; one where parent nodes are departments and child nodes are cost centers; and another where parent nodes are geographical regions and child nodes are cost centers.

Create a list viewpoint for cost centers, then add parents for departments and geography.

Create two node sets; one with a group of departments and another with a group of geographical regions.

Create one hierarchy set with different top nodes for departments and geography, and add shared cost center nodes as children.

Hierarchy sets define nodes’ parent-child relationships. You can use hierarchy sets to organize nodes into different hierarchies based on business needs or perspectives. One way to group cost centers by department and geography is to create two hierarchy sets; one where parent nodes are departments and child nodes are cost centers; and another where parent nodes are geographical regions and child nodes are cost centers. Another way is to create one hierarchy set with different top nodes for departments and geography, and add shared cost center nodes as children. Shared nodes allow the same nodes to exist multiple times in the hierarchy set. You cannot use a list viewpoint or node sets to group cost centers by department and geography, because they do not define parent-child relationships or hierarchies. Reference: Working with Hierarchy Sets – Oracle Help Center

QUESTION 17
Which two statements are true about the Participant permission?

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.

Granting the Participant (Read) permission at the application level lets users browse viewpoints that contain data for any dimension in the application.

You can assign the Participant permission at the application, dimension, hierarchy set, node type, and property level.

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.

“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.” and “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.” The other statements are false. Granting the Participant (Read) permission at the application level does not let users browse viewpoints that contain data for any dimension in the application, but only lets them browse viewpoints that contain data for dimensions where they have been granted explicit permissions. You cannot assign the Participant permission at the property level.

QUESTION 18
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?

You can define your own hierarchy sets when you want to create alternate hierarchies using different relationships between the same or different node types.

Node types manage nodes and properties.

A hierarchy uses all the data chain objects.

Node sets define the group of nodes available in viewpoints.

Views are a collection of node sets and hierarchy sets.

A viewpoint is the interface you use to display and edit information, and work with 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.

QUESTION 19
What are two scenarios where mapping nodes across applications are required?

When applications share data but have different dimensions

When applications have common dimensions but use different prefixes or suffixes for member names

When applications share common dimensions but use different granularity

When applications share an external connection

“Suppose you have an acquired company with a general ledger, and you want to map the general ledger accounts to planning accounts. The general ledger accounts have different prefixes than the planning accounts.” This is an example of a scenario where mapping nodes across applications is required. Another scenario is when applications share data but have different dimensions, such as when mapping accounts from a GL application to a Planning application. The other options are not scenarios where mapping nodes across applications is required.

QUESTION 20
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?

You can define your own hierarchy sets when you want to create alternate hierarchies using different relationships between the same or different node types.

Node types manage nodes and properties.

A hierarchy uses all the data chain objects.

Node sets define the group of nodes available in viewpoints.

Views are a collection of node sets and hierarchy sets.

A viewpoint is the interface you use to display and edit information, and work with 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.
Reference:
https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/edmra/understanding-data-chains.html

QUESTION 21
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

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.

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.

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.

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.

Explanation
If you have a maintenance view that consists of viewpoints from different applications, and you open a request and manually add a new node to one of the viewpoints, you can use two methods to add the node to the other viewpoints: share manually or compare and align. Share manually means dragging and dropping the new node from one viewpoint to another viewpoint, after manually identifying the appropriate parents. This way, you can create new nodes in the target viewpoint that have properties derived or transformed from the source nodes using the node type converter and map binding. Compare and align means running a comparison between the viewpoints to identify missing nodes, then searching for the appropriate parents in the target viewpoint before dragging and dropping the new node to insert it into the target viewpoint. This way, you can also create new nodes in the target viewpoint that have properties derived or transformed from the source nodes using the node type converter and map binding. You cannot use master alignment or automatic insert methods, because these are not supported by Oracle Enterprise Data Management Cloud. References: Working with Requests – Oracle Help Center3; Comparing Viewpoints – Oracle Help Center

QUESTION 22
A request has a status of “In Flight.” In which stage of the approval workflow is the request?

Approve

Closed

Submit

Review

* Approve: This option is correct because when a request has a status of “In Flight”, it means that it is in the Approve stage of the approval workflow, where it is waiting for approvals from the approvers or data managers.

QUESTION 23
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?

After exceeding the defined number of approval notifications, the request is pushed back to the original submitter and must be submitted and approved again.

The request is escalated to a data manager, who grants an exceptional approval and commits the request.

The request is escalated to an application owner, who changes the approval policy to require fewer approvers, at which point the request is committed.

The request is closed after exceeding the defined number of approval notifications and cannot be committed.

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.
Reference:
https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/edmra/approving-and-enriching-requests.html

QUESTION 24
Maintenance views contain viewpoints from multiple applications. What two types of sharing do these views facilitate?

Sharing workflows and approvals for comparable dimensions across applications

Adding new nodes to comparable dimensions across multiple applications

Copying hierarchies from one application to another

Aligning nodes and property values between comparable dimensions in different applications

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. Reference: Working with Maintenance Views – Oracle Help Center2

QUESTION 25
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?

Separate hierarchy sets for each source-to-target relationship

Target nodes and converted source nodes in two separate hierarchies

Target nodes in one hierarchy set and converted source nodes in a separate hierarchy set

Target nodes as parents and converted source nodes as children

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

QUESTION 26
Which EPM Automate command can you use to restart services on your instance?

restartService

recreateService

startService

resetService

Explanation
The restartService command restarts the services on an environment. This command is useful when you want to refresh an environment after performing maintenance tasks such as importing or exporting snapshots or uploading files. References: Using EPM Automate Commands – Oracle Help Center2

QUESTION 27
A node exists in a hierarchy. Which three types of properties could be present7

Inherited properties

Relationship properties

Hierarchy properties

Node properties

Shared properties

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

QUESTION 28
You define an approval policy at the dimension level.
What statement correctly describes how this approval policy interacts with related data chain objects?

The approval policy applies to the node types and hierarchy sets in the dimension.

The approval policy cascades down to only the data chain objects specified in the policy definition.

The approval policy applies to hierarchy sets but not node sets in the dimension.

The approval policy applies to only the dimension and does not apply to related data chain objects.

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

QUESTION 29
Which three statements are true about lookup sets7

You use lookup sets in expressions for deriving properties or transforming properties in node type converters.

Lookup sets associate source values, or keys, with target values.

Keys and values in a lookup set can be configured for one or more applications.

Lookup sets are created during application registration.

You can use lookup sets to group and filter nodes.

Explanation
Lookup sets are used to associate source values, or keys, with target values that can be used in expressions for deriving properties or transforming properties in node type converters. You can configure keys and values in a lookup set for one or more applications. Lookup sets are not created during application registration, but rather as separate objects that can be shared acrossapplications. Lookup sets are not used to group and filter nodes, but rather to map values between different applications or perspectives. References: Working with Lookup Sets – Oracle Help Center2

QUESTION 30
In a list viewpoint, what are the related data chain objects?

Node type, node set, dimension

Node type, hierarchy set, node set, properties

Node type, node set

Node type, node set, properties

Node type, hierarchy set, node set

Explanation
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. References: Working with List Viewpoints – Oracle Help Center

QUESTION 31
After submitting a request for approval, you discover that you need to make additional changes to it. What two options do you have?

Create a second request with the additional changes, and submit it for separate approval.

Recall the request and delete it. Create a new request with all of the required changes and submit it for approval.

Push the request back to the submit stage, add the changes, then submit it again for approval.

Recall the request, add the changes, then submit it again for approval.

* Create a second request with the additional changes, and submit it for separate approval: This option is correct because you can create another request with the additional changes and submit it for approval while the first request is still in progress. However, this option may create conflicts or dependencies between the requests that need to be resolved later.
* Recall the request, add the changes, then submit it again for approval: This option is correct because you can recall a request that you submitted for approval and make changes to it before submitting it again for approval. However, this option may cause delays in the approval workflow and require rework by the approvers.

QUESTION 32
Which two things occur during application registration7

The system generates default data objects based on your selections in the registration wizard.

The system generates connections to external applications.

The system imports external application data to determine the application configuration.

You select an Enterprise Data Management Cloud application type.

You load dimension data from flat files.

QUESTION 33
Which two statements are true about requests?

Requests are the mechanism that you use to apply changes to data.

When you create a request, data changes are not applied immediately.

You can perform data changes across multiple views and submit all those changes together in the same request.

You cannot make multiple changes to the same node in the same request.

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

QUESTION 34
Which three tasks can you automate with EPM Automate?

Archive backups

Import and export dimensions

Create and auto-submit change requests

Recreate service

Export and import snapshots

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. Reference: About EPM Automate – Oracle Help Center1

QUESTION 35
In your application, you have nodes for cost centers. You want to group them two ways: by department and geography.
What are two ways to accomplish this?

Create two hierarchy sets; one where parent nodes are departments and child nodes are cost centers; and another where parent nodes are geographical regions and child nodes are cost centers.

Create a list viewpoint for cost centers, then add parents for departments and geography.

Create two node sets; one with a group of departments and another with a group of geographical regions.

Create one hierarchy set with different top nodes for departments and geography, and add shared cost center nodes as children.

Explanation
Hierarchy sets define nodes’ parent-child relationships. You can use hierarchy sets to organize nodes into different hierarchies based on business needs or perspectives. One way to group cost centers by department and geography is to create two hierarchy sets; one where parent nodes are departments and child nodes are cost centers; and another where parent nodes are geographical regions and child nodes are cost centers.
Another way is to create one hierarchy set with different top nodes for departments and geography, and add shared cost center nodes as children. Shared nodes allow the same nodes to exist multiple times in the hierarchy set. You cannot use a list viewpoint or node sets to group cost centers by department and geography, because they do not define parent-child relationships or hierarchies. References: Working with Hierarchy Sets
– Oracle Help Center

Loading …