Best Oracle 1z0-1086-22 Exam Practice Material Updated on Nov 02, 2023 [Q29-Q52]

Share

Best Oracle 1z0-1086-22 Exam Practice Material Updated on Nov 02, 2023

New 1z0-1086-22 Actual Exam Dumps,  Oracle Practice Test


Oracle 1z0-1086-22 exam is a challenging test that requires candidates to demonstrate their knowledge of Oracle Enterprise Data Management Cloud 2022. 1z0-1086-22 exam covers a wide range of topics, including data governance, metadata management, data integration, and data quality, and requires candidates to answer multiple-choice questions and perform hands-on tasks to demonstrate their skills.


Oracle 1z0-1086-22 certification exam is a vendor-specific certification offered by Oracle. Oracle Enterprise Data Management Cloud 2022 Implementation Professional certification is recognized worldwide and demonstrates that a professional has the skills and knowledge required to implement Oracle Enterprise Data Management Cloud. Oracle Enterprise Data Management Cloud 2022 Implementation Professional certification is suitable for professionals who work as developers, administrators, or consultants in the Oracle ecosystem. Oracle Enterprise Data Management Cloud 2022 Implementation Professional certification can help professionals advance their careers and increase their earning potential.

 

NEW QUESTION # 29
In what order do you archive data chain objects?

  • A. Node type, hierarchy set, node set, viewpoint
  • B. Application, dimension, viewpoint
  • C. Viewpoint, node set, hierarchy set, node type
  • D. You can archive data chain objects in any order
  • E. Viewpoint, dimension, application

Answer: A

Explanation:
Explanation
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.
References: Archiving and Unarchiving Data Chain Objects - Oracle Help Center


NEW QUESTION # 30
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 hierarchy set
  • B. Account Mapping node set
  • C. Account Mapping dimension
  • D. A node type converter with the Account (GL) node type as source and Account Mapping (Planning) node type as target
  • E. Account Mapping viewpoint in the default Planning application view

Answer: A,B,D

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 # 31
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. The alternate viewpoint may be partially bound if it shares data chain objects with a bound viewpoint.
  • C. 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.
  • D. You cannot use the alternate viewpoint to construct a what-if scenario that is isolated from production.
  • E. 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.

Answer: B,C

Explanation:
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


NEW QUESTION # 32
You want to enforce the "four-eyes" principle for your approval policy. How can you do this?

  • A. Use any approval method and do not select "Include Submitter".
  • B. Use any approval method with at least three different approval groups.
  • C. Use a parallel approval method.
  • D. Use a serial approval method.

Answer: A

Explanation:
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


NEW QUESTION # 33
What are two scenarios where mapping nodes across applications are required7

  • A. When applications share common dimensions but use different granularity
  • B. When applications share an external connection
  • C. When applications share data but have different dimensions
  • D. When applications have common dimensions but use different prefixes or suffixes for member names

Answer: A,C

Explanation:
Explanation
Mapping nodes across applications are required when applications share data but have different dimensions or different granularity. For example, if a source application has a product dimension with four levels and a target application has a product dimension with three levels, you need to map the nodes from the source to the target to determine how the data will be aggregated or disaggregated. Similarly, if a source application has a monthly time dimension and a target application has a quarterly time dimension, you need to map the nodes from the source to the target to determine how the data will be summed or averaged. Mapping nodes across applications are not required when applications have common dimensions but usedifferent prefixes or suffixes for member names, because this can be handled by node type converters or property derivations. Mapping nodes across applications are not required when applications share an external connection, because this does not affect the dimensionality or granularity of the data. References: Creating Mapping Viewpoints - Oracle Help Center1; Working with Node Type Converters - Oracle Help Center


NEW QUESTION # 34
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 a single export for the target that contains all mappings for both sources.
  • B. You run three exports, one for each source and one for the target.
  • C. You run two separate exports, one for each source-to-target location.
  • D. You run four exports, one for each viewpoint involved in the mapping.

Answer: C

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. Reference: Working with Requests - Oracle Help Center3; Creating Mapping Viewpoints - Oracle Help Center2


NEW QUESTION # 35
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. By default, when you assign the Participant permission to a user or group, their data access is set to Write.
  • 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. The Owner permission on a view enables a user to configure the view and grants full access to the data objects in that view.

Answer: C

Explanation:
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


NEW QUESTION # 36
Which two statements are true about importing Planning dimensions?

  • A. An application adapter connects your instance to the Planning application outbox and finds dimension files that were exported from the source application.
  • B. You can connect to an external Planning application and import dimensions directly into your Enterprise Data Management Cloud instance.
  • C. For Planning dimensions, Enterprise Data Management Cloud supports importing from comma-delimited (.csv) or tab-delimited (.txt) files.
  • D. When you import data for multiple Planning dimensions from a local file, the file can contain data for all dimensions.

Answer: A,B


NEW QUESTION # 37
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?

  • A. 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.
  • B. Create a list viewpoint for cost centers, then add parents for departments and geography.
  • C. Create two node sets; one with a group of departments and another with a group of geographical regions.
  • D. Create one hierarchy set with different top nodes for departments and geography, and add shared cost center nodes as children.

Answer: A,D

Explanation:
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


NEW QUESTION # 38
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. 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.
  • B. 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.
  • C. 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.
  • D. 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.

Answer: B,C

Explanation:
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


NEW QUESTION # 39
You want to enforce the "four-eyes" principle for your approval policy. How can you do this?

  • A. Use any approval method and do not select "Include Submitter".
  • B. Use any approval method with at least three different approval groups.
  • C. Use a parallel approval method.
  • D. Use a serial approval method.

Answer: A

Explanation:
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


NEW QUESTION # 40
When you register an application, the system creates a default view that contains all your dimensions.
However, there may be situations where the default view is not enough and you need to create an alternate view and viewpoints.
Which three are situations where you create an alternate view and viewpoints?

  • A. You need to create a view to give users access to a limited set of data.
  • B. You need to give users access to the default view so that they have access to only one dimension.
  • C. You need an alternate view to share, compare, and map information across multiple applications.
  • D. You need to create a maintenance view with multiple viewpoints from different applications so you can maintain all your dimension information in one place.
  • E. You need to create a validation view with multiple viewpoints from different dimensions so you can maintain all your application information in one place.

Answer: A,C,E

Explanation:
* You need to create a validation view with multiple viewpoints from different dimensions so you can maintain all your application information in one place: This option is correct because a validation view is a type of view that allows you to create multiple viewpoints from different dimensions and validate them against each other. You can use a validation view to maintain all your application information in one place and check for any errors or inconsistencies.
* You need to create a view to give users access to a limited set of data: This option is correct because a view is a type of data chain object that defines the scope of data that users can access and work with.
You can create a view to give users access to a limited set of data by specifying the node sets and hierarchy sets that are included in the view.
* You need an alternate view to share, compare, and map information across multiple applications:
This option is correct because an alternate view is a typeof view that allows you to create multiple viewpoints from different applications and share, compare, and map information across them. You can use an alternate view to synchronize and govern data across registered applications.


NEW QUESTION # 41
Which EPM Automate command can you use to restart services on your instance?

  • A. resetService
  • B. recreateService
  • C. startService
  • D. restartService

Answer: D

Explanation:
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


NEW QUESTION # 42
What are two scenarios where mapping nodes across applications are required?

  • A. When applications share an external connection
  • B. When applications share common dimensions but use different granularity
  • C. When applications have common dimensions but use different prefixes or suffixes for member names
  • D. When applications share data but have different dimensions

Answer: C,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 # 43
Which are two reasons for creating a migration snapshot?

  • A. To restore the artifacts and data to the snapshot state
  • B. To export the enterprise data to an external application
  • C. To download the enterprise data locally for offline work
  • D. To migrate the enterprise data between different releases of the environment
  • E. To refresh the test environment from the production environment

Answer: A,E

Explanation:
According to the Oracle Help Center, migration snapshots are used to migrate application artifacts and data between environments, such as refreshing the test environment from the production environment. Migration snapshots can also be used to restore the artifacts and data to the snapshot state in case of any issues or errors. The other reasons are not valid for creating a migration snapshot.


NEW QUESTION # 44
The Owner permission for an application lets users perform which three tasks?

  • A. Assign permissions for an application's data objects to other users and groups.
  • B. Delete service administrators from an instance.
  • C. Manage an application's data objects.
  • D. Modify application registration.
  • E. Import viewpoints from external applications.

Answer: A,C,D

Explanation:
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. References: Working with Permissions - Oracle Help Center1; Registering Applications - Oracle Help Center


NEW QUESTION # 45
The Owner permission for an application lets users perform which three tasks?

  • A. Assign permissions for an application's data objects to other users and groups.
  • B. Delete service administrators from an instance.
  • C. Manage an application's data objects.
  • D. Modify application registration.
  • E. Import viewpoints from external applications.

Answer: A,C,D

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 # 46
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?

  • A. 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.
  • B. 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.
  • C. Create one bi-directional node type converter between the two applications.
  • D. 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.

Answer: B,D

Explanation:
Explanation
To share nodes between applications, you need to create node type converters and maintenance views. Node type converters enable you to transform properties or derive values from source node types to target node types when sharing data across applications. You need to 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. This way, you can share nodes in both directions. Maintenance views contain viewpoints from multiple applications that facilitate sharing data across applications. You need to create a maintenance view with viewpoints for both the General Ledger account dimension and the Planning account dimension. This way, you can create requests or subscriptions to share nodes between the two dimensions. You do not need to create one bi-directional node type converter or a node type converter for the Account node type in the General Ledger application that uses the Planning Account node type as a source. References: Working with Node Type Converters - Oracle Help Center1; Working with Maintenance Views - Oracle Help Center2


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

  • A. The approval policy applies to hierarchy sets but not node sets in the dimension.
  • B. The approval policy applies to only the dimension and does not apply to related data chain objects.
  • C. The approval policy applies to the node types and hierarchy sets in the dimension.
  • D. The approval policy cascades down to only the data chain objects specified in the policy definition.

Answer: C

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


NEW QUESTION # 48
A request has a status of "In Flight." In which stage of the approval workflow is the request?

  • A. Approve
  • B. Closed
  • C. Review
  • D. Submit

Answer: A

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


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

  • A. The approval policy applies to hierarchy sets but not node sets in the dimension.
  • B. The approval policy applies to only the dimension and does not apply to related data chain objects.
  • C. The approval policy applies to the node types and hierarchy sets in the dimension.
  • D. The approval policy cascades down to only the data chain objects specified in the policy definition.

Answer: C

Explanation:
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.
Reference:
https://docs.oracle.com/en/cloud/saas/enterprise-data-management-cloud/edmra/creating-approval-policies.html


NEW QUESTION # 50
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. Target nodes and converted source nodes in two separate hierarchies
  • D. Separate hierarchy sets for each source-to-target relationship

Answer: D

Explanation:
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


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

  • A. Inherited properties
  • B. Shared properties
  • C. Node properties
  • D. Hierarchy properties
  • E. Relationship properties

Answer: B,C,E

Explanation:
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


NEW QUESTION # 52
......

Study HIGH Quality 1z0-1086-22 Free Study Guides and Exams Tutorials: https://www.exams-boost.com/1z0-1086-22-valid-materials.html

Download Oracle 1z0-1086-22 Exam Dumps to Pass Exam Easily: https://drive.google.com/open?id=1ga9F-b7rDmovk85bjLiXotgE31q5Vtad