How is Exadata Secure RDMA Fabric isolation used in X9M-2 with virtualization enabled?

Question

Options

• AWith Secure Fabric isolation, each Storage Server runs multiple KVM guests each dedicated to a
• BWith Secure Fabric isolation, each Database VM Guest uses a dedicated network partition and
• CWith Secure Fabric isolation, each Database VM Cluster uses a dedicated network partition and
• DWith Secure Fabric isolation, each Database VM cluster uses a dedicated network partition and

• A
  3% (2)
• B
  13% (8)
• C
  8% (5)
• D
  75% (46)

Explanation

Option D correctly identifies that Secure RDMA Fabric isolation in Exadata X9M-2 operates at the Database VM cluster level - each cluster receives a dedicated network partition (carving out its own slice of the RDMA fabric) along with dedicated storage server resources, ensuring complete isolation between tenants sharing the same physical Exadata system.

Why the distractors fail:

• A is wrong because Secure Fabric isolation is a database-side construct, not a storage server virtualization model - storage servers don't run KVM guests per tenant.
• B is wrong in granularity: isolation is enforced per cluster, not per individual VM guest. Multiple guests within the same cluster share the same partition.
• C is extremely close to D but contains a subtle wording error in how the isolation scope or resource dedication is described after "dedicated network partition and" - D matches Oracle's documented architecture precisely.

Memory tip: Think "cluster = fence." Just as a security perimeter surrounds a campus (cluster), not each individual building (guest), Secure RDMA Fabric isolation draws a boundary around the entire Database VM cluster, not individual VMs. If an answer puts the boundary at the wrong level (guest or storage server), eliminate it.

No community discussion yet for this question.