Path-based routing in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of path-based routing Ingress configuration

Given the following Kubernetes Ingress YAML snippet, what will be the backend service receiving traffic for the path /app1?

Kubernetes

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: example-ingress
spec:
  rules:
  - http:
      paths:
      - path: /app1
        pathType: Prefix
        backend:
          service:
            name: service-app1
            port:
              number: 80
      - path: /app2
        pathType: Prefix
        backend:
          service:
            name: service-app2
            port:
              number: 80

A service-app1 on port 80

B service-app2 on port 80

C Default backend service

D No service, returns 404

💡 Hint

Look at the path and backend service mapping in the Ingress spec.

The path /app1 is explicitly routed to service-app1 on port 80 as per the Ingress rules.

❓ Configuration

intermediate

Correct pathType for prefix matching in Ingress

Which pathType value should be used in a Kubernetes Ingress to route all requests starting with /api to a backend service?

A Prefix

B Regex

C Exact

D ImplementationSpecific

💡 Hint

Consider which pathType matches all paths starting with the given prefix.

The 'Prefix' pathType matches all requests that start with the specified path prefix.

❓ Troubleshoot

advanced

Why does traffic to /app not route correctly?

A user configured this Ingress snippet but traffic to /app returns 404. What is the most likely cause?

Kubernetes

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: test-ingress
spec:
  rules:
  - http:
      paths:
      - path: /app/
        pathType: Exact
        backend:
          service:
            name: app-service
            port:
              number: 80

A Service app-service is not running

B Using pathType Exact with a trailing slash causes mismatch for /app

C Ingress controller is not installed

D Port 80 is blocked by firewall

💡 Hint

Check how Exact pathType matches requests.

Exact pathType requires the request path to exactly match /app/, so /app (without trailing slash) returns 404.

🔀 Workflow

advanced

Order of path matching in Kubernetes Ingress

In which order does Kubernetes Ingress controller evaluate multiple path rules for routing?

A 3,1,2,4

B 2,1,3,4

C 1,2,3,4

D 4,3,2,1

💡 Hint

Think about how more specific paths should be matched before less specific ones.

Ingress controllers match the longest path prefix first to ensure specific routes take precedence.

✅ Best Practice

expert

Best practice for path-based routing with overlapping paths

You have two Ingress paths: /app and /app/v2. What is the best practice to ensure traffic to /app/v2 goes to the correct backend without conflict?

A Use a single backend for both paths

B Use pathType Exact for both paths

C Use different Ingress resources for each path

D Define /app/v2 path before /app path in Ingress rules

💡 Hint

Consider how path matching order affects routing when paths overlap.

Defining the more specific path /app/v2 before /app ensures it matches first and routes correctly.