Which method does Cisco DNA Center use to allow management of non-Cisco devices through southbound protocols?

Question

Options

• AIt creates device packs through the use of an SDK
• BIt uses an API call to interrogate the devices and register the returned data.
• CIt obtains MIBs from each vendor that details the APIs available.
• DIt imports available APIs for the non-Cisco device in a CSV format.

• A
  90% (55)
• B
  2% (1)
• C
  3% (2)
• D
  5% (3)

Explanation

Cisco DNA Center and Non-Cisco Device Management

Cisco DNA Center uses device packages (packs) built through a Software Development Kit (SDK) to extend its management capabilities to non-Cisco devices via southbound protocols. These device packs act as translators or plugins, allowing DNA Center to communicate with third-party hardware using that vendor's specific protocols and data models, effectively bridging compatibility gaps.

Why the distractors are wrong:

• Option B is incorrect because simply making an API call to interrogate and register devices is not a structured method for ongoing southbound protocol management - it describes a basic discovery function, not a management integration framework.
• Option C is incorrect because MIBs (Management Information Bases) are associated with SNMP, and DNA Center's southbound integration doesn't rely on vendors supplying MIBs to define API availability.
• Option D is incorrect because importing APIs via CSV is not a recognized or valid method within DNA Center's architecture - CSV files are used for data imports like inventory, not API integration.

Memory Tip: Think of device packs as "translator apps" you install on DNA Center - just like downloading an app to make your phone work with a new smart device. SDK → Device Pack → Non-Cisco compatibility. Remember: "SDK = Special Device Knowledge" for third-party management.

No community discussion yet for this question.