ISTIO MCQ Questions and Answers
Question#1 Which istioctl commad injects sidecars manually?
Question#2 This is not an istio system service.
Question#3 How to enable Automatic Injection?
a) Istioctl injection=enabled
b) kubectl namespace istio-injection=enabled
c) kubectl label namespace istio-injection=enabled
d) kubectl injection=enabled
Answer:- kubectl label namespace istio-injection=enabled
Question#4 Envoy comes under
a) Service Plane
b) Control Plane
c) Data Plane
d) Proxy Plane
Answer:- Data Plane
Question#5 Envoy is responsible for enforcement of access control and usage policies
Question#6 Istio enables service to service communication without any intermediate services.
Question#7 monolithic applications are easily scalable
Question#8 This component is responsible for ingress traffic management.
Question#9 Automatic sidecar injection is suitable for
a) new services
b) non istio services
c) statefull services
d) all kubernetes services
Answer:- statefull services
Question#10 In yaml “–“(hyphen) represents
d) Nothing. Its Invalid
Question#11 This component is responsible for authentication
Question#12 istio doesn’t support the following protocol
d) none of the mentioned
Answer:- none of the mentioned
Question#13 Which istio component is responsible for mediating traffic between services?
Question#14 Envoy is written in which programming language?
Question#15 Istio cannot handle load balancing
ISTIO Explanatory Questions and Answers for Experienced
1) What is Istio and how it works?
An Istio service mesh is logically split into a data plane and a control plane. The data plane is composed of a set of intelligent proxies (Envoy ) deployed as sidecars. These proxies mediate and control all network communication between microservices. They also collect and report telemetry on all mesh traffic.
2) What is Istio used for in Kubernetes?
Istio makes traffic management transparent to the application, moving this functionality out of the application and into the platform layer as a cloud native infrastructure. Istio complements Kubernetes, by enhancing its traffic management, observability and security for cloud native applications.
3) What problems does Istio solve?
And Kubernetes/Istio is a technical solution to deal with the issues created by moving to microservices. As a deliverable for microservices, containers solve the problem of environmental consistency and allow for more granularity in limiting application resources. They are widely used as a vehicle for microservices.
4) What are the Istio components?
Istio has two components: the data plane and the control plane. The data plane is the communication between services. Without a service mesh, the network doesn’t understand the traffic being sent over, and can’t make any decisions based on what type of traffic it is, or who it is from or to.
5) Who developed Istio?
The Istio project was started by teams from Google and IBM in partnership with the Envoy team from Lyft. It’s been developed fully in the open on GitHub.
6) What is galley in Istio?
Galley is Istio’s configuration validation, ingestion, processing and distribution component. It is responsible for insulating the rest of the Istio components from the details of obtaining user configuration from the underlying platform (e.g. Kubernetes).
7) Is Istio hard?
Solo sponsored this post. For a very long time, Istio has been criticized as notoriously complex and hard to use. As someone who worked on the project for over four years, I agreed with this statement in the first two years of Istio.
8) What is a helm chart?
Helm uses a packaging format called charts. A chart is a collection of files that describe a related set of Kubernetes resources. A single chart might be used to deploy something simple, like a memcached pod, or something complex, like a full web app stack with HTTP servers, databases, caches, and so on.
9) What are the main features of Citadel in Istio?
Citadel for key and certificate management. Sidecar and perimeter proxies to implement secure communication between clients and servers. Pilot to distribute authentication policies and secure naming information to the proxies. Mixer to manage authorization and auditing.
10) What is the job of an Istio agent?
A separate component, the istio-agent, helps each sidecar connect to the mesh by securely passing configuration and secrets to the Envoy proxies. While the agent, strictly speaking, is still part of the control plane, it runs on a per-pod basis.
11) Is Istio safe?
The Istio security features provide strong identity, powerful policy, transparent TLS encryption, and authentication, authorization and audit (AAA) tools to protect your services and data. The goals of Istio security are: Security by default: no changes needed to application code and infrastructure.
12) What is the default sidecar proxy in Istio?
By default, Istio will program all sidecar proxies in the mesh with the necessary configuration required to reach every workload instance in the mesh, as well as accept traffic on all the ports associated with the workload.