1Z0-1046-20 · Question #106
As an Oracle Global Human Resources Cloud implementation consultant, you are configuring an enterprise structure for an organization that has undergone major restructuring. The client wants you to…
The correct answer is C. Configure multiple enterprise structures by using the Establish Enterprise Structure guided flow. Explanation/Reference:
Question
As an Oracle Global Human Resources Cloud implementation consultant, you are configuring an enterprise structure for an organization that has undergone major restructuring. The client wants you to make multiple versions of the enterprise structure so that they can decide on a final one that suits them based on proper analysis and comparison. What should you do to meet this requirement of the client?
Options
- ADesign the enterprise structure by using individual tasks available for each of the organizations and
- BCreate and load one enterprise structure at a time through Establish Enterprise Structure, analyze the
- CConfigure multiple enterprise structures by using the Establish Enterprise Structure guided flow.
- DConfigure multiple enterprise structures and load all of them simultaneously so that analysis and
How the community answered
(51 responses)- A6% (3)
- B4% (2)
- C73% (37)
- D18% (9)
Explanation
Explanation/Reference:
Topics
Community Discussion
7C is your answer here, and the reasoning is straightforward once you know how Oracle HCM handles this scenario. The Establish Enterprise Structure guided flow is specifically designed to let you create and save multiple draft configurations of an enterprise structure without committing any of them to the live system, so the client can review each version side by side and make an informed decision. Option B sounds close but it implies loading one structure at a time into the actual system, which means you are making real changes before the client has finished comparing, and that defeats the whole purpose of doing a proper analysis. Option A using individual tasks gives you no version management at all, just a piecemeal setup that gets messy fast when a client wants to backtrack and try a different org design. If this question trips you up on the real exam it is usually because people confuse "guided flow with multiple drafts" with "loading structures one at a time," so lock in the distinction that the guided flow keeps versions in a holding state until a final one is selected and activated.
The draft comparison piece is solid, but worth noting that even after you select and activate a final draft you still cannot undo the legal entity and business unit assignments without a significant rework effort, so clients should treat that activation step as nearly irreversible in practice.
Honestly my first instinct was B because that workflow of load one, analyze, then move on sounds like how I was taught to approach implementations in a linear way. But then I stopped and thought about what the question is actually asking, which is the client wants to compare multiple versions side by side before committing. That is exactly what the Establish Enterprise Structure guided flow is built for, it lets you create and save multiple configurations so the client can do a real apples-to-apples comparison without having to tear down and rebuild each time. D sounds tempting too but loading them all simultaneously is not how the tool works, so C is the only one that actually matches the functionality.
Your instinct on C is solid, and the key detail that seals it is that "Establish Enterprise Structure" specifically preserves each configuration as a named snapshot, which is the only way the client can revisit version 1 after building version 3 without reconstructing it from memory.
Thought B was right since you load one at a time, but Establish Enterprise Structure lets you save multiple draft configurations for comparison, so C it is.
Good catch on the multi-draft part, but worth noting that saving drafts for comparison is a separate step from actually committing the configuration, so if the exam question specifies a finalized deployment scenario you might still see B as a distractor designed to catch people who confuse draft-save with single-load workflows.
C is right, the guided flow lets you save multiple draft structures side by side.