Service mesh vs library-based approach in Kubernetes - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Key difference between service mesh and library-based approach

Which statement best describes the main difference between a service mesh and a library-based approach for managing microservice communication?

A A service mesh operates as a separate infrastructure layer managing communication, while a library-based approach requires code changes inside each service.

B Both service mesh and library-based approaches require no changes to application code and operate transparently.

C A service mesh requires modifying application code, but a library-based approach works externally without code changes.

D A library-based approach manages communication at the network level, while a service mesh is embedded inside each service.

💡 Hint

Think about where the communication logic lives: inside the app or outside it.

A service mesh runs as a separate layer (usually sidecar proxies) managing communication without changing app code. A library-based approach requires adding code to each service to handle communication.

✅ Best Practice

intermediate

Choosing between service mesh and library-based approach

You want to add observability and traffic control to your microservices without changing their code. Which approach is best?

A Rewrite all services to include communication libraries for better control.

B Use a library-based approach because it requires no infrastructure changes.

C Use a service mesh because it works without modifying service code.

D Use manual network policies to control traffic instead of either approach.

💡 Hint

Consider which approach allows adding features without touching service code.

Service meshes add features like observability and traffic control externally, so services do not need code changes. Library-based approaches require modifying each service.

💻 Command Output

advanced

Output of checking sidecar proxy in a service mesh

What is the expected output of the following command in a Kubernetes cluster using Istio service mesh?

kubectl get pods -n default -l app=myservice -o jsonpath='{.items[0].spec.containers[*].name}'

Assuming Istio sidecar injection is enabled.

A Error: no such label

B myservice

C istio-proxy

D myservice istio-proxy

💡 Hint

Think about what containers run in a pod with Istio sidecar injection.

When Istio sidecar injection is enabled, each pod has the original service container plus an 'istio-proxy' sidecar container. The command lists both container names.

❓ Troubleshoot

advanced

Troubleshooting failed communication in library-based approach

You deployed a library-based communication approach in your microservices. Suddenly, services cannot communicate. Which is the most likely cause?

A Network policies block traffic between pods.

B The communication library version is incompatible with the service runtime.

C The service mesh sidecar proxy crashed.

D The Kubernetes API server is down.

💡 Hint

Focus on what is unique to library-based approaches compared to service mesh.

Library-based approaches depend on the communication library inside the service. If the library version is incompatible, communication fails. Sidecar crashes or network policies are more common in service mesh or network issues.

🔀 Workflow

expert

Correct order to enable service mesh on existing Kubernetes services

Arrange the steps in the correct order to enable a service mesh (e.g., Istio) on existing Kubernetes services.

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 3,1,2,4

💡 Hint

Think about installing first, then enabling injection, then redeploying.

First, install the control plane. Then enable sidecar injection in the namespace. Next, redeploy services to get sidecars injected. Finally, verify pods have both containers.

Practice

1. What is the main difference between a service mesh and a library-based approach in Kubernetes?

easy

A. Service mesh requires changing app code, library-based works externally

B. Service mesh is for storage, library-based is for networking

C. Service mesh only works with databases, library-based only with APIs

D. Service mesh manages communication outside the app, library-based adds code inside the app

Solution

1. Step 1: Understand service mesh role

   A service mesh manages communication between services outside the app, usually with sidecar proxies.

2. Step 2: Understand library-based approach

   Library-based approach adds communication features inside the app code itself.

3. Final Answer:

   Service mesh manages communication outside the app, library-based adds code inside the app -> Option D

4. Quick Check:

   Service mesh = external, library-based = internal [OK]

Hint: Service mesh is external, library-based is inside app code [OK]

Common Mistakes:

• Confusing which approach requires code changes
• Thinking service mesh only works with databases
• Mixing up external vs internal communication handling

2. Which of the following is a correct statement about implementing a service mesh in Kubernetes?

easy

A. Service mesh uses sidecar proxies injected alongside application pods

B. You must modify each application's source code to use the service mesh

C. Service mesh replaces Kubernetes networking completely

D. Service mesh only works with monolithic applications

Solution

1. Step 1: Recall service mesh architecture

   Service mesh typically uses sidecar proxies injected into pods to handle communication externally.

2. Step 2: Evaluate other options

   Modifying app code is not required; it does not replace Kubernetes networking; it works with microservices too.

3. Final Answer:

   Service mesh uses sidecar proxies injected alongside application pods -> Option A

4. Quick Check:

   Sidecar proxies = service mesh [OK]

Hint: Sidecar proxies run alongside apps in service mesh [OK]

Common Mistakes:

• Thinking app code must be changed for service mesh
• Believing service mesh replaces Kubernetes networking
• Assuming service mesh only supports monoliths

3. Given a Kubernetes app using a library-based approach for service communication, what is the expected output if the app code does not include the library?

medium

A. The app will fail to communicate with other services

B. The app will automatically use a service mesh fallback

C. The app will communicate normally without any issues

D. The app will crash immediately on startup

Solution

1. Step 1: Understand library-based approach dependency

   Library-based approach requires the app code to include the communication library to work properly.

2. Step 2: Predict behavior without library

   If the library is missing, the app cannot handle communication as expected and will fail to connect to other services.

3. Final Answer:

   The app will fail to communicate with other services -> Option A

4. Quick Check:

   Missing library = communication failure [OK]

Hint: Library missing means communication fails [OK]

Common Mistakes:

• Assuming app works without library in library-based approach
• Thinking service mesh auto-fallback happens
• Confusing app crash with communication failure

4. You deployed a service mesh but notice your app is not routing traffic correctly. Which is the most likely cause?

medium

A. The app code lacks the required communication library

B. Sidecar proxy injection failed or is missing

C. The Kubernetes cluster is down

D. The app is using an unsupported programming language

Solution

1. Step 1: Identify service mesh traffic handling

   Service mesh relies on sidecar proxies injected into pods to route traffic correctly.

2. Step 2: Analyze common deployment issues

   If traffic is not routing, a common cause is sidecar proxy injection failure or absence.

3. Final Answer:

   Sidecar proxy injection failed or is missing -> Option B

4. Quick Check:

   Missing sidecar = routing issues [OK]

Hint: Check sidecar proxy injection for routing issues [OK]

Common Mistakes:

• Blaming app code library in service mesh setup
• Assuming cluster is down without checking
• Thinking language support affects routing directly

5. You want to add observability and security features to your Kubernetes microservices without changing app code. Which approach is best and why?

hard

A. Rewrite apps to include custom communication logic

B. Use a library-based approach to add features inside each app

C. Use a service mesh to manage features externally with sidecars

D. Disable all communication features for simplicity

Solution

1. Step 1: Identify requirement to avoid app code changes

   The question states no changes to app code are desired.

2. Step 2: Match approach to requirement

   Service mesh manages communication externally using sidecars, so it adds features without touching app code.

3. Step 3: Evaluate other options

   Library-based requires code changes; rewriting apps is costly; disabling features is not helpful.

4. Final Answer:

   Use a service mesh to manage features externally with sidecars -> Option C

5. Quick Check:

   No code change = service mesh best [OK]

Hint: No code change? Choose service mesh [OK]

Common Mistakes:

• Choosing library-based despite no code change allowed
• Thinking rewriting apps is easier
• Ignoring observability and security needs