← AZ-104: Azure administration in production
13 / 17 · 40 MIN

Templates, modules and intended state

Review declarative changes, incomplete analysis and deployment concurrency.

Resources and properties

In an incremental deployment, existing resources omitted from the template remain. That rule does not mean omitted properties on a declared resource are preserved. Declare that resource’s complete intended state, including nondefault values.

Splitting properties across concurrent partial definitions does not automatically create a safe merge. Compare published configuration with application requirements before accepting a change as small or harmless.

Interpreting what-if

Compilation checks the definition; what-if compares predicted environmental changes. Neither alone proves application behavior. An unresolved expression can prevent analysis of a resource or module.

In that case, absence of displayed differences is not evidence of equality. Record the scope actually compared and resolve the dependency preventing analysis. Filtering output does not remove the resource from the actual deployment.

Execution identity

A Bicep module represents a nested deployment. Concurrent executions using the same fixed name at the same scope can interfere with observed outputs. The symbolic name in the file is different from remote deployment identity.

Use distinct execution names or generated names while retaining stable resource identity where intended. Isolating execution does not require indiscriminately duplicating infrastructure.

Migration and review exercise

Changing location in a template does not transport an existing VM to another region. Plan target resources, data, networking, dependencies and transition. In the exercise, a pipeline publishes a template with missing properties, an unanalyzed module and a shared name.

Produce three independent decisions: complete declared state, recover the omitted comparison and prevent execution collision. Then assess functional acceptance and recovery according to change risk.

IN PRACTICE

Two teams receive storage outputs mixed between concurrent deployments. Record each deployment’s scope and name; correct execution identity before using outputs to authorize publication.

Common pitfalls

Avoid treating incremental as a property patch, omitted results as successful comparison, and module name as a mere comment.

Related topics: Machines, disks and effective capacity · Containers: repetition, revisions and promotion

Take this idea with you

Review should connect definition, remote state and execution identity to acceptance criteria.

Create account

References

Azure is a trademark of the Microsoft group of companies. bigsavant.com is an independent preparation platform and is not affiliated with, associated with, sponsored, authorised or endorsed by Microsoft. Content and questions are original, are not official exam questions, and completing our tests does not award or guarantee any certification. Names are used only to identify the subject. All other trademarks belong to their respective owners.