Service mesh concept in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary role of a service mesh in microservices?

Imagine you have many small services talking to each other in an app. What main job does a service mesh do?

A It stores all the data used by the microservices in a central database.

B It compiles the code of all microservices into a single executable.

C It replaces the need for containers by running services directly on hardware.

D It manages communication between services, handling security, routing, and monitoring.

💡 Hint

Think about how services talk and stay safe and visible.

A service mesh helps microservices communicate securely and reliably by managing traffic, security policies, and observability without changing the services themselves.

💻 Command Output

intermediate

What output does this Istio command produce?

Run the command istioctl proxy-status in a Kubernetes cluster with Istio installed. What does it show?

Microservices

istioctl proxy-status

A A list of all Envoy proxies connected to the Istio control plane with their sync status.

B The current CPU and memory usage of the Istio control plane pods.

C A list of all Kubernetes nodes and their IP addresses.

D The version of Istio installed on the cluster.

💡 Hint

Think about what 'proxy-status' might mean in Istio.

The command shows the status of Envoy proxies (sidecars) connected to the Istio control plane, including if their configurations are synced.

🔀 Workflow

advanced

Order the steps to enable mutual TLS (mTLS) in a service mesh

Put these steps in the correct order to enable mutual TLS between services in a service mesh.

A 1,3,2,4

B 1,2,3,4

C 3,1,2,4

D 2,1,3,4

💡 Hint

Think about preparing the namespace, deploying services, then enforcing policies.

First, enable sidecar injection so proxies are added. Then deploy services with sidecars. Next, apply the mTLS policy. Finally, verify the setup.

❓ Troubleshoot

advanced

Why might a service mesh cause increased latency between microservices?

You notice that calls between microservices are slower after adding a service mesh. What is a likely cause?

A The service mesh merges all services into one, causing bottlenecks.

B The sidecar proxies add extra network hops and encryption overhead.

C The service mesh disables caching in the microservices.

D The microservices are running on slower hardware than before.

💡 Hint

Think about what sidecars do to network traffic.

Sidecar proxies intercept and encrypt traffic, adding processing time and extra network hops, which can increase latency.

✅ Best Practice

expert

Which practice best improves observability in a service mesh?

To understand how your microservices behave in a service mesh, which practice is best?

A Only monitor the main application containers, ignoring sidecars.

B Disable all logging to reduce noise and improve performance.

C Enable distributed tracing and collect metrics from sidecar proxies.

D Use manual log parsing instead of automated tools.

💡 Hint

Think about how to get detailed info from all parts of the mesh.

Distributed tracing and metrics from sidecars give detailed insights into service interactions and performance.