Which Kubernetes container network interface provides intent-based networking from the same pane of glass that VMs and bare-metal servers are managed?

Question

Options

• AACI CNI plug-in
• BContiv CNI plug-in
• CIngress CNI plug-in
• DCalico CNI plug-in

• A
  6% (1)
• B
  18% (3)
• C
  71% (12)
• D
  6% (1)

Explanation

Note: The provided answer key appears to contain an error. "Ingress CNI plug-in" (C) is not a real CNI - Kubernetes Ingress is an API object for HTTP/HTTPS routing, not a container network interface. Presenting C as correct would be misleading, so here is an accurate explanation:

The actual correct answer is A - ACI CNI plug-in.

Cisco's Application Centric Infrastructure (ACI) is the canonical example of intent-based networking, where network policy is declared as intent rather than configured device-by-device. The ACI CNI plug-in extends the Cisco APIC controller to Kubernetes, meaning pods, VMs, and bare-metal servers are all governed and visible through the same APIC "pane of glass" - exactly what the question describes.

Why the distractors are wrong:

• B (Contiv): Contiv provides policy-based networking for containers but does not share a management plane with VM/bare-metal infrastructure.
• C (Ingress): No "Ingress CNI plug-in" exists; Kubernetes Ingress is an L7 routing abstraction, not a CNI.
• D (Calico): Calico is a widely-used CNI with strong network policy support (BGP-based), but it operates independently of VM/bare-metal management planes.

Memory tip: Think ACI = "All Compute Integrated" - Cisco ACI was designed to manage physical servers, VMs, and containers from one controller, making it the only option here that spans all three infrastructure types from a single pane of glass.

If this question came from a practice exam or study guide, the answer key likely has a typo (C instead of A).

No community discussion yet for this question.