How should the Kubernetes manifests be modified to allow Kubernetes environment integration with Cisco ACI?

Question

Options

• AThe metadata section must contain the Cisco APIC management IP.
• BThe manifest does not have to be changed, but the Kubernetes object is not discovered by Cisco ACI if it is not defined in the manifest.
• CThe manifests must include ACI EPG reference.
• DNo change is needed to perform this action.

• A
  4% (1)
• B
  4% (1)
• C
  8% (2)
• D
  84% (21)

Explanation

Cisco ACI integrates with Kubernetes at the infrastructure and CNI (Container Network Interface) layer, not the manifest layer. The ACI CNI plugin, once installed and configured on the cluster, automatically discovers Kubernetes objects (pods, namespaces, deployments) and applies network policies without requiring any changes to individual manifests - making D correct.

Why the distractors fail:

• A is wrong because Kubernetes manifests never contain infrastructure management IPs like the APIC address; that configuration lives in the CNI plugin or cluster-level config, not in workload manifests.
• B is wrong on both counts: manifests don't need modification, and ACI does automatically discover Kubernetes objects once the CNI integration is active - discovery isn't gated on manifest content.
• C is wrong because EPG (End Point Group) assignment is handled automatically by the ACI CNI plugin (typically based on namespace mapping), not by embedding EPG references directly into manifests.

Memory tip: Think of ACI integration as plumbing installed beneath the floor - once the ACI CNI plugin is in place, everything above it (your manifests) works unchanged. If the question asks about manifest changes for ACI, the answer is almost always "none needed."

No community discussion yet for this question.