1z0-1086-22 Practice Exam Tests Latest Updated on Jun-2023
Pass 1z0-1086-22 Exam in First Attempt Guaranteed Dumps!
NEW QUESTION # 17
Which two methods are valid ways to create request items?
- A. By loading a text file
- B. Manually in a view
- C. By loading an Excel spreadsheet
- D. By running a batch script with data changes
Answer: B,C
Explanation:
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.
NEW QUESTION # 18
A request you submitted has been pushed back to you. One of the approvers has enriched the request with an action that your data access does not enable you to perform.
What happens when you submit the request again?
- A. The enriched item is validated using the enricher's data access ancTtan be submitted along with the rest of the request.
- B. 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.
- C. The enriched item creates a validation error and must be deleted from the request inspector before you can submit the request for approval.
- D. The enriched item creates a validation error but can still be submitted with the rest of the request for approval.
Answer: B
Explanation:
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.
Reference:
https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/edmra/approving-and-enriching-requests.html
NEW QUESTION # 19
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. A node type converter with the Account (GL) node type as source and Account Mapping (Planning) node type as target
- B. Account Mapping dimension
- C. Account Mapping viewpoint in the default Planning application view
- D. Account Mapping node set
- E. Account Mapping hierarchy set
Answer: A,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. Reference: Working with Map Bindings - Oracle Help Center; Working with Node Type Converters - Oracle Help Center
NEW QUESTION # 20
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?
- A. The request is closed after exceeding the defined number of approval notifications and cannot be committed.
- B. The request is escalated to a data manager, who grants an exceptional approval and commits the request.
- C. The request is escalated to an application owner, who changes the approval policy to require fewer approvers, at which point the request is committed.
- D. After exceeding the defined number of approval notifications, the request is pushed back to the original submitter and must be submitted and approved again.
Answer: B,C
Explanation:
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
NEW QUESTION # 21
A subscription is triggered by changes in a source viewpoint. One item in the subscription request is invalid and auto-submit is enabled.
What happens next?
- A. The request is automatically rejected, and the subscription assignee is notified of the rejection.
- B. All request items except the invalid item are automatically committed to the target viewpoint, and the subscription assignee is notified that an issue must be resolved for the outstanding item.
- C. All request items are automatically committed to the target viewpoint, and the subscription assignee is notified.
- D. No request items are committed to the target viewpoint, and the subscription assignee is notified that an issue must be resolved before any items can be committed.
Answer: D
Explanation:
* No request items are committed to the target viewpoint, and the subscription assignee is notified that an issue must be resolved before any items can be committed: This option is correct because when a subscription is triggered by changes in a source viewpoint and auto-submit is enabled, the request isautomatically submitted for approval. However, if one or more items in the request are invalid, the request is not approved and no items are committed to the target viewpoint. The subscription assignee is notified that an issue must be resolved before the request can be approved and committed.
NEW QUESTION # 22
The Owner permission for an application lets users perform which three tasks?
- A. Modify application registration.
- B. Delete service administrators from an instance.
- C. Import viewpoints from external applications.
- D. Manage an application's data objects.
- E. Assign permissions for an application's data objects to other users and groups.
Answer: A,D,E
Explanation:
The Owner permission is the highest level of permission that can be assigned to an application. Users with the Owner permission can perform various tasks such as: modify application registration, assign permissions for an application's data objects to other users and groups, manage an application's data objects such as properties, views, node types, node sets, hierarchy sets, etc., create and delete applications, and link dimensions across applications. Users with the Owner permission cannot import viewpoints from external applications, because viewpoints are created within Oracle Enterprise Data Management Cloud and are not imported from external applications. Users with the Owner permission cannot delete service administrators from an instance, because service administrators are created and managed in Oracle Cloud EPM through My Services by the Identity Domain Administrator. Reference: Working with Permissions - Oracle Help Center1; Registering Applications - Oracle Help Center2
NEW QUESTION # 23
You have mapped accounts from two different general ledger applications to your Planning application. What do you do when it's time to synchronize the changes by exporting the mappings?
- A. You run three exports, one for each source and one for the target.
- B. You run four exports, one for each viewpoint involved in the mapping.
- C. You run two separate exports, one for each source-to-target location.
- D. You run a single export for the target that contains all mappings for both sources.
Answer: C
Explanation:
Explanation
When you have mapped accounts from two different general ledger applications to your Planning application, you need to run two separate exports, one for each source-to-target location, when it's time to synchronize the changes by exporting the mappings. This way, you can export the mapping data from each source node type to the corresponding target node type using the appropriate node type converter and map binding. You do not need to run three exports, one for each source and one for the target, because this would not export the mapping data correctly. You do not need to run a single export for the target that contains all mappings for both sources, because this would not use the correct node type converters and map bindings for each source-to-target pair. You do not need to run four exports, one for each viewpoint involved in the mapping, because this would be redundant and inefficient. References: Working with Requests - Oracle Help Center3; Creating Mapping Viewpoints - Oracle Help Center
NEW QUESTION # 24
In a maintenance view for mappings, you compare the source and mapping viewpoints to identify nodes that exist in the source but have not been mapped to the target.
What is the next step to define mappings?
- A. Open a request, add nodes to the target viewpoint, and assign the mapping key to the new nodes.
- B. Run the mapping utility to relate source to target nodes.
- C. Create a request, then drag and drop nodes from the source to the mapping viewpoint.
- D. Using the appropriate mapping key, import an Excel mapping file.
Answer: C
Explanation:
Explanation
In a maintenance view for mappings, you can compare the source and mapping viewpoints to identify nodes that exist in the source but have not been mapped to the target. The next step to define mappings is to create a request, then drag and drop nodes from the source to the mapping viewpoint. This way, you can create new nodes in the mapping viewpoint that have properties derived or transformed from the source nodes using the node type converter and map binding. You do not need to use an Excel mapping file, run a mapping utility, or open a request and add nodes to the target viewpoint, because these are not supported methods for defining mappings in Oracle Enterprise Data Management Cloud. References: Working with Requests - Oracle Help Center3; Creating Mapping Viewpoints - Oracle Help Center2
NEW QUESTION # 25
What are two scenarios where mapping nodes across applications are required?
- A. When applications share common dimensions but use different granularity
- B. When applications share data but have different dimensions
- C. When applications share an external connection
- D. When applications have common dimensions but use different prefixes or suffixes for member names
Answer: B,D
Explanation:
"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.
NEW QUESTION # 26
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. Link the account dimension in the General Ledger application to the account dimension in the Planning application.
- B. 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.
- 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 maintenance view with viewpoints for both the General Ledger account dimension and the Planning account dimension.
Answer: A,D
Explanation:
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.
NEW QUESTION # 27
Which statement is true about permissions?
- A. By default, when you assign the Participant permission to a user or group, their data access is set to Write.
- 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. 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. Permissions assigned to a dimension do not also apply to the hierarchy sets and node types that they contain.
Answer: C
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. Reference: Working with Permissions - Oracle Help Center1
NEW QUESTION # 28
You are an assignee for a subscription that listens for changes in a source viewpoint, and auto-submit is not enabled.
What happens when a request is submitted that changes the source viewpoint?
- A. The system sends you a notification of the original source request, which you can then review and copy into your target viewpoint.
- B. The system converts the original request items into a new subscription request for the target viewpoint and sends you a notification to review and submit the request.
- C. The system sends you a notification of the original source request and includes a link to manually convert it to a new request for the target viewpoint.
- D. The system sends you a notification with an attachment of the original request items, which you can then load into a new request.
Answer: B
Explanation:
The system converts the original request items into a new subscription request for the target viewpoint and sends you a notification to review and submit the request: This option is correct because when a subscription is triggered by changes in a source viewpoint and auto-submit is not enabled, the system creates a new subscription request for the target viewpoint with the same request items as the original request. The system then sends a notification to the subscription assignee to review and submit the request.
Reference:
https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/edmra/creating-subscriptions.html
NEW QUESTION # 29
Which two items describe the information that you can find in the Custom Validation Report?
- A. A list of all manually created validations across all applications
- B. The date and status of the last time a validation was run
- C. The actions and properties that trigger the validation check
- D. A list of system and application-specific validations
Answer: C,D
Explanation:
Explanation
The Custom Validation Report is a report that lists all the custom validations that have been created for an application. The report includes information such as: the actions and properties that trigger the validation check, the validation rule expression and message, the node types and hierarchy sets that use the validation, and whether the validation is enabled or disabled. The report does not include a list of all manually created validations across all applications, because it is specific to one application at a time. The report does not include a list of system and application-specific validations, because these are predefined validations that cannot be customized. The report does not include the date and status of the last time a validation was run, because this information is available in the request history or subscription history. References: Working with Custom Validations - Oracle Help Center
NEW QUESTION # 30
Which three statements are true about an alternate viewpoint in an unbound state7
- A. 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.
- B. 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.
- C. 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.
- D. You cannot use the alternate viewpoint to construct a what-if scenario that is isolated from production.
- E. The alternate viewpoint may be partially bound if it shares data chain objects with a bound viewpoint.
Answer: A,C
Explanation:
"An alternate viewpoint is a data object that enables you to create an alternate version of a bound viewpoint that is not used in a binding. All of the data chain objects that it contains have a binding status of Unbound." and "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 other statements are false. 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 can use the alternate viewpoint to construct a what-if scenario that is isolated from production. The alternate viewpoint cannot be partially bound if it shares data chain objects with a bound viewpoint.
NEW QUESTION # 31
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. A node type converter with the Account (GL) node type as source and Account Mapping (Planning) node type as target
- B. Account Mapping dimension
- C. Account Mapping viewpoint in the default Planning application view
- D. Account Mapping node set
- E. Account Mapping hierarchy set
Answer: A,D,E
Explanation:
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
NEW QUESTION # 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 create bindings for the unbound dimension, or use it for importing and exporting data.
- C. You can add bound or partially bound data chains to the unbound dimension.
- D. You can select the unbound dimension in the application registration wizard or the import and export screens.
- E. You can convert the unbound dimension to a bound dimension.
Answer: B
Explanation:
"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.
NEW QUESTION # 33
Which two statements are true about exporting dimensions and mappings7
- A. For Planning and Universal applications, you can export enterprise data using either a connection or a comma-delimited file.
- B. All application types support exporting dimensions and mappings to registered external applications using connections.
- C. For bound hierarchy viewpoints, nodes are exported starting with the top nodes.
- D. You need the Data Manager or Owner permission to the application to export its dimensions and mappings.
Answer: A,D
Explanation:
1. 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.
2. 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.
Reference:
https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/edmra/exporting-enterprise-data.html
NEW QUESTION # 34
Which two statements are true about mapping keys?
- A. The system automatically generates mapping keys for each unique location.
- B. Mapping keys consist of a location, source node type, and target node type.
- C. Mapping keys control which dimensions are output in the source and target columns of the mapping export.
- D. One mapping key is required per location.
Answer: B,C
Explanation:
Explanation
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. The following statements are true about mapping keys: mapping keys consist of a location, source node type, and target node type; mapping keys control which dimensions are output in the source and target columns of the mapping export. The following statements are false about mapping keys: the system automatically generates mapping keys for each unique location; one mapping key is required per location. You need to manually define mapping keys for each source-to-target relationship using a unique location name. You can have multiple mapping keys for the same location if you have different source node types mapped to the same target node type. References: Defining Mapping Keys - Oracle Help Center1; Exporting Mapping Data - Oracle Help Center
NEW QUESTION # 35
Maintenance views contain viewpoints from multiple applications. What two types of sharing do these views facilitate?
- A. Aligning nodes and property values between comparable dimensions in different applications
- B. Adding new nodes to comparable dimensions across multiple applications
- C. Copying hierarchies from one application to another
- D. Sharing workflows and approvals for comparable dimensions across applications
Answer: A,B
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. Reference: Working with Maintenance Views - Oracle Help Center2
NEW QUESTION # 36
Which two objects can you transfer using templates?
- A. Data
- B. Dimensions
- C. Transaction history
- D. Applications
- E. Requests
Answer: B,D
Explanation:
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. Reference: Working with Templates - Oracle Help Center1
NEW QUESTION # 37
Which two objects can you transfer using templates?
- A. Data
- B. Dimensions
- C. Transaction history
- D. Applications
- E. Requests
Answer: B,D
Explanation:
Explanation
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
NEW QUESTION # 38
Which three are use case examples of node type validations?
- A. Start date must occur before end date.
- B. Property values must be in a certain format.
- C. Node type names must conform to naming conventions.
- D. Rollup nodes must have enabled base nodes below them.
- E. Hierarchy levels must match specific node types.
Answer: A,B,E
Explanation:
"A node type validation is a data object that enables you to define rules for validating nodes of a specific node type. You can use node type validations to check for conditions such as: Property values are in a certain format; Start date occurs before end date; Hierarchy levels match specific node types." The other options are not examples of node type validations.
NEW QUESTION # 39
In a list viewpoint, what are the related data chain objects?
- A. Node type, node set, dimension
- B. Node type, node set
- C. Node type, hierarchy set, node set, properties
- D. Node type, hierarchy set, node set
- E. Node type, node set, properties
Answer: B
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. Reference: Working with List Viewpoints - Oracle Help Center3
NEW QUESTION # 40
......
Enterprise Data Management Free Certification Exam Material from TroytecDumps with 60 Questions: https://actualtests.troytecdumps.com/1z0-1086-22-troytec-exam-dumps.html