Diagnosing MWAA Workflow Failures with Apache Airflow Logs
Short answer
D Use YourEnvironmentName-Task logs to diagnose the cause of the failure because they contain detailed execution information and error traces for individual tasks.
Question
Key Takeaways
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.
Common mistake: 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.
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
https://docs.aws.amazon.com/mwaa/latest/userguide/monitoring-logging.html
This link opens the official vendor documentation in a new tab.
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?
What do DAGProcessing logs tell you in MWAA?
Community Votes
82% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
150b64e 👍 6 Answered Dhttps://pupuweb.com/amazon-dea-c01-which-apache-airflow-log-type-should-you-use-to-diagnose-workflow-failures-in-amazon-mwaa/ When a workflow fails to run in Amazon MWAA, the task logs (YourEnvironmentName-Task) are the most relevant for diagnosing the issue. Task logs contain detailed information about the execution of individual tasks within the workflow, including any error messages or stack traces that can help pinpoint the cause of the failure.
-
teo2157 👍 3 Answered DAgree with D based on 150b64e comments
-
Shanmahi 👍 2 Answered CReference --> https://aws.amazon.com/managed-workflows-for-apache-airflow/
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All DEA-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DEA-C01 Practice Test →