When deleting records created by child business units in Enterprise 2.0, which MID should be used in the request?

When deleting records created by child business units in Enterprise 2.0, which MID should be used in the request?

• A. The parent account MID
• B. The child business unit MID
• C. The ClientID of the parent organization
• D. The root account MID

Answer: (B)

In Enterprise 2.0, each business unit has its own MID that defines the scope of data and actions for that unit. When you need to delete records created by a child business unit, you must target the request to that specific unit by using the child BU’s MID. This ensures the operation applies to the correct data and respects the unit’s permissions. Using the parent MID would hit the parent’s data rather than the child’s, and the root MID isn’t appropriate for BU-scoped operations. The ClientID of the parent organization isn’t the identifier used to scope data in this context. Therefore, the child business unit MID is the correct one to use.

In Enterprise 2.0, each business unit has its own MID that defines the scope of data and actions for that unit. When you need to delete records created by a child business unit, you must target the request to that specific unit by using the child BU’s MID. This ensures the operation applies to the correct data and respects the unit’s permissions. Using the parent MID would hit the parent’s data rather than the child’s, and the root MID isn’t appropriate for BU-scoped operations. The ClientID of the parent organization isn’t the identifier used to scope data in this context. Therefore, the child business unit MID is the correct one to use.