Which OCI construct is recommended to isolate FDI instance types?

Which OCI construct is recommended to isolate FDI instance types?

• A. Schemas
• B. Tablespaces
• C. Compartments
• D. Users

Answer: (C)

Compartments are the OCI construct used to separate and govern resources across your tenancy. They create isolated boundaries for groups of OCI resources, so you can apply distinct access controls, budgets, and lifecycles to different FDI instance types. This is ideal because FDI instance types are cloud resources, not data elements inside a database. Schemas, tablespaces, and users are all database-level constructs. They organize or secure objects and data within a single database, but they don’t provide isolation across different FDI instance types or OCI resource boundaries. So they can’t offer the kind of cross-resource separation that compartments provide.

Compartments are the OCI construct used to separate and govern resources across your tenancy. They create isolated boundaries for groups of OCI resources, so you can apply distinct access controls, budgets, and lifecycles to different FDI instance types. This is ideal because FDI instance types are cloud resources, not data elements inside a database.

Schemas, tablespaces, and users are all database-level constructs. They organize or secure objects and data within a single database, but they don’t provide isolation across different FDI instance types or OCI resource boundaries. So they can’t offer the kind of cross-resource separation that compartments provide.