Which Cisco ACI policy binds the VMM domain with specific leaf interfaces?

Question

Options

• AInterface profile
• BSwitch pokey
• CvSwitch policy
• Dattachable access entity pokey

• A
  2% (1)
• B
  2% (1)
• C
  87% (39)
• D
  9% (4)

Explanation

vSwitch policy is correct because, in Cisco ACI's VMM integration, the vSwitch policy is the construct that ties the VMM domain to specific leaf switch interfaces, governing how virtual switches (e.g., VMware DVS) communicate with the physical ACI fabric - including settings like CDP/LLDP, NetFlow, and port channel modes that apply at those leaf ports.

Option A (Interface profile) is wrong because an interface profile groups interface selectors and maps to switch profiles, but it does not itself bind a VMM domain - it's a lower-level physical port grouping construct.

Option B (Switch policy) - likely "Switch policy" - is wrong because switch-level policies govern things like spanning tree or MCP at the node level, not VMM domain binding.

Option D (Attachable Access Entity Profile / AAEP) is the most tempting distractor: the AAEP does link domains (including VMM domains) to interface policy groups, but it acts as the bridge to all domain types - the vSwitch policy is specific to how the VMM domain binds behavior at leaf interfaces.

Memory tip: Think "VMM = VSwitch policy" - the v in vSwitch matches the v in VMM. It's the VMM-specific policy, whereas AAEP is the general-purpose domain-to-interface glue.

No community discussion yet for this question.