nerdexam
Oracle

1Z0-1072-20 · Question #234

You have compartments C and D under the root compartment in your Oracle Cloud Infrastructure (OCI) tenancy; compartment C contains a sub-compartment also named D. You are trying to move this…

The correct answer is C. Both parent and child compartments cannot have the same name. https://docs.cloud.oracle.com/en-us/iaas/Content/Identity/Tasks/managingcompartments.htm (restriction on moving compartments)

Implement OCI Identity and Access Management

Question

You have compartments C and D under the root compartment in your Oracle Cloud Infrastructure (OCI) tenancy; compartment C contains a sub-compartment also named D. You are trying to move this sub-compartment D to the parent compartment D like shown in the picture, but the move fails. What is the reason for this error?

Options

  • AYou need to move all the compartments in the hierarchy to the new parent compartment.
  • BYou cannot move a subcompartment to another parent compartment.
  • CBoth parent and child compartments cannot have the same name.
  • DSub-compartment D needs to be empty before it can be moved.

How the community answered

(21 responses)
  • A
    14% (3)
  • B
    10% (2)
  • C
    71% (15)
  • D
    5% (1)

Explanation

https://docs.cloud.oracle.com/en-us/iaas/Content/Identity/Tasks/managingcompartments.htm (restriction on moving compartments)

Topics

#compartments#compartment naming#compartment hierarchy

Community Discussion

4
Dervla O.Dervla O.Dec 11, 2025

The correct answer is C. OCI enforces the rule that within a given parent compartment, no two direct children can share the same name, so if the destination compartment D already exists at that level, the move is blocked because it would create a naming collision.

15
Grace U.Grace U.Nov 27, 2025

I picked D, but seeing two D's made C click.

3
Ingrid P.Ingrid P.Dec 2, 2025

C is right, and this is a card-worthy rule: OCI enforces unique names among sibling compartments within the same parent, so once you move sub-compartment D under parent compartment D, you would have two siblings named D at that level, which the system rejects outright. The rename-before-move workaround is the clean fix here, and the name uniqueness constraint applies at each level of the hierarchy, not globally across the tenancy.

3
Toby R.Toby R.Nov 14, 2025

D is the trap here because OCI does require compartments to be empty to delete them, so your brain wants to go there, but the actual blocker is C, names within the same parent have to be unique and you already have a D sitting directly under root. The exam was pretty direct about this rule, no tricks in the scenario itself.

0
Full 1Z0-1072-20 Practice