A Lakeflow Job task named agg ends with: ```python dbutils.jobs.taskValues.set(key = "row_count", value = result_count) ``` result_count is the Python float `12.0`. An If/else condition task evaluates `{{tasks.agg.values.row_count}} == 12`, and the engineer expects the true branch to run — but the condition evaluates to false. Why did this happen, and which comparison behaves numerically?

1. A. Task values lose precision when serialized, so == is unreliable; >= has the same precision problem 💬 A
2. B. If/else conditions accept only boolean task values, so numeric conditions silently evaluate to false 💬 B
3. C. == and != compare as strings, so 12.0 does not equal 12; >, >=, <, and <= are numeric ✓ C
4. D. The If/else task failed to read the value, because task values cannot store numbers 💬 D

Reveal answer

Correct answer: == and != compare as strings, so 12.0 does not equal 12; >, >=, <, and <= are numeric

Reference: https://docs.databricks.com/aws/en/jobs/tasks/if-else