The correct next step is to check the ALB’s idle timeout settings and compare them with the CloudFront origin timeout. This is because a CloudFront 504 error with ALB 200 OK signals a timeout mismatch rather than an origin failure: the ALB successfully processes the request and returns a 200, but if its idle timeout (default 60 seconds) is shorter than the time CloudFront waits for the full response, the ALB may close the connection before CloudFront receives it, triggering the 504. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this scenario tests your understanding of how CloudFront’s origin timeout (default 30 seconds) and ALB’s idle timeout interact—a common trap is assuming the 504 means the origin is unhealthy when the logs clearly show 200s. Remember the key insight: the ALB’s idle timeout governs connection persistence, not request processing time, so a mismatch here causes silent failures. Memory tip: “504 + 200 = Timeout Tango”—if the origin says OK but CloudFront times out, dance between the two timeout settings.
DOP-C02 Incident and Event Response Practice Question
This DOP-C02 practice question tests your understanding of incident and event response. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
A DevOps team observes that an Amazon CloudFront distribution is returning HTTP 504 errors for a small percentage of requests. The origin is an Application Load Balancer (ALB) that distributes traffic to EC2 instances. The team has already checked the ALB's access logs and found that the ALB returns 200 OK for all requests. What should the team investigate NEXT?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Check the ALB's idle timeout settings and compare with CloudFront origin timeout.
The ALB returns 200 OK for all requests, so the origin itself is not failing. However, HTTP 504 errors from CloudFront typically indicate that the origin (ALB) is not responding within CloudFront's timeout window. The ALB's idle timeout (default 60 seconds) can cause the ALB to close idle connections, while CloudFront's origin timeout (default 30 seconds) is separate. If the ALB's idle timeout is shorter than the time CloudFront waits for a response, the ALB may close the connection before CloudFront receives the full response, leading to a 504. Option D directly addresses this mismatch.
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.
✗
Check the ALB target group health check settings and ensure instances are healthy.
Why it's wrong here
ALB logs show 200, so targets are responding.
✗
Examine the request headers in CloudFront logs to identify unusual patterns.
Why it's wrong here
Request headers are unlikely to cause 504 errors.
✗
Review the CloudFront cache hit ratio and optimize caching strategies.
Why it's wrong here
Cache hit ratio does not cause 504 errors.
✓
Check the ALB's idle timeout settings and compare with CloudFront origin timeout.
Why this is correct
If the ALB idle timeout is less than CloudFront's origin timeout, the ALB may close the connection before CloudFront receives the response.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume 504 errors always indicate an unhealthy origin, but the ALB logs show 200 OK, so they incorrectly focus on health checks or caching instead of the timeout mismatch between CloudFront and the ALB.
Trap categories for this question
Command / output trap
ALB logs show 200, so targets are responding.
Detailed technical explanation
How to think about this question
CloudFront's origin timeout is configurable up to 60 seconds (for custom origins) and defaults to 30 seconds, while the ALB's idle timeout defaults to 60 seconds. If the ALB's idle timeout is set lower than CloudFront's origin timeout, the ALB may close the TCP connection after the idle timeout expires, causing CloudFront to receive a connection reset (RST) and return a 504. This is a classic timeout mismatch scenario where both systems appear healthy individually but fail under specific timing conditions.
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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
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.
Incident and Event Response — This question tests Incident and Event Response — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Check the ALB's idle timeout settings and compare with CloudFront origin timeout. — The ALB returns 200 OK for all requests, so the origin itself is not failing. However, HTTP 504 errors from CloudFront typically indicate that the origin (ALB) is not responding within CloudFront's timeout window. The ALB's idle timeout (default 60 seconds) can cause the ALB to close idle connections, while CloudFront's origin timeout (default 30 seconds) is separate. If the ALB's idle timeout is shorter than the time CloudFront waits for a response, the ALB may close the connection before CloudFront receives the full response, leading to a 504. Option D directly addresses this mismatch.
What should I do if I get this DOP-C02 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 →
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.
This DOP-C02 practice question is part of Courseiva's free Amazon Web Services 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 DOP-C02 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.