H12-893_V1-0 practice question 9 of 15

"1-3-5" troubleshooting of the CloudFabric intelligent O&M solution can detect, locate, and rectify faults from multiple dimensions. Which of the following are not dimensions supported by this function? (Select All that Apply)

Full set: 60 questions
Answer options
A: Device
B: Protocol
C: Service
D: Application Correct answer
E: Configuration
Correct Answer:
D. Application
Explanation

The "1-3-5" intelligent O&M capability of Huawei's CloudFabric solution focuses on the network infrastructure layers to rapidly detect, locate, and rectify faults. Its analysis dimensions include the health and performance of physical and virtual Devices, the status of network Protocols (like BGP EVPN), the impact on end-to-end Services (tenant connectivity), and issues arising from Configuration changes. It does not perform deep analysis of the Application layer itself (e.g., application code, database performance), which is the domain of Application Performance Monitoring (APM) tools.

Why Incorrect

A. Device health (CPU, memory, interface status) is a fundamental dimension for network O&M and is monitored by the solution.
B. Protocol status (e.g., BGP EVPN peer relationships) is critical for overlay network connectivity and is a key analysis dimension.
C. Service-level monitoring, such as tenant-to-tenant or tenant-to-external connectivity, is a primary goal of the O&M solution.
E. Configuration changes are a common source of faults, and the system correlates these changes with network issues.

References

1. Huawei iMaster NCE-FabricInsight Product Documentation, "Intelligent O&M" section. This document outlines the solution's capabilities, focusing on network-centric dimensions like device status, service quality, and protocol health to achieve the "1-3-5" goal. It does not list application-layer analysis as a native dimension.

2. Huawei CloudFabric Data Center Network Solution White Paper, "Intelligent O&M with iMaster NCE-FabricInsight" chapter. It describes the multi-dimensional analysis of the network fabric, covering physical network, logical network, and service application network layers, but the analysis of the "application" is from a network perspective (e.g., packet loss), not an application code perspective.

Scroll to Top