Question 120
The organization wants region-specific workspace provisioning from one workflow, with only location and naming differences. What GitHub Actions feature fits?
Explanation
Correct Answer
A deployment matrix reuses one workflow definition while recording each environment's distinct parameter set.
Incorrect Answers
Make deployment depend on successful test and build jobs and halt on failures. This is useful for the distinct issue: A workflow has test, build, and deploy jobs but continues deploying when integration tests fail. The relevant technical rationale or evidence for that issue is: Gated job dependencies ensure unverified artifacts do not advance to environments that serve production ML traffic. Here the reported issue is: The organization wants region-specific workspace provisioning from one workflow, with only location and naming differences. The relevant response is: Use an explicit matrix strategy with approved region and parameter combinations. The first result cannot verify this different correction: A deployment matrix reuses one workflow definition while recording each environment's distinct parameter set.
Publish build artifacts or versioned model assets and download them in dependent jobs. It addresses another case: An engineer checks in generated model binaries as workflow source to pass them between training and deployment jobs. For that case, the distinguishing justification or acceptance check is: Artifact transfer preserves the exact build output without inflating source history or recreating it in each deployment job. The present case instead states: The organization wants region-specific workspace provisioning from one workflow, with only location and naming differences. It calls for Use an explicit matrix strategy with approved region and parameter combinations. Showing success for the other case would not establish: A deployment matrix reuses one workflow definition while recording each environment's distinct parameter set.
The alternative, Record the Git commit SHA, parameter values, deployment ID, and outcome as release evidence, belongs to a different technical condition: A failed production infrastructure deployment should leave evidence identifying the exact Bicep commit. There the source-specific mechanism or proof is: Immutable source and deployment identifiers make it possible to reconstruct which configuration produced the deployed state. The condition asked about here is: The organization wants region-specific workspace provisioning from one workflow, with only location and naming differences. A suitable correction is Use an explicit matrix strategy with approved region and parameter combinations; the targeted justification or result is: A deployment matrix reuses one workflow definition while recording each environment's distinct parameter set.