Diagnosing MWAA Workflow Failures with Apache Airflow Logs
A data engineer uses Amazon Managed Workflows for Apache Airflow (Amazon MWAA) to run data pipelines in an AWS account. A workflow recently failed to run. The data engineer needs to use Apache Airflow logs to diagnose the failure of the workflow. Which log type should the data engineer use to diagnose the cause of the failure?
Community Votes
82% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests knowledge of Amazon MWAA logging architecture; the common trap is confusing scheduler or web server logs with the granular task execution logs required for failure diagnosis.
Learn which Amazon MWAA log type is essential for diagnosing workflow failures: Task logs provide the specific error details needed to troubleshoot individual task execution.
Selecting Scheduler logs (B) because they handle DAG scheduling, but failing to realize that scheduler logs do not contain the runtime error details of the tasks themselves.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
To diagnose a specific workflow failure in Amazon Managed Workflows for Apache Airflow (MWAA), the data engineer must examine the Task logs (YourEnvironmentName-Task). These logs capture the output and standard error streams of individual tasks running within the workflow. When a task fails, the exception traceback, stack trace, and specific error messages are written here, providing the necessary context to identify why the code or logic failed.Why the Other Options Are Wrong
The WebServer logs (A) record HTTP requests and API calls made to the Airflow UI, which are useful for debugging UI issues but not task execution errors. The Scheduler logs (B) track how DAGs are parsed and scheduled, helping to identify if a DAG was missed or delayed, but they do not show task-level runtime exceptions. The DAGProcessing logs (C) focus on the parsing phase of DAG files, highlighting syntax errors or import issues before execution begins, rather than runtime failures during the run itself.Community Comment Notes
Community consensus strongly supports Option D, with many users noting that task logs are the primary source for troubleshooting runtime errors. As one commenter noted, "Task logs contain detailed information about the execution of individual tasks," which aligns with AWS documentation stating that task logs are crucial for debugging task-specific issues.Official Reference
Exam Strategy
When asked about troubleshooting a running pipeline's failure, always look for logs that capture the execution state of the components doing the work (Tasks). For configuration or setup issues, look at Scheduler or DAG Processing logs.
Frequently Asked Questions
Why not use Scheduler logs to diagnose a failed workflow?
Scheduler logs only show when and if DAGs were scheduled. They do not contain the runtime error messages or stack traces generated by the tasks themselves during execution.
What do DAGProcessing logs tell you in MWAA?
DAGProcessing logs reveal issues with parsing DAG files, such as syntax errors or missing imports, occurring before the workflow actually starts running.
Related Analysis
Practice All DEA-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DEA-C01 Practice Test →