Conditional resources let one template support environment-specific needs. In this case, a release pipeline has different deployment parameters for test and production. “Guard the optional resource with an appropriate condition” would not satisfy that requirement; the supported action is “Use environment-specific parameter files or controlled pipeline inputs”. Separating parameters from reusable source reduces hard-coded drift.

Conditional deployment can include or omit resources based on parameters. In this case, a release pipeline has different deployment parameters for test and production. “Use conditional resource deployment with an if expression” would not satisfy that requirement; the supported action is “Use environment-specific parameter files or controlled pipeline inputs”. Separating parameters from reusable source reduces hard-coded drift.

Language validation catches many parameter and property errors early. In this case, a release pipeline has different deployment parameters for test and production. “Resolve compile-time type diagnostics before deployment” would not satisfy that requirement; the supported action is “Use environment-specific parameter files or controlled pipeline inputs”. Separating parameters from reusable source reduces hard-coded drift.

Azure CLI deployment commands apply declarative definitions without interactive UI steps. In this case, a resource must be created only when a feature flag is enabled. “Invoke a scoped az deployment command with a Bicep file and parameters” would not satisfy that requirement; the supported action is “Use conditional resource deployment with an if expression”. Conditional deployment can include or omit resources based on parameters.

Incremental deployments manage described resources without indiscriminately removing omitted ones. In this case, a resource must be created only when a feature flag is enabled. “Use safe incremental deployment semantics and inspect what-if changes” would not satisfy that requirement; the supported action is “Use conditional resource deployment with an if expression”. Conditional deployment can include or omit resources based on parameters.

Separating parameters from reusable source reduces hard-coded drift. In this case, a resource must be created only when a feature flag is enabled. “Use environment-specific parameter files or controlled pipeline inputs” would not satisfy that requirement; the supported action is “Use conditional resource deployment with an if expression”. Conditional deployment can include or omit resources based on parameters.

Separating parameters from reusable source reduces hard-coded drift. In this case, a template always creates an expensive test appliance regardless of environment. “Use environment-specific parameter files or controlled pipeline inputs” would not satisfy that requirement; the supported action is “Guard the optional resource with an appropriate condition”. Conditional resources let one template support environment-specific needs.

Azure CLI deployment commands apply declarative definitions without interactive UI steps. In this case, a template always creates an expensive test appliance regardless of environment. “Invoke a scoped az deployment command with a Bicep file and parameters” would not satisfy that requirement; the supported action is “Guard the optional resource with an appropriate condition”. Conditional resources let one template support environment-specific needs.

Incremental deployments manage described resources without indiscriminately removing omitted ones. In this case, a template always creates an expensive test appliance regardless of environment. “Use safe incremental deployment semantics and inspect what-if changes” would not satisfy that requirement; the supported action is “Guard the optional resource with an appropriate condition”. Conditional resources let one template support environment-specific needs.

Conditional deployment can include or omit resources based on parameters. In this case, a resource is redeployed with a new tag, and the team wants to avoid deleting unrelated resources. “Use conditional resource deployment with an if expression” would not satisfy that requirement; the supported action is “Use safe incremental deployment semantics and inspect what-if changes”. Incremental deployments manage described resources without indiscriminately removing omitted ones.

Dynamic references follow provisioned resources instead of stale pasted identifiers. In this case, a resource is redeployed with a new tag, and the team wants to avoid deleting unrelated resources. “Use a deployment parameter or reference derived from actual resource outputs” would not satisfy that requirement; the supported action is “Use safe incremental deployment semantics and inspect what-if changes”. Incremental deployments manage described resources without indiscriminately removing omitted ones.

Module outputs and references make dependencies explicit and avoid hard-coded IDs. In this case, a resource is redeployed with a new tag, and the team wants to avoid deleting unrelated resources. “Pass a typed output or symbolic resource reference into the consuming module” would not satisfy that requirement; the supported action is “Use safe incremental deployment semantics and inspect what-if changes”. Incremental deployments manage described resources without indiscriminately removing omitted ones.

Module outputs and references make dependencies explicit and avoid hard-coded IDs. In this case, a team plans a destructive complete-state update without examining its scope. “Pass a typed output or symbolic resource reference into the consuming module” would not satisfy that requirement; the supported action is “Review planned changes and removal impact using what-if or deployment stacks”. Removal semantics require a deliberate preview and scope assessment.

Conditional deployment can include or omit resources based on parameters. In this case, a team plans a destructive complete-state update without examining its scope. “Use conditional resource deployment with an if expression” would not satisfy that requirement; the supported action is “Review planned changes and removal impact using what-if or deployment stacks”. Removal semantics require a deliberate preview and scope assessment.

Dynamic references follow provisioned resources instead of stale pasted identifiers. In this case, a team plans a destructive complete-state update without examining its scope. “Use a deployment parameter or reference derived from actual resource outputs” would not satisfy that requirement; the supported action is “Review planned changes and removal impact using what-if or deployment stacks”. Removal semantics require a deliberate preview and scope assessment.

Version pinning avoids unplanned behavior changes during deployment. In this case, an application team needs a storage account's resource ID in a dependent module. “Pin reviewed module versions in release deployments” would not satisfy that requirement; the supported action is “Pass a typed output or symbolic resource reference into the consuming module”. Module outputs and references make dependencies explicit and avoid hard-coded IDs.

Incremental deployments manage described resources without indiscriminately removing omitted ones. In this case, an application team needs a storage account's resource ID in a dependent module. “Use safe incremental deployment semantics and inspect what-if changes” would not satisfy that requirement; the supported action is “Pass a typed output or symbolic resource reference into the consuming module”. Module outputs and references make dependencies explicit and avoid hard-coded IDs.

Declarative module reuse allows different environments to share tested infrastructure logic. In this case, an application team needs a storage account's resource ID in a dependent module. “Version the common module source while supplying tenant-specific parameter sets” would not satisfy that requirement; the supported action is “Pass a typed output or symbolic resource reference into the consuming module”. Module outputs and references make dependencies explicit and avoid hard-coded IDs.

Incremental deployments manage described resources without indiscriminately removing omitted ones. In this case, an app template contains a stale manually copied storage resource ID. “Use safe incremental deployment semantics and inspect what-if changes” would not satisfy that requirement; the supported action is “Use a deployment parameter or reference derived from actual resource outputs”. Dynamic references follow provisioned resources instead of stale pasted identifiers.

Declarative module reuse allows different environments to share tested infrastructure logic. In this case, an app template contains a stale manually copied storage resource ID. “Version the common module source while supplying tenant-specific parameter sets” would not satisfy that requirement; the supported action is “Use a deployment parameter or reference derived from actual resource outputs”. Dynamic references follow provisioned resources instead of stale pasted identifiers.

Removal semantics require a deliberate preview and scope assessment. In this case, an app template contains a stale manually copied storage resource ID. “Review planned changes and removal impact using what-if or deployment stacks” would not satisfy that requirement; the supported action is “Use a deployment parameter or reference derived from actual resource outputs”. Dynamic references follow provisioned resources instead of stale pasted identifiers.

Module outputs and references make dependencies explicit and avoid hard-coded IDs. In this case, a platform engineer wants centrally reusable definitions but independent parameters per tenant. “Pass a typed output or symbolic resource reference into the consuming module” would not satisfy that requirement; the supported action is “Version the common module source while supplying tenant-specific parameter sets”. Declarative module reuse allows different environments to share tested infrastructure logic.

Dynamic references follow provisioned resources instead of stale pasted identifiers. In this case, a platform engineer wants centrally reusable definitions but independent parameters per tenant. “Use a deployment parameter or reference derived from actual resource outputs” would not satisfy that requirement; the supported action is “Version the common module source while supplying tenant-specific parameter sets”. Declarative module reuse allows different environments to share tested infrastructure logic.

Incremental deployments manage described resources without indiscriminately removing omitted ones. In this case, a platform engineer wants centrally reusable definitions but independent parameters per tenant. “Use safe incremental deployment semantics and inspect what-if changes” would not satisfy that requirement; the supported action is “Version the common module source while supplying tenant-specific parameter sets”. Declarative module reuse allows different environments to share tested infrastructure logic.

Module outputs and references make dependencies explicit and avoid hard-coded IDs. In this case, a shared module change breaks production when a floating version is updated. “Pass a typed output or symbolic resource reference into the consuming module” would not satisfy that requirement; the supported action is “Pin reviewed module versions in release deployments”. Version pinning avoids unplanned behavior changes during deployment.

Dynamic references follow provisioned resources instead of stale pasted identifiers. In this case, a shared module change breaks production when a floating version is updated. “Use a deployment parameter or reference derived from actual resource outputs” would not satisfy that requirement; the supported action is “Pin reviewed module versions in release deployments”. Version pinning avoids unplanned behavior changes during deployment.

Removal semantics require a deliberate preview and scope assessment. In this case, a shared module change breaks production when a floating version is updated. “Review planned changes and removal impact using what-if or deployment stacks” would not satisfy that requirement; the supported action is “Pin reviewed module versions in release deployments”. Version pinning avoids unplanned behavior changes during deployment.

Managed disk performance depends on SKU, provisioned performance and VM limits. In this case, a Windows VM's OS disk has insufficient capacity for application binaries. “Choose a supported managed disk performance tier or SKU for the workload” would not satisfy that requirement; the supported action is “Resize the managed OS disk and extend the guest partition or filesystem”. Disk expansion involves both Azure disk capacity and guest OS volume recognition.

Disk-side improvements cannot exceed the VM's supported performance ceiling. In this case, a Windows VM's OS disk has insufficient capacity for application binaries. “The VM size's supported aggregate disk IOPS and throughput limits” would not satisfy that requirement; the supported action is “Resize the managed OS disk and extend the guest partition or filesystem”. Disk expansion involves both Azure disk capacity and guest OS volume recognition.

VM resizing depends on available sizes, capacity and possible restart/deallocation. In this case, a Windows VM's OS disk has insufficient capacity for application binaries. “Resize to a suitable VM SKU after checking region and hardware availability” would not satisfy that requirement; the supported action is “Resize the managed OS disk and extend the guest partition or filesystem”. Disk expansion involves both Azure disk capacity and guest OS volume recognition.

Disk-side improvements cannot exceed the VM's supported performance ceiling. In this case, an admin increases a managed disk size but the guest still shows old partition capacity. “The VM size's supported aggregate disk IOPS and throughput limits” would not satisfy that requirement; the supported action is “Extend the partition and filesystem inside the guest”. Azure-side resize does not automatically guarantee guest volume expansion.

Managed disk performance depends on SKU, provisioned performance and VM limits. In this case, an admin increases a managed disk size but the guest still shows old partition capacity. “Choose a supported managed disk performance tier or SKU for the workload” would not satisfy that requirement; the supported action is “Extend the partition and filesystem inside the guest”. Azure-side resize does not automatically guarantee guest volume expansion.

Not every VM family and size is supported or currently available everywhere. In this case, an admin increases a managed disk size but the guest still shows old partition capacity. “Available VM sizes and regional capacity constraints” would not satisfy that requirement; the supported action is “Extend the partition and filesystem inside the guest”. Azure-side resize does not automatically guarantee guest volume expansion.