Question 390
A Bicep template includes production API credentials as plaintext parameter defaults in Git. The team can modify the relevant resource but must not broaden unrelated permissions or access. The team needs evidence that the source tree has no credential and deployment authenticates securely. What is the best next action for this Azure AI workload?
Explanation
Correct Answer
Parameter files and repository history are inappropriate stores for production credentials. After the change, the source tree has no credential and deployment authenticates securely.
Incorrect Answers
Provisioning the Foundry resource does not automatically grant data access to unrelated vaults.
A manual one-off edit is vulnerable to being reversed by the next declarative deployment. Parameter files and repository history are inappropriate stores for production credentials.
Declarative configuration makes deployment settings reproducible across approved environments.