Which aspect is NOT directly addressed by SMI API specifications?

Which aspect is NOT directly addressed by SMI API specifications?

• A. Data storage
• B. Traffic routing
• C. Policy enforcement
• D. Service discovery

Answer: (A)

SMI API specifications define how a service mesh describes communication between services: how services are discovered, how traffic is routed between them, and what policies apply to that traffic (such as route definitions, retries, timeouts, and policy-based access between services). This makes data routing, routing policies, and service discovery directly addressed by the SMI standards. Data storage, on the other hand, is about persisting state and databases, which is outside the scope of traffic management and service-mmesh policy definitions. Therefore, the aspect not addressed by SMI API specifications is data storage.

SMI API specifications define how a service mesh describes communication between services: how services are discovered, how traffic is routed between them, and what policies apply to that traffic (such as route definitions, retries, timeouts, and policy-based access between services). This makes data routing, routing policies, and service discovery directly addressed by the SMI standards. Data storage, on the other hand, is about persisting state and databases, which is outside the scope of traffic management and service-mmesh policy definitions. Therefore, the aspect not addressed by SMI API specifications is data storage.