Bird
0
0

A microservice call fails intermittently due to DNS resolution errors. What is the most likely cause?

medium📝 Analysis Q6 of 15
Microservices - Orchestration with Kubernetes
A microservice call fails intermittently due to DNS resolution errors. What is the most likely cause?
AMicroservice code has syntax errors
BLoad balancer is misconfigured
CDatabase connection is slow
DService discovery cache is outdated
Step-by-Step Solution
Solution:

  1. Step 1: Identify DNS resolution failure cause

    Intermittent DNS errors often happen when service discovery caches stale IP addresses.

  2. Step 2: Exclude unrelated causes

    Syntax errors, slow database, or load balancer issues do not cause DNS resolution failures.

  3. Final Answer:

    Service discovery cache is outdated -> Option D

  4. Quick Check:

    DNS errors = stale service discovery cache [OK]
Quick Trick: DNS errors often mean stale service info [OK]
Common Mistakes:
MISTAKES
  • Blaming code syntax
  • Confusing database slowness with DNS
  • Assuming load balancer causes DNS errors

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Microservices Quizzes
Authentication and Authorization - JWT token propagation - Quiz 13medium Authentication and Authorization - API key management - Quiz 5medium Authentication and Authorization - JWT token propagation - Quiz 15hard Authentication and Authorization - Service-to-service authentication - Quiz 15hard Monitoring and Observability - Correlation IDs - Quiz 5medium Orchestration with Kubernetes - Liveness and readiness probes - Quiz 10hard Orchestration with Kubernetes - Namespace isolation - Quiz 6medium Orchestration with Kubernetes - Pods and deployments for services - Quiz 10hard Resilience Patterns - Circuit breaker pattern - Quiz 7medium Resilience Patterns - Bulkhead pattern - Quiz 4medium