Refer to the exhibit. Which action does the execution of this ACI Cobra Python code perform? ``python mo_dir = cobra.mit.access.MoDirectory(cobra.mit.session.LoginSession(apic_url, username…

Question

mo_dir = cobra.mit.access.MoDirectory(cobra.mit.session.LoginSession(apic_url, username, password))
mo_dir.login()
eq = cobra.mit.access.ClassQuery('fvCEp')
eq.subtree = 'full'
objList = mo_dir.query(eq)
for mo in objList:
 print 'mac: %s ip: %s' % (mo.mac + " " + mo.ip)

Options

• AIt prints all LLDP neighbor MAC and IP addresses.
• BIt prints all Cisco Discovery Protocol neighbor MAC and IP addresses.
• CIt prints all endpoint MAC and IP addresses.
• DIt prints all APIC MAC and IP addresses.

• A
  9% (4)
• B
  2% (1)
• C
  76% (35)
• D
  13% (6)

Explanation

Option C is correct because the code queries the ACI class fvCEp (fabric virtual Client Endpoint), which is the ACI managed object class that represents learned endpoints - the actual workloads (VMs, servers, containers) connected to the fabric. The loop then explicitly prints mo.mac and mo.ip, confirming it outputs endpoint MAC and IP pairs.

Options A and B are wrong because LLDP and CDP neighbor information lives in different ACI classes (lldpAdjEp and cdpAdjEp respectively) - protocol neighbor tables are infrastructure-layer data, not endpoint data. Option D is wrong because APIC controller information is stored in management-related classes (e.g., infraCont), not fvCEp.

Memory tip: Break down fvCEp - fv = fabric virtual (ACI's overlay), C = Client, Ep = Endpoint. "Client Endpoint" = workloads talking to the fabric, not the fabric devices themselves. If you see fvCEp in Cobra code, think "VM/server endpoints," not switches or controllers.

No community discussion yet for this question.