What is the recommended approach to organizing OCI compartments when you have multiple FDI instances, such as test and production?

• A. Use a single compartment for all instances
• B. Create separate compartments for each FDI instance type
• C. Use compartments by region
• D. Do not use compartments

Answer: (B)

Organizational boundaries in OCI are about isolating resources and controlling who can do what. When you have multiple FDI instances, such as test and production, creating separate compartments for each environment gives you clear, enforced separation between them. This lets you apply different IAM policies, budgets, and security controls to each environment, so developers or operators can access only the appropriate compartment. It also makes governance, auditing, and cost tracking per environment straightforward, and it reduces the risk of accidentally impacting production when working in test.

Using a single compartment for all instances would blur those boundaries, making it harder to enforce least-privilege access and separate cost and audit trails. Organizing by region isn’t aligned with environment separation, and not using compartments at all removes the isolation that guards production systems.