Question 440
A production Bicep change could remove a private endpoint, and the security team wants review before application. What should run first?
Explanation
Correct Answer
What-if shows planned resource changes for review before an infrastructure update affects service network controls.
Incorrect Answers
Deploy the Foundry platform from version-controlled Bicep infrastructure definitions. A separate source case supports that approach when: A platform team repeatedly provisions Foundry projects manually, causing inconsistent tags and identity settings. The supporting rationale or observable result is: Declarative templates make project resources and settings reproducible across multiple environments and reviewer-approved releases. This question describes a different issue: A production Bicep change could remove a private endpoint, and the security team wants review before application. Address it through Execute a deployment what-if preview with the exact target parameters, with the required justification or evidence: What-if shows planned resource changes for review before an infrastructure update affects service network controls.
Keep reusable Bicep modules with approved environment-specific region and model parameters. This is useful for the distinct issue: Different regions require different model deployment configurations but the team wants one shared infrastructure source. The relevant technical rationale or evidence for that issue is: Parameter files separate permitted environment variations from the centrally reviewed provisioning logic. Here the reported issue is: A production Bicep change could remove a private endpoint, and the security team wants review before application. The relevant response is: Execute a deployment what-if preview with the exact target parameters. The first result cannot verify this different correction: What-if shows planned resource changes for review before an infrastructure update affects service network controls.
Declare mandatory resource tags and naming conventions in provisioning modules. It addresses another case: A new Foundry project is deployed without the expected cost center and owner information. For that case, the distinguishing justification or acceptance check is: Consistent metadata supports cost attribution and operational ownership across automatically created projects. The present case instead states: A production Bicep change could remove a private endpoint, and the security team wants review before application. It calls for Execute a deployment what-if preview with the exact target parameters. Showing success for the other case would not establish: What-if shows planned resource changes for review before an infrastructure update affects service network controls.