1D0-1086-26-D Sample Questions & Answers
Questions span administering Enterprise Data Management Cloud through user and permission provisioning, the biggest chunk, plus registering applications, the information model, change requests, alternate views, data sharing, mapping, synchronization, and governance.
Launch the full 1D0-1086-26-D simulator →Showing 6 of 12 free samples.
- Question 1Advanced
Changing Enterprise Data with Requests · Match and merge request items
A global manufacturing conglomerate is consolidating regional chart of accounts structures into Oracle Enterprise Data Management Cloud. During a large-scale integration cycle, the metadata team imports thousands of prospective cost center nodes from an external procurement subsystem using request files containing Add actions.
The implementation team configures matching rules to evaluate these incoming Add request items against existing cost centers in the corporate viewpoint. The Match Workbench identifies several candidate matches where incoming cost center names match existing master nodes with slight variations in local descriptions.
The data stewards evaluate the candidates, accept the matches, and apply property updates. The request successfully passes validation, progresses through governance approvals, and is completed and closed. Two days later, a finance manager discovers that an incoming cost center was mistakenly matched to an existing corporate cost center that represented a completely different business unit.
How must the administrator reverse this incorrect match and clear the stored match metadata in Oracle Enterprise Data Management Cloud?
flowchart TD A[Incoming Add Request Item] --> B[Match Workbench Evaluates Rules] B --> C[Candidate Match Accepted] C --> D[Request Approved & Completed] D --> E[Stored Match Metadata Persisted] E -.->|How to reverse after closure?| F{Resolution}Show answer & explanation
Correct answer: C
Once a request containing applied matches is completed and closed, the match metadata is permanently saved to the target node for that data source. EDM does not allow closed requests to be recalled, edited, or rolled back through the workbench. To purge the stored match relationship so future feeds do not automatically merge into this node, the administrator must delete the target node in a new request and re-add it.
- Question 2Intermediate
Changing Enterprise Data with Requests · Match and merge request items
An enterprise data steward processes an interactive request that matches and merges newly added legal entity records from an external ERP feed into an existing EDM hierarchy. The steward accepts the matches and submits the request, which is approved and closed. What occurs when subsequent request items with Add actions arrive from the same ERP data source referencing those same entity identifiers?
Show answer & explanation
Correct answer: A
In Oracle Enterprise Data Management Cloud, when a request containing applied matches is completed and closed, the match is committed and saved for that data source. Any subsequent incoming request items from that data source referencing those keys merge automatically into the target nodes without requiring manual user intervention in the Match Workbench.
- Question 3Intermediate
Creating Alternate Views and Viewpoints · Deduplicate and merge viewpoints
A master data analyst needs to deduplicate vendor nodes within a shared viewpoint following a corporate acquisition. The analyst wants to run deduplication in batches based on specific criteria. What is a key technical requirement when utilizing Cluster Key mode for viewpoint deduplication compared to Time-Based mode?
Show answer & explanation
Correct answer: B
When deduplicating viewpoints in EDM, Cluster Key mode requires selecting a clustering property defined on the node type that has an Allowed Values list configured. This enables administrators to segment source candidates into distinct clusters based on permitted values. In contrast, Time-Based deduplication evaluates nodes created on or after a specified date without requiring a clustering property.
- Question 4AdvancedSelect 2
Creating Alternate Views and Viewpoints · Deduplicate and merge viewpoints
A data governance team is preparing to execute viewpoint deduplication across multiple regional business units in Oracle Enterprise Data Management Cloud. Which TWO operational constraints and behaviors apply when running deduplication requests? (Select TWO)
Show answer & explanation
Correct answers: A, E
During deduplication comparison, property differences between the source candidate and the target surviving node are clearly marked with a Not Equal (≠) sign to alert stewards to potential property overwrites or survivorship conflicts.
EDM enforces concurrency controls on deduplication: nodes of a given node type can be processed in only one active deduplication request at a time.
- Question 5Intermediate
Creating Alternate Views and Viewpoints · Deduplicate and merge viewpoints
An administrator configures a viewpoint deduplication process using Cluster Key mode, selecting a custom property Vendor.Region whose allowed values include NorthAmerica, EMEA, and APAC. When the administrator runs deduplication selecting NorthAmerica as the cluster key filter, how does EDM evaluate potential duplicates?
Show answer & explanation
Correct answer: A
In Oracle Enterprise Data Management Cloud, the cluster key filter restricts only the source candidates evaluated for potential duplicates. EDM evaluates those source candidates against potential matching target nodes across the entire viewpoint, ensuring duplicates are identified even if the target node has a different or unassigned cluster key value.
- Question 6Advanced
Configuring Validations and Constraints · Configure validations and constraints (including external custom validations introduced in 2026)
An enterprise architect is designing a real-time compliance check in Oracle Enterprise Data Management Cloud that verifies whether newly created Cost Center nodes exist and are active in an external SAP ERP system prior to request approval. Which architectural configuration is required to implement an External Custom Validation for this requirement?
Show answer & explanation
Correct answer: D
External Custom Validations can only be configured on node types (not on applications, dimensions, or hierarchy sets). They require a Global Connection set specifically to the External Validation type. During validation execution, EDM issues an HTTP POST request with an application/json payload (including requestId, applicationId, validationId, validationKey, data, and nodes) using HTTP Basic Authentication.
sequenceDiagram participant EDM as EDM Request Engine participant GC as Global Connection (External Validation) participant EXT as External ERP Endpoint EDM->>GC: Trigger Node Type External Validation GC->>EXT: HTTP POST (JSON Payload) EXT-->>GC: Return Issues / Status JSON GC-->>EDM: Render Severity & Messages
Ready for the real thing?
The full 1D0-1086-26-D simulator has every exam-style question, timed mode, and instant scoring.