Regarding the description of Huawei Cloud Application Service Grid ASM, which of the following statements is wrong?

Question

Options

• AProvide integrated solutions for traditional microservice SDKs such as Spring Cloud and Dubbo
• BCloud application service grid development framework is not limited to language
• CAbility to provide container-based gray scale publishing and traffic management
• DIt is necessary to integrate the Istio Community Edition SDK to realize application access

• A
  11% (2)
• B
  5% (1)
• C
  5% (1)
• D
  79% (15)

Explanation

Option D is wrong because Huawei Cloud ASM (Application Service Mesh) operates on a sidecar proxy model, meaning applications do not need to integrate any SDK - including the Istio Community Edition SDK - to be onboarded. The entire value of a service mesh is that it works transparently at the infrastructure layer without requiring code changes or library dependencies.

Options A, B, and C are all accurate descriptions of ASM. It does provide integration support for traditional microservice frameworks like Spring Cloud and Dubbo (A), it is language-agnostic because the sidecar proxy handles communication independently of the application's programming language (B), and it does support container-based canary (gray scale) publishing and traffic management (C).

Memory tip: The core promise of any service mesh is "no SDK required." If a question suggests you must embed an Istio SDK into your application to use ASM, that directly contradicts the non-intrusive design principle - flag it as false immediately.

No community discussion yet for this question.