Which of the following items are typical application scenarios of lMaster NCE service open and programmable? (Multiple choice)

Question

Options

• AThe southbound supports device connection with NETCONF and STelnet protocols.
• BCross-vendor device management and quick connection with third-party devices
• CUser-defined network services and rapid delivery of services based on the Web
• DiMaster NCE automatically generates a northbound RESTful interface

• A
  71% (47)
• C
  29% (19)

Explanation

A, B, and D are correct because they each describe concrete "open and programmable" capabilities of iMaster NCE: (A) the southbound interface natively supports NETCONF and STelnet protocols for device connectivity, enabling open southbound communication; (B) cross-vendor management and third-party device integration are direct benefits of that open southbound architecture; and (D) iMaster NCE automatically generates northbound RESTful APIs, making it programmable for upstream orchestration systems and applications.

C is incorrect because iMaster NCE does not deliver user-defined services "based on the Web" as a programmable feature - its northbound programmability is specifically through auto-generated RESTful interfaces (captured by D), not a general-purpose web service delivery mechanism. Option C conflates the concept of web-based service portals with the platform's actual API-driven programmability.

Memory tip: Think of iMaster NCE's openness in two directions - south (NETCONF/STelnet for devices, cross-vendor support) and north (auto-generated RESTful APIs for orchestrators). A, B, and D map cleanly to those two directions; C sneaks in "Web delivery" which doesn't match either layer.

No community discussion yet for this question.