Which two items are types of application isolation options available when Kubernetes is deployed with the ACI CNI plug-in? (Choose two.)

Question

Options

• AVM isolation
• BCluster Isolation
• CServer Isolation
• DProcess Isolation
• ENamespace Isolation

• A
  3% (1)
• B
  90% (26)
• C
  3% (1)
• D
  3% (1)

Explanation

When Kubernetes is deployed with the Cisco ACI CNI plug-in, it supports Cluster Isolation and Namespace Isolation as its two application isolation models. Cluster Isolation treats the entire Kubernetes cluster as an isolated network boundary within ACI, while Namespace Isolation maps Kubernetes namespaces to ACI Endpoint Groups (EPGs), enforcing network policy at the namespace level.

The distractors are wrong because: VM Isolation (A) is not a CNI-layer concept - VM-level separation happens at the hypervisor/infrastructure layer, not through the ACI CNI plug-in. Server Isolation (C) is not a defined isolation construct in Kubernetes or ACI networking. Process Isolation (D) is an OS/container runtime concept (think cgroups/namespaces at the kernel level), not an ACI CNI feature.

Memory tip: Think "C and N" - Cluster and Namespace are the two logical scopes Kubernetes already understands natively, so it makes sense that the ACI CNI plug-in maps its isolation to those same boundaries.

No community discussion yet for this question.