- A
Scale up the frontend service to handle more concurrent requests
Why wrong: Does not address the root cause; may only delay the failure.
- B
Convert all inter-service communication to synchronous calls with retries
Why wrong: Synchronous calls without resilience patterns can still cause cascading failures.
- C
Increase the timeout values in the frontend service configuration
Why wrong: Longer timeouts can still exhaust threads if the downstream is slow.
- D
Implement circuit breakers in the frontend service for calls to the order service
Circuit breakers prevent cascading failures by failing fast.
KCNA Cloud Native Architecture Practice Question
This KCNA practice question tests your understanding of cloud native architecture. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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?
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
Option D is correct because 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.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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
Does not address the root cause; may only delay the failure.
- ✗
Convert all inter-service communication to synchronous calls with retries
Why it's wrong here
Synchronous calls without resilience patterns can still cause cascading failures.
- ✗
Increase the timeout values in the frontend service configuration
Why it's wrong here
Longer timeouts can still exhaust threads if the downstream is slow.
- ✓
Implement circuit breakers in the frontend service for calls to the order service
Why this is correct
Circuit breakers prevent cascading failures by failing fast.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
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.
Detailed technical explanation
How to think about this question
Circuit breakers in Kubernetes environments are often implemented using libraries like Hystrix, Resilience4j, or Istio’s circuit breaker via Envoy proxy, which track metrics such as request latency, error rate, and concurrent request count. When the failure rate exceeds a threshold (e.g., 50% of requests fail within a 10-second sliding window), the circuit opens and subsequent requests are immediately rejected with a fallback, preventing thread pool exhaustion. A subtle behavior is the half-open state, where the circuit allows a limited number of probe requests to test if the downstream service has recovered, avoiding premature re-closure.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Cloud Native Architecture — study guide chapter
Learn the concepts, then practise the questions
- →
Cloud Native Architecture practice questions
Targeted practice on this topic area only
- →
All KCNA questions
997 questions across all exam domains
- →
Kubernetes and Cloud Native Associate KCNA study guide
Full concept coverage aligned to exam objectives
- →
KCNA practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related KCNA practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Kubernetes Fundamentals practice questions
Practise KCNA questions linked to Kubernetes Fundamentals.
Container Orchestration practice questions
Practise KCNA questions linked to Container Orchestration.
Cloud Native Architecture practice questions
Practise KCNA questions linked to Cloud Native Architecture.
Cloud Native Observability practice questions
Practise KCNA questions linked to Cloud Native Observability.
Cloud Native Application Delivery practice questions
Practise KCNA questions linked to Cloud Native Application Delivery.
KCNA fundamentals practice questions
Practise KCNA questions linked to KCNA fundamentals.
KCNA scenario practice questions
Practise KCNA questions linked to KCNA scenario.
KCNA troubleshooting practice questions
Practise KCNA questions linked to KCNA troubleshooting.
Practice this exam
Start a free KCNA practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this KCNA question test?
Cloud Native Architecture — This question tests Cloud Native Architecture — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Implement circuit breakers in the frontend service for calls to the order service — Option D is correct because 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.
What should I do if I get this KCNA question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More KCNA practice questions
- Match each Kubernetes resource to its primary purpose.
- Match each Kubernetes security concept to its definition.
- A team observes that a Pod is stuck in CrashLoopBackOff. The Pod runs a single container with an entrypoint that exits w…
- An application running in a Kubernetes cluster needs to securely access a third-party API. The API key must be stored in…
- A company is adopting a GitOps workflow for their Kubernetes deployments. They want to ensure that the cluster state alw…
- Match each Kubernetes networking concept to its description.
Last reviewed: Jun 30, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.