Which two statements about job 'needs' graphs are true? (Choose two.)
Select all correct answers, then click Submit.
Short Explanation and Infographic
needs builds a DAG within the workflow: multi-parent joins are allowed and outputs are keyed by job id. Cycles and wildcard cross-workflow waits are not features.
Full explanation below image
Full Explanation
Correct: dependency graphs must be acyclic; GitHub validates the workflow. A job can list multiple needs and then read outputs from each. Incorrect: needs does not dynamically re-execute upstream jobs when later steps change—the graph is fixed for the run. There is no needs: '*' that spans all workflows; each workflow file defines its own jobs. For cross-workflow ordering use workflow_run or explicit API dispatch. Design shallow graphs when possible so failures are easy to diagnose.