diff --git a/_questions/data-engineering-zoomcamp/module-2/021_5a0d2c0e59_kestra-stdout-variables.md b/_questions/data-engineering-zoomcamp/module-2/021_5a0d2c0e59_kestra-stdout-variables.md
new file mode 100644
index 0000000..b2b4f16
--- /dev/null
+++ b/_questions/data-engineering-zoomcamp/module-2/021_5a0d2c0e59_kestra-stdout-variables.md
@@ -0,0 +1,7 @@
+---
+id: 5a0d2c0e59
+question: Why doesn’t Kestra automatically convert printed task outputs into variables?
+sort_order: 5
+---
+
+Kestra distinguishes between execution logs and structured outputs. Values printed to stdout are treated as logs for observability, not as structured data. Explicit output definitions are required to persist or reuse values across tasks.
\ No newline at end of file