Courseiva

KCNA Cloud Native Architecture Practice Question

Your organization runs a cloud-native e-commerce platform on Kubernetes. The platform consists of several microservices: a frontend service, an order service, a payment service, and a shipping service. All services communicate via HTTP REST APIs. Recently, during a flash sale event, the platform experienced a cascading failure. The order service became overwhelmed with requests and started responding slowly. This caused the frontend service to time out waiting for order responses, and eventually the frontend service crashed due to exhausted thread pools. The payment and shipping services were unaffected because they are called asynchronously via a message queue. You need to redesign the system to prevent such cascading failures in the future. Which approach is the most effective?

⚠ Common exam trap

CNCF often tests the misconception that scaling or increasing timeouts is a sufficient fix for cascading failures, but the trap here is that these options treat symptoms rather than applying the circuit breaker pattern, which is the standard resilience mechanism for synchronous calls in cloud-native systems.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Implement circuit breakers in the frontend service for calls to the order service

Implementing circuit breakers in the frontend service for calls to the order service prevents cascading failures by monitoring failure rates and automatically tripping the circuit when the order service becomes slow or unresponsive. This stops the frontend from exhausting its thread pools waiting for timeouts, allowing it to fail fast and return a fallback response. Circuit breakers are a proven resilience pattern in cloud-native architectures, especially for synchronous HTTP REST calls where latency spikes can propagate.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Scale up the frontend service to handle more concurrent requests

    Why it's wrong here

    Adding frontend replicas leaves the exhausted thread pools blocked on the slow order service, so each new pod stalls identically. Horizontal scaling suits CPU-bound frontends serving independent requests; here the bottleneck sits downstream, and the stem's fix must break the synchronous dependency.

  • ✗

    Convert all inter-service communication to synchronous calls with retries

    Why it's wrong here

    Retries amplify load on an already-overloaded order service, deepening the cascading failure rather than containing it. Synchronous retries suit transient network faults, where a brief blip resolves on a second attempt; here the dependency is saturated, so retrying multiplies pressure and exhausts frontend threads faster.

  • ✗

    Increase the timeout values in the frontend service configuration

    Why it's wrong here

    Longer timeouts keep frontend threads occupied waiting on the slow order service, delaying failure without freeing the pool. Extended timeouts suit occasional slow-but-successful calls; during sustained overload they hold resources longer, so the cascade still occurs.

  • ✓

    Implement circuit breakers in the frontend service for calls to the order service

    Why this is correct

    Circuit breakers in the frontend trip when order-service calls exceed a failure threshold, failing fast instead of holding threads until timeout. This stops thread-pool exhaustion and the cascading failure, directly addressing the synchronous HTTP dependency that caused the frontend to crash.

Visual reference

Client Server SYN (seq=100) SYN-ACK (seq=200, ack=101) ACK (ack=201) Connection established — data transfer begins

About these practice questions

Courseiva writes every KCNA question from scratch — 930 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This KCNA practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the KCNA exam.