Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.
AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by Oracle
Exam Format
Registration
Validity
Skills this practice test covers
- Reconcile structures and resolve naming collisions during the first DRM data load.
- Build derived, inherited and lookup properties for downstream systems.
- Choose between imports, action scripts, blender and exports for a data feed.
- Pad or skip levels in balanced and recursive hierarchy feeds.
- Plan version composition, timing and status for what-if and planning versions.
- Secure nodes and properties with node access groups and property categories.
Explore related topics
1Z0-588 exam content
12 domains · 38 topics · 196 of 204 questions sorted by domain
Implementation Scope and Risks22 questions
This domain is about running a DRM project, not the software itself. Candidates scope the work, set timelines and phases, name the roles on the team, judge a customer's strengths and issues, and plan testing and rollout.
Skills tested
- Set the scope and timeline of a DRM implementation, and split it into phases.
- List common implementation risks and ways to reduce them.
- Assign implementation roles and responsibilities on the project team.
- Plan testing and rollout before users depend on DRM data.
Questions by topic
- Describe best practices for project scoping and establishing implementation timelines8
- Describe common implementation risks8
- Describe implementation roles and responsibilities6
DRM Overview26 questions
This domain covers the product's daily use. Candidates describe DRM's key features, architecture and user roles, then manage versions, hierarchies and nodes, run property queries, produce exports and reports, and read audit data.
Skills tested
- Describe the DRM architecture and the job of each user role.
- Create and manage versions, hierarchies and nodes.
- Find nodes with property queries and check changes in audit data.
- Produce exports and reports for other systems and users.
Questions by topic
- Describe the DRM Architecture3
- Manage hierarchies3
- Manage nodes10
- Use Audit Data4
- Manage versions1
- Manage property scoping1
- Use Property Queries4
Managing the Initial Data Load16 questions
The first load brings master data from several source systems into DRM. Candidates reconcile hierarchy structures from those sources, resolve naming collisions, and deal with duplicate nodes.
Skills tested
- Reconcile the structures of hierarchies that arrive from different sources.
- Resolve naming collisions when two sources use one name for different members.
- Find and handle duplicate nodes before users rely on the data.
Questions by topic
- Manage naming collisions7
- Perform structural reconciliation9
Managing Properties and Property Categories22 questions
Properties hold the attributes that each system needs for a node. Candidates manage properties from upstream and downstream systems, defaults, calculated properties, property scoping, node types and property categories, and load properties with the structure.
Skills tested
- Set property defaults and decide when a value should be calculated.
- Build derived, inherited and lookup properties.
- Manage node types and property scoping.
- Group properties into property categories for display and security.
Questions by topic
- Manage calculated properties (derived, inherited, lookup)5
- Manage property scoping2
- Manage property defaults9
- Manage properties from upstream and downstream systems6
Alternate Hierarchies11 questions
Alternate hierarchies arrange existing nodes in another structure. Candidates define and build them by hand, from attributes and from an export, and decide where they may differ from the main hierarchy and where they must stay consistent.
Skills tested
- Define and build an alternate hierarchy from existing nodes.
- Build an alternate hierarchy from attributes and from an export.
- Decide when to allow differences and when to force consistency.
Questions by topic
- Support differences or force consistency3
- Build alternate hierarchies from attributes and an export4
- Define and build alternate hierarchies4
Mappings6 questions
Mappings link a member in one system to members in another. Candidates manage one to one and one to many mappings with properties or with hierarchies, and handle complex many to many mappings.
Skills tested
- Map one member to one or many members with a property.
- Build mappings with a hierarchy instead of a property.
- Handle many to many mappings between two systems.
Questions by topic
- Manage complex many to many mappings3
- Manage basic one to one or one to many mappings using properties3
Managing Data Feeds25 questions
This domain has the most objectives. It covers how DRM receives and sends master data: upstream and downstream systems, interfaces, feed timing and file formats, and the tools that move data. It ends with level padding, ETL mapping tables and automated feeds.
Skills tested
- Identify upstream and downstream systems and the interfaces between them.
- Choose imports, action scripts, blender or exports for each data movement.
- Pad or skip levels when a feed needs a balanced or recursive hierarchy.
- Generate mapping tables for the ETL processes of downstream systems.
- Automate data feeds and reconcile them with their sources and targets.
Questions by topic
- Describe Imports, Action Scripts, Blender, and Exports9
- Include skipping and padding levels in balance or recursive hierarchy feeds8
- Implement automated data feed(s)8
Versioning24 questions
DRM keeps its data in versions. Candidates decide what each version holds, when versions are created, how version status is used, and how to keep what-if and planning versions in step with the main data.
Skills tested
- Plan the composition and timing of versions.
- Use version status to control when a version can still change.
- Synchronize what-if and planning versions with the main version.
Questions by topic
- Manage synch methodology for what/if and planning versions9
- Manage version timings6
- Manage usage of version status6
- Manage versions3
Business Rules20 questions
Business rules keep master data valid for the systems that use it. Candidates manage rules for downstream system needs, for client processes and for known system issues.
Skills tested
- Turn a downstream system's requirements into DRM business rules.
- Add rules that support a client's own processes.
- Use rules to catch known system issues before data is sent.
Questions by topic
- Manage business rules for client processes5
- Manage business rules to address system issues8
- Manage business rules for downstream systems7
Users6 questions
This domain controls who can see and change master data. Candidates manage users and roles, node access groups and property categories, node access for each user, and anonymous access.
Skills tested
- Create users and assign roles to them.
- Grant node access through node access groups.
- Limit property access with property categories.
- Set up anonymous access where a project needs it.
Questions by topic
- Manage node access groups and property categories3
- Manage node access for users3
Workflow8 questions
Workflow is optional in a DRM project. Candidates decide whether it is needed, gather its requirements, and integrate it through the request API.
Skills tested
- Decide whether a project needs workflow and list its requirements.
- Integrate a workflow through the request API.
Questions by topic
- Integrate workflow through the request API2
- Evaluate if workflow is needed and determine workflow requirements6
API Integration10 questions
The last domain connects DRM to other programs. Candidates evaluate what an API integration must do, then integrate through the public API.
Skills tested
- Evaluate the requirements for an API integration.
- Integrate another application through the public API.
Questions by topic
- Integrate through the public API5
- Evaluate API integration requirements4
- Integrate workflow through the request API1
Requirements
- No formal prerequisites: passing this exam alone earns the credential.
- Recommended: Oracle's optional course, Oracle Data Relationship Management 11.1.2 Administration.
- Recommended: a grasp of master data management and of the systems that send and receive the data.
About the 1Z0-588 exam
Oracle built 1Z0-588 for implementation consultants on Oracle Hyperion Data Relationship Management (DRM), its master data management product. DRM keeps hierarchies, nodes and properties consistent across the transactional and analytical systems that share them. The exam follows a DRM project from scoping and the first data load through properties, mappings, data feeds, versions, security and integration. Oracle aims it at Oracle PartnerNetwork (OPN) members, though it is open to all candidates.
The PlanetCert practice test spreads its questions across all twelve domains, with the most on DRM Overview, Managing Data Feeds and Versioning. Explanations help where DRM terms sit close together, such as a derived property and an inherited one, or blender and action scripts. Study Mode suits Managing Data Feeds, where imports, action scripts, blender and exports each move data in a different way. Brainy AI Assistant can explain how a recursive hierarchy feed differs from a balanced one, or when to force consistency in an alternate hierarchy.
How to earn the certification
- Earns
- Oracle Hyperion Data Relationship Management Certified Implementation SpecialistSpecialist
How to prepare for 1Z0-588
- 1
Read the outline as a project plan
The twelve domains follow a DRM implementation in order, from scoping to integration. Study them in that order, so each step builds on the one before.
- 2
Load two hierarchies that overlap
Where a DRM environment is available, import two small hierarchies that share some members. Reconcile their structures, and resolve the naming collisions and duplicate nodes that appear.
- 3
Write one property of each kind
Create a derived, an inherited and a lookup property, then group them in a property category. Check how each value changes when a parent node moves.
- 4
Trace a feed from end to end
Pick one downstream system and plan its feed: interface, timing, file format and any padding of levels. Then decide which DRM tool, such as an export, carries each step.
- 5
Drill the twelve domains
Work through the 1Z0-588 practice test domain by domain in Study Mode, then take a full run in Timed Mode. Ask Brainy AI Assistant about any versioning or feed question that went wrong.
Start a timed 1Z0-588run
Oracle lists Oracle Data Relationship Management 11.1.2 Administration as optional preparation. Partners can also follow the Oracle Hyperion Data Relationship Management Implementation guided learning path.
Who 1Z0-588 is for
- Implementation consultants at Oracle partners who deliver DRM projects.
- DRM administrators who maintain hierarchies, properties and mappings.
- Enterprise performance management (EPM) consultants who connect DRM to other systems.
Typical job titles: DRM consultant · Master data management consultant · EPM consultant · DRM administrator · Data governance analyst
1Z0-588 glossary
17 terms from the exam objectives and the vendor's official material, each defined in a sentence.
- Action Scripts
- A DRM feature that applies a batch of actions, such as adding nodes or changing property values, in one run.
- Alternate hierarchies
- Extra hierarchies that arrange the same nodes in a different structure, for example for another report.
- Audit Data
- The record DRM keeps of changes, such as who changed a node or a property value and when.
- Blender
- A DRM tool that combines hierarchies, nodes and property values from one version into another version.
- Derived properties
- Properties whose values DRM calculates, for example with a formula, instead of storing a value a user typed.
- Exports
- Outputs that write hierarchy and property data from DRM to a file or a table for another system.
- Inherited properties
- Properties whose values pass down from an ancestor node unless a node overrides them.
- Lookup properties
- Properties that return a value from a lookup table, based on the value of another property.
- Master Data Management
- Keeping shared reference data, such as charts of accounts and organization structures, the same in every system that uses it.
- Naming collisions
- Cases where two source systems use the same name for different members, so one must be renamed or told apart.
- Node access groups
- Groups that give their users a set level of access, such as read or edit, to chosen nodes and their descendants.
- Node types
- Classes of nodes that let DRM show different properties and apply different rules to each kind of node.
- Property categories
- Named groups of properties that organize how they are shown and control which users can view or edit them.
- Property Queries
- Searches that find nodes whose property values match set criteria, in a hierarchy or a whole version.
- Recursive hierarchy
- A hierarchy written as parent and child pairs, one row per relationship, instead of one column per level.
- Structural reconciliation
- Aligning hierarchy structures that come from different source systems so that they fit one model in DRM.
- Version status
- The state of a DRM version, such as working or finalized, which controls whether its data can still change.