Question 110
A deployment needs to pass the newly created Azure ML workspace resource identifier to a subsequent GitHub Actions job. Which Bicep feature exposes it?
Explanation
Correct Answer
Explicit outputs transmit computed resource identifiers without fragile scraping of deployment logs or copied portal values.
Incorrect Answers
Reference resource symbols and their IDs instead of copying fixed resource-ID strings. A separate source case supports that approach when: A deployment fails after a dependent resource was renamed; the workspace refers to a literal outdated resource ID. The supporting rationale or observable result is: Symbolic dependencies are resolved from the current declaration and reduce mismatch when names or scopes change. This question describes a different issue: A deployment needs to pass the newly created Azure ML workspace resource identifier to a subsequent GitHub Actions job. Address it through Define a Bicep output for the workspace resource ID and consume the deployment output, with the required justification or evidence: Explicit outputs transmit computed resource identifiers without fragile scraping of deployment logs or copied portal values.
Use approved secret parameters and Key Vault or identity-based access rather than checked-in secrets. This is useful for the distinct issue: A Bicep deployment stores a storage-account key in plain text as a template parameter committed to Git. The relevant technical rationale or evidence for that issue is: Secrets should not enter source history; secure parameter handling and identities keep credentials out of published infrastructure code. Here the reported issue is: A deployment needs to pass the newly created Azure ML workspace resource identifier to a subsequent GitHub Actions job. The relevant response is: Define a Bicep output for the workspace resource ID and consume the deployment output. The first result cannot verify this different correction: Explicit outputs transmit computed resource identifiers without fragile scraping of deployment logs or copied portal values.
Use Azure deployment what-if against the target scope and parameter set. It addresses another case: A team must preview resource changes before a production Azure ML workspace update. For that case, the distinguishing justification or acceptance check is: What-if compares proposed resource changes with current state, offering reviewers a preview before applying the actual deployment. The present case instead states: A deployment needs to pass the newly created Azure ML workspace resource identifier to a subsequent GitHub Actions job. It calls for Define a Bicep output for the workspace resource ID and consume the deployment output. Showing success for the other case would not establish: Explicit outputs transmit computed resource identifiers without fragile scraping of deployment logs or copied portal values.