Answer-first summary for fast verification
Answer: Use Istio's fault injection on the particular microservice whose faulty behavior you want to simulate.
The question requires validating application behavior when a specific microservice crashes abruptly. Option B (Istio's fault injection) is optimal because it allows targeted simulation of microservice failures without affecting other components, aligning with chaos engineering principles. The community consensus strongly supports B (89% votes), with key insights: fault injection tests application-layer failures directly, while destroying a node (C) is imprecise—it may not affect the target microservice if distributed across nodes and disrupts other services. Option A (taint/anti-affinity) is for pod placement, not failure simulation. Option D (traffic management) handles routing after failure but doesn't simulate the crash itself. Although Istio on GKE is deprecated, Anthos Service Mesh is its successor, and the fault injection concept remains valid for controlled testing.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
You are developing a microservices application on Google Kubernetes Engine. During testing, you need to validate your application's behavior when a specific microservice crashes abruptly. What should you do?
A
Add a taint to one of the nodes of the Kubernetes cluster. For the specific microservice, configure a pod anti-affinity label that has the name of the tainted node as a value.
B
Use Istio's fault injection on the particular microservice whose faulty behavior you want to simulate.
C
Destroy one of the nodes of the Kubernetes cluster to observe the behavior.
D
Configure Istio's traffic management features to steer the traffic away from a crashing microservice.