Question 610
Two independent deployments of the same Bicep module target one resource group simultaneously using the same hard-coded nested deployment name. One deployment overwrites the other's operation history. What should the author consider?
Explanation
Correct Answer
Nested deployment name collisions can interfere with concurrent deployment records even if resource declarations themselves differ.
Incorrect Answers
A ReadOnly lock would restrict writes and cannot eliminate collisions of nested deployment names among concurrent runs.
Broad tenant privilege does not resolve a concurrency collision on a module deployment resource name.
Bicep modules require a deployment name and valid module declaration.