- A service mesh works at which layer of the network?
A) Layer 7
B) Layer 3/4
- Libraries such as Hystrix and Finnagle were excellent in abstracting traffic routing capabilities, but why did Envoy prove to be successful for cloud-native applications?
A) The libraries were for Java applications, and they needed to be ported to other applications, whereas the Envoy proxy sidecar was language-agnostic and could work with polyglot applications.
B) An update in the library will force an application to update, whereas the Envoy proxy can be upgraded independently of the application microservices.
C) Libraries can manage traffic, but load balancing is an outside function, whereas it is integrated with the Envoy proxy with dynamic rules and configuration propagation through Istio components.
D) All of the above.
E) None of the above.
- The Istio control plane is a single point of failure for microservices applications.
A) True
B) False
- The true service mesh is formed through Envoy sidecar proxies.
A) True
B) False
- Istio works at a single cluster level and can't span multiple clusters.
A) True
B) False
- Service discovery in Istio is tightly integrated with Kubernetes, but it can also work with external service providers.
A) True
B) False
- Pilot is responsible for managing traffic, whereas Envoy pushes the configuration to Pilot.
A) True
B) False
- Istio primitives such as Destination Rules, Gateway, Virtual Service, and so on can only be created through istioctl but not using kubectl.
A) True
B) False
- Implementing Istio transport security for mTLS is a self-service model.
A) True
B) False
- You can observe the service mesh for connectivity and traffic patterns through Kiali.
A) True
B) False