H12-891_V1.0 · Question #170
During the static subscription process of Telemetry, the network manager samples the subscription configuration delivered by the device. Regarding the sampling path of huawei debug…
The correct answer is C. debug may be the top-level node (module) of the model. Option C is wrong because in the YANG model path huawei-debug:debug/cpu-infos/cpu-info, the portion before the colon (huawei-debug) identifies the top-level module - not debug. The colon is the YANG namespace separator, so debug is actually a container sitting inside the…
Question
During the static subscription process of Telemetry, the network manager samples the subscription configuration delivered by the device. Regarding the sampling path of huawei debug: debug/cpu-infos/cpu-info, which of the following descriptions is wrong?
Options
- AThis sampling path is the YANG model structure
- Bcpu-info may be the node (list) of the model
- Cdebug may be the top-level node (module) of the model
- Dcpu-infos may be the container of the model (container)
How the community answered
(39 responses)- A5% (2)
- B8% (3)
- C85% (33)
- D3% (1)
Explanation
Option C is wrong because in the YANG model path huawei-debug:debug/cpu-infos/cpu-info, the portion before the colon (huawei-debug) identifies the top-level module - not debug. The colon is the YANG namespace separator, so debug is actually a container sitting inside the huawei-debug module, not the module itself.
Options A, B, and D are all correct: the path does represent a YANG model hierarchy (A); cpu-info fits the role of a list node, since list names in YANG are typically singular (B); and cpu-infos - the plural, parent node - fits the pattern of a container that wraps a list (D).
Memory tip: Think of the colon as a package prefix - everything to its left (huawei-debug) is the module name, and everything to its right (debug/cpu-infos/cpu-info) is the path inside that module. The first segment after the colon is a container, not the module itself.
Topics
Community Discussion
No community discussion yet for this question.