A data engineer tries to create a new Apache Airflow Job item inside a branch archives workspace, but the item type doesn't appear as an option. What is the most likely missing prerequisite?
Select an answer to reveal the explanation.
Short Explanation
New Fabric item types don't just show up by default -- some, like Apache Airflow Job, need a workspace admin to flip the switch in workspace settings first. Until that setting is turned on for this specific workspace, the option to create one simply won't be there.
Full Explanation
Apache Airflow support is controlled by a workspace-level setting that a workspace admin must enable before the Apache Airflow Job item type becomes available to create in that workspace -- its absence from the create menu is the direct symptom of that setting still being off. Git connectivity governs source control and change tracking for item definitions; it has no bearing on which item types are available to create in the first place. Sensitivity labels classify data for governance after an item exists; they don't gate whether an item type can be created. A configured custom Spark pool backs Spark-based compute for notebooks and Spark jobs, a separate compute path from the dedicated environment that backs Airflow DAG runs. A scope note: this setting is per workspace, so enabling it in one branch's archives workspace does not make the item type available elsewhere in the network. Confirm the fix by having a workspace admin open Apache Airflow workspace settings, enable it, and check that the item type now appears in the New item menu.