Linkerd overview in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary role of Linkerd in a microservices architecture?

Linkerd is a service mesh used in microservices. What is its main function?

A It replaces the need for load balancers in the network.

B It stores data persistently for microservices to access.

C It acts as a database query optimizer for microservices.

D It manages communication between microservices by providing observability, reliability, and security.

💡 Hint

Think about what a service mesh does for microservices communication.

Linkerd provides a transparent layer that manages service-to-service communication, adding features like retries, timeouts, and security without changing the services themselves.

❓ Architecture

intermediate

Which component in Linkerd handles the proxying of network traffic between services?

In Linkerd's architecture, which part is responsible for intercepting and managing the network traffic between microservices?

A Service Registry

B Control Plane

C Data Plane Proxy (sidecar proxy)

D API Gateway

💡 Hint

This component runs alongside each service instance.

The Data Plane Proxy, often a sidecar proxy, runs next to each service instance and intercepts all network traffic to provide features like load balancing and retries.

❓ scaling

advanced

How does Linkerd ensure scalability when managing thousands of microservices?

Linkerd must handle communication for many microservices. Which design aspect helps it scale efficiently?

A Storing all service data in a single database

B Distributed sidecar proxies running alongside each service instance

C Using a single monolithic control plane to manage all services

D Centralized proxy for all traffic to reduce overhead

💡 Hint

Think about how distributing work helps scale systems.

Linkerd uses sidecar proxies deployed with each service instance, distributing the load and avoiding bottlenecks, which allows it to scale horizontally.

❓ tradeoff

advanced

What is a tradeoff when using Linkerd's sidecar proxy model in microservices?

Using sidecar proxies adds benefits but also some costs. Which is a common tradeoff?

A Increased network latency due to extra proxy hops

B Elimination of the need for service discovery

C Simplified deployment with no additional resource use

D Reduced security because proxies bypass encryption

💡 Hint

Adding a proxy means traffic passes through an extra step.

Sidecar proxies add an extra network hop for each request, which can slightly increase latency and resource consumption.

❓ estimation

expert

Estimate the additional CPU overhead per service instance when deploying Linkerd sidecar proxies at scale.

If each Linkerd sidecar proxy adds approximately 5% CPU overhead to a service instance, what is the total CPU overhead for 1000 instances running on identical hardware?

A 5000% total CPU overhead across all instances

B 5% total CPU overhead across all instances

C 50% total CPU overhead across all instances

D 100% total CPU overhead across all instances

💡 Hint

Multiply the overhead per instance by the number of instances.

Each instance adds 5% CPU overhead. For 1000 instances, total overhead is 5% * 1000 = 5000%. This means the sum of overhead across all instances is 50 times the CPU of one instance.

Practice

1. What is the primary purpose of Linkerd in a microservices architecture?

easy

A. To write business logic for microservices

B. To replace the database layer in microservices

C. To help microservices communicate securely and reliably

D. To serve as a frontend framework for microservices

Solution

1. Step 1: Understand Linkerd's role

   Linkerd is a service mesh designed to manage communication between microservices.

2. Step 2: Identify its main function

   It ensures secure and reliable communication without changing service code.

3. Final Answer:

   To help microservices communicate securely and reliably -> Option C

4. Quick Check:

   Linkerd = Secure, reliable microservice communication [OK]

Hint: Linkerd manages communication, not business logic or UI [OK]

Common Mistakes:

• Confusing Linkerd with database or frontend tools
• Thinking Linkerd writes application code
• Assuming Linkerd replaces microservices

2. Which of the following commands is used to check the health of Linkerd after installation?

easy

A. linkerd check

B. linkerd install

C. linkerd monitor

D. linkerd deploy

Solution

1. Step 1: Recall Linkerd CLI commands

   Linkerd provides commands like install, check, and monitor for managing the service mesh.

2. Step 2: Identify the health check command

   The linkerd check command verifies if Linkerd is installed and running correctly.

3. Final Answer:

   linkerd check -> Option A

4. Quick Check:

   Health check = linkerd check [OK]

Hint: Use 'linkerd check' to verify installation health [OK]

Common Mistakes:

• Using 'linkerd install' to check health
• Confusing 'linkerd monitor' with health check
• Assuming 'linkerd deploy' is a valid command

3. Given the following snippet, what will linkerd check report if Linkerd proxies are not injected into the services?

kubectl get pods
NAME                     READY   STATUS    RESTARTS   AGE
service-a-12345           1/1     Running   0          10m
service-b-67890           1/1     Running   0          10m

medium

A. Info: Services are running but no Linkerd installed

B. All checks pass, Linkerd is fully operational

C. Error: Kubernetes cluster not reachable

D. Warning: No proxies detected, Linkerd not fully enabled

Solution

1. Step 1: Understand proxy injection role

   Linkerd requires proxies injected into pods to manage traffic and security.

2. Step 2: Analyze pod readiness and proxy presence

   Pods show 1/1 ready, but no proxy sidecar means Linkerd features are not active.

3. Final Answer:

   Warning: No proxies detected, Linkerd not fully enabled -> Option D

4. Quick Check:

   No proxies = Warning from linkerd check [OK]

Hint: No proxies means Linkerd features inactive, expect warnings [OK]

Common Mistakes:

• Assuming pods ready means Linkerd is fully working
• Confusing cluster reachability errors with proxy injection
• Thinking Linkerd works without proxies

4. You deployed Linkerd but notice that traffic is not being routed through the proxies. Which of the following is the most likely cause?

medium

A. Proxies were not injected into the service pods

B. The services are not exposing any ports

C. The Kubernetes cluster is down

D. The Linkerd control plane is not installed

Solution

1. Step 1: Check Linkerd traffic routing requirements

   Traffic routing requires proxies injected into pods to intercept and manage requests.

2. Step 2: Identify common deployment mistakes

   If proxies are missing, traffic bypasses Linkerd, causing routing issues.

3. Final Answer:

   Proxies were not injected into the service pods -> Option A

4. Quick Check:

   Missing proxies = traffic not routed [OK]

Hint: Missing proxies cause traffic routing failure [OK]

Common Mistakes:

• Assuming control plane absence causes routing issues
• Blaming Kubernetes cluster status without checking proxies
• Ignoring service port exposure as a cause

5. You want to add observability to your microservices using Linkerd. Which combination of features does Linkerd provide to achieve this without changing your service code?

hard

A. Database management, caching, and load balancing

B. Traffic routing, security, and built-in monitoring dashboards

C. Frontend UI components, API gateways, and authentication

D. Code instrumentation, manual tracing, and custom logging

Solution

1. Step 1: Identify Linkerd's observability features

   Linkerd provides traffic routing, security, and monitoring dashboards automatically via proxies.

2. Step 2: Exclude unrelated features

   Database, frontend UI, and manual code changes are outside Linkerd's scope.

3. Final Answer:

   Traffic routing, security, and built-in monitoring dashboards -> Option B

4. Quick Check:

   Linkerd = routing + security + monitoring [OK]

Hint: Linkerd adds observability without code changes [OK]

Common Mistakes:

• Confusing Linkerd with database or frontend tools
• Thinking manual code changes are needed for observability
• Mixing Linkerd with unrelated infrastructure components