XYZ Corp. has acquired ABC Corp. XYZ operates with Multi-Org Access Control. Consequently XYZ Corp. needs to add additional Operating Units. Identify the statement that describes the sequence for…

Question

Options

• AIt is not possible to add additional Operating Units.
• BSet the MO: Operating Unit profile option, run the Replicate Seed Data concurrent request, create
• CSet the MO: Security Profile profile option, run the Replicate Seed Data concurrent request, create
• DCreate the Operating Unit, run the Replicate Seed Data concurrent request, create new responsibilities
• ECreate the Operating Unit, run the Replicate Seed Data concurrent request, assign the Operating

• A
  3% (1)
• B
  3% (1)
• E
  95% (35)

Explanation

Option E correctly reflects the MOAC (Multi-Org Access Control) workflow: you first Create the Operating Unit, then run Replicate Seed Data to seed the new OU with the required transactional data and setups, and finally assign it to the existing Security Profile - allowing existing responsibilities to access the new OU without creating new ones. This is the defining advantage of MOAC over single-org setups.

Why the distractors fail:

• A is simply false - MOAC is specifically designed to scale with acquisitions like this.
• B confuses MOAC with single-org setup; MO: Operating Unit is a single-OU profile option, not used in a MOAC environment.
• C has the sequence backwards - you must create the OU before you can configure the Security Profile to include it.
• D describes the legacy single-org approach where each OU requires its own responsibility; MOAC eliminates this need by using Security Profiles instead.

Memory tip: Think of MOAC as "Create, Seed, Assign" - you build the OU, replicate the data it needs to function, then plug it into the Security Profile. If an answer mentions creating new responsibilities per OU, it's describing the old single-org model, not MOAC.

No community discussion yet for this question.