In the Cisco APIC, how are fabric-wide unique identifiers managed?

The correct answer is A. dme. DME (Data Management Engine) is the correct answer because it is the internal APIC process responsible for managing the MIT (Management Information Tree) object model and allocating fabric-wide unique identifiers - such as VXLAN segment IDs, VLAN encapsulations, and policy…

ACI Fabric Components and Operation

Question

In the Cisco APIC, how are fabric-wide unique identifiers managed?

Options

Adme
Bcoop
Celtmc
Dldmgr

How the community answered

(41 responses)

A
90% (37)
B
2% (1)
C
5% (2)
D
2% (1)

Explanation

DME (Data Management Engine) is the correct answer because it is the internal APIC process responsible for managing the MIT (Management Information Tree) object model and allocating fabric-wide unique identifiers - such as VXLAN segment IDs, VLAN encapsulations, and policy object IDs - ensuring no collisions occur across the entire ACI fabric.

COOP (Council of Oracles Protocol) is wrong; it runs on spine switches and distributes endpoint-to-location mappings (IP/MAC to VTEP), not unique identifier management. ELTMC (Endpoint Learning and Tracking Manager Controller) handles endpoint tracking and learning state - a different function entirely. LDMGR relates to local directory management functions, not fabric-wide ID allocation.

Memory tip: Think "DME = Data Management Engine = the keeper of IDs." Just as a DMV (Department of Motor Vehicles) issues unique license plate numbers, the DME issues unique fabric identifiers - both are central registries preventing duplicates.

Topics

#Data Management Engine#Fabric Identifiers#APIC Components#Management Architecture

Community Discussion

No community discussion yet for this question.

Full 500-601 Practice