Pass Your Microsoft AZ-104 Exam Easy!

The nearby action 'Extend the guest partition and filesystem into the new capacity' is associated with this separate need: an admin enlarged a managed disk in Azure, but the Windows guest still shows the old filesystem size. That is because cloud disk expansion does not always automatically grow the guest partition or filesystem. Here an application writes actively to a data disk that an admin wants to detach, so 'Extend the guest partition and filesystem into the new capacity' misses the fact that detaching an active filesystem risks unflushed data loss and application corruption. 'Quiesce writes, unmount safely and coordinate detach with application owner' is the more defensible action; confirm its behavior in the target service before calling the task complete.

'Verify guest device discovery, mount point, filesystem and permissions' solves another task because ARM attachment is only the infrastructure step; the guest must recognize and mount the volume correctly. For the situation where an application writes actively to a data disk that an admin wants to detach, this distractor misses the requirement that detaching an active filesystem risks unflushed data loss and application corruption. Unlike 'Verify guest device discovery, mount point, filesystem and permissions', 'Quiesce writes, unmount safely and coordinate detach with application owner' directly targets that requirement; its success must be confirmed at the authorized resource scope.

When a database VM's data volume is full while its operating system disk has space, the action 'Expand the correct managed data disk, then extend the guest volume if required' can be relevant: OS and data disks hold different filesystems; adding OS capacity may not fix database storage. For the different problem of an application writes actively to a data disk that an admin wants to detach, 'Expand the correct managed data disk, then extend the guest volume if required' misses the mechanism that detaching an active filesystem risks unflushed data loss and application corruption. Choosing 'Expand the correct managed data disk, then extend the guest volume if required' would address that other need, whereas 'Quiesce writes, unmount safely and coordinate detach with application owner' is intended to solve the stated condition.

'Increase the OS disk size on the single existing VM' fails the stated scenario where a critical service needs protection if an entire availability zone fails because more disk capacity does not create an independently available compute replica. The required multi-part resolution instead needs zones isolate facilities within a region; application load balancing and regional limits still matter, which 'Increase the OS disk size on the single existing VM' does not establish. Do not count 'Increase the OS disk size on the single existing VM' among the mandatory actions; confirm the specific service's effective permissions, network path, or deployment result before treating the design as complete.

'Place all VM replicas in one zone and rely on a health probe only' fails the stated scenario where a critical service needs protection if an entire availability zone fails because a common zonal outage would remove every backend, regardless of probe configuration. The required multi-part resolution instead needs zones isolate facilities within a region; application load balancing and regional limits still matter, which 'Place all VM replicas in one zone and rely on a health probe only' does not establish. Do not count 'Place all VM replicas in one zone and rely on a health probe only' among the mandatory actions; confirm the specific service's effective permissions, network path, or deployment result before treating the design as complete.

'Move all replicas to one availability zone with lower hourly cost' fails the stated scenario where a critical service needs protection if an entire availability zone fails because cost consolidation would recreate a common zonal failure domain. The required multi-part resolution instead needs zones isolate facilities within a region; application load balancing and regional limits still matter, which 'Move all replicas to one availability zone with lower hourly cost' does not establish. Do not count 'Move all replicas to one availability zone with lower hourly cost' among the mandatory actions; confirm the specific service's effective permissions, network path, or deployment result before treating the design as complete.

'Use only an availability set and claim protection from every zone outage' fails the stated scenario where a critical service needs protection if an entire availability zone fails because an availability set does not inherently distribute replicas across distinct availability zones. The required multi-part resolution instead needs zones isolate facilities within a region; application load balancing and regional limits still matter, which 'Use only an availability set and claim protection from every zone outage' does not establish. Do not count 'Use only an availability set and claim protection from every zone outage' among the mandatory actions; confirm the specific service's effective permissions, network path, or deployment result before treating the design as complete.

An availability set spreads eligible VMs across fault and update domains within its supported datacenter placement design; it does not itself provide placement across independent Azure availability zones or regions. Conflating update domains with zonal failure isolation would give the workload weaker resilience than expected. The scenario asks to correct that misconception, so differentiate availability sets from zonal placement and separate regional disaster recovery design.

When an administrator wants zonal placement for a VM size that is only offered in zone 1, the action 'Validate target VM SKU availability per zone before committing placement' can be relevant: not every size is supported in every region's zone; select compatible alternatives if necessary. For the different problem of a team assumes an availability set protects against loss of an entire region or zone, 'Validate target VM SKU availability per zone before committing placement' misses the mechanism that availability sets are not equivalent to multi-zone or multi-region redundancy. Choosing 'Validate target VM SKU availability per zone before committing placement' would address that other need, whereas 'Availability sets distribute fault/update domains within a datacenter context' is intended to solve the stated condition.

'Distribute compatible VMs across availability zones with redundant service design' applies to a different feature boundary because zones isolate facilities within a region; application load balancing and regional limits still matter. In the stated scenario where a team assumes an availability set protects against loss of an entire region or zone, 'Distribute compatible VMs across availability zones with redundant service design' does not satisfy the mechanism that availability sets are not equivalent to multi-zone or multi-region redundancy. The necessary action is 'Availability sets distribute fault/update domains within a datacenter context', which should be checked against this Azure resource's actual permissions and state.

An availability set helps distribute compatible VMs across fault and update domains, but it does not automatically distribute three independent instances across multiple distinct availability zones. Placing every VM in the same zone exposes all of them to that entire zone's failure, which violates the business requirement. For zonal fault tolerance, deploy the stateless VM replicas across separate supported availability zones, ensure any load-balancing design spans them appropriately and test loss of a single zone. The question explicitly excludes a scale set, so its alternative placement controls do not replace individual VM zonal decisions.

'Separate maintenance availability design from regional disaster recovery planning' applies to a different feature boundary because fault/update domains and availability zones do not automatically replace cross-region failover. In the stated scenario where an application has three replicated stateless VMs and should withstand one zonal outage, 'Separate maintenance availability design from regional disaster recovery planning' does not satisfy the mechanism that replicas sharing one zone would fail together; health-aware routing must include surviving zones. The necessary action is 'Deploy instances across distinct supported availability zones', which should be checked against this Azure resource's actual permissions and state.

The nearby action 'Validate target VM SKU availability per zone before committing placement' is associated with this separate need: an administrator wants zonal placement for a VM size that is only offered in zone 1. That is because not every size is supported in every region's zone; select compatible alternatives if necessary. Here an application has three replicated stateless VMs and should withstand one zonal outage, so 'Validate target VM SKU availability per zone before committing placement' misses the fact that replicas sharing one zone would fail together; health-aware routing must include surviving zones. 'Deploy instances across distinct supported availability zones' is the more defensible action; confirm its behavior in the target service before calling the task complete.

When a team assumes an availability set protects against loss of an entire region or zone, the action 'Availability sets distribute fault/update domains within a datacenter context' can be relevant: availability sets are not equivalent to multi-zone or multi-region redundancy. For the different problem of an application has three replicated stateless VMs and should withstand one zonal outage, 'Availability sets distribute fault/update domains within a datacenter context' misses the mechanism that replicas sharing one zone would fail together; health-aware routing must include surviving zones. Choosing 'Availability sets distribute fault/update domains within a datacenter context' would address that other need, whereas 'Deploy instances across distinct supported availability zones' is intended to solve the stated condition.

A Virtual Machine Scale Set simplifies management and scaling, but changing the resource type without changing failure-domain distribution does not eliminate the single-domain outage risk described. If all replicas still share one fault domain, one infrastructure failure can stop every instance regardless of autoscale or load-balancer configuration. The team must spread replicas over distinct supported fault domains or availability zones, and test routing to surviving healthy instances. A scale set with the same concentrated placement remains a single failure domain rather than the requested resilient topology.

Virtual network subnets define IP routing and security segmentation, not independent physical power, rack, or update failure domains. VMs can sit on different subnets and still depend on the same host/fault-domain infrastructure. The application here loses service whenever that one facility fails because all instances share its fault domain. Distribution must use supported availability-set fault domains or availability zones as appropriate, combined with health-aware load balancing. Separating only subnets leaves the original physical placement risk intact.

When a team assumes an availability set protects against loss of an entire region or zone, the action 'Availability sets distribute fault/update domains within a datacenter context' can be relevant: availability sets are not equivalent to multi-zone or multi-region redundancy. For the different problem of a load-balanced application loses service whenever one facility fails because every VM is in the same fault domain, 'Availability sets distribute fault/update domains within a datacenter context' misses the mechanism that a load balancer cannot compensate when every backend shares the same failure boundary. Choosing 'Availability sets distribute fault/update domains within a datacenter context' would address that other need, whereas 'Spread VM instances across independent fault or zone failure domains' is intended to solve the stated condition.

The nearby action 'Availability sets distribute fault/update domains within a datacenter context' is associated with this separate need: a team assumes an availability set protects against loss of an entire region or zone. That is because availability sets are not equivalent to multi-zone or multi-region redundancy. Here an administrator wants zonal placement for a VM size that is only offered in zone 1, so 'Availability sets distribute fault/update domains within a datacenter context' misses the fact that not every size is supported in every region's zone; select compatible alternatives if necessary. 'Validate target VM SKU availability per zone before committing placement' is the more defensible action; confirm its behavior in the target service before calling the task complete.

'Check OS, architecture, generation and disk/SKU compatibility for the target VM size' solves another task because an available SKU is not automatically compatible with the VM's image and boot requirements. For the situation where an administrator wants zonal placement for a VM size that is only offered in zone 1, this distractor misses the requirement that not every size is supported in every region's zone; select compatible alternatives if necessary. Unlike 'Check OS, architecture, generation and disk/SKU compatibility for the target VM size', 'Validate target VM SKU availability per zone before committing placement' directly targets that requirement; its success must be confirmed at the authorized resource scope.

When a critical service needs protection if an entire availability zone fails, the action 'Distribute compatible VMs across availability zones with redundant service design' can be relevant: zones isolate facilities within a region; application load balancing and regional limits still matter. For the different problem of an administrator wants zonal placement for a VM size that is only offered in zone 1, 'Distribute compatible VMs across availability zones with redundant service design' misses the mechanism that not every size is supported in every region's zone; select compatible alternatives if necessary. Choosing 'Distribute compatible VMs across availability zones with redundant service design' would address that other need, whereas 'Validate target VM SKU availability per zone before committing placement' is intended to solve the stated condition.

When an application has three replicated stateless VMs and should withstand one zonal outage, the action 'Deploy instances across distinct supported availability zones' can be relevant: replicas sharing one zone would fail together; health-aware routing must include surviving zones. For the different problem of a service needs continuous operation during planned host maintenance and disaster recovery from a regional outage, 'Deploy instances across distinct supported availability zones' misses the mechanism that fault/update domains and availability zones do not automatically replace cross-region failover. Choosing 'Deploy instances across distinct supported availability zones' would address that other need, whereas 'Separate maintenance availability design from regional disaster recovery planning' is intended to solve the stated condition.

'Availability sets distribute fault/update domains within a datacenter context' applies to a different feature boundary because availability sets are not equivalent to multi-zone or multi-region redundancy. In the stated scenario where a service needs continuous operation during planned host maintenance and disaster recovery from a regional outage, 'Availability sets distribute fault/update domains within a datacenter context' does not satisfy the mechanism that fault/update domains and availability zones do not automatically replace cross-region failover. The necessary action is 'Separate maintenance availability design from regional disaster recovery planning', which should be checked against this Azure resource's actual permissions and state.

The nearby action 'Distribute compatible VMs across availability zones with redundant service design' is associated with this separate need: a critical service needs protection if an entire availability zone fails. That is because zones isolate facilities within a region; application load balancing and regional limits still matter. Here a service needs continuous operation during planned host maintenance and disaster recovery from a regional outage, so 'Distribute compatible VMs across availability zones with redundant service design' misses the fact that fault/update domains and availability zones do not automatically replace cross-region failover. 'Separate maintenance availability design from regional disaster recovery planning' is the more defensible action; confirm its behavior in the target service before calling the task complete.

When a scale set needs a new golden image while preserving a path back to its last working image, the action 'Version the image and stage a tested rolling or controlled VMSS upgrade' can be relevant: image replacement can fail; record current and target versions before broad rollout. For the different problem of a service requires hundreds of interchangeable web-processing VMs with common image and lifecycle, 'Version the image and stage a tested rolling or controlled VMSS upgrade' misses the mechanism that scale sets orchestrate instance pools and scaling; individual VM handcrafting is harder to manage. Choosing 'Version the image and stage a tested rolling or controlled VMSS upgrade' would address that other need, whereas 'Use an Azure Virtual Machine Scale Set for managed fleets of uniform instances' is intended to solve the stated condition.

'Configure supported zone or fault-domain distribution for scale-set instances' applies to a different feature boundary because capacity planning should align placement and upgrade boundaries with the desired fault isolation. In the stated scenario where a service requires hundreds of interchangeable web-processing VMs with common image and lifecycle, 'Configure supported zone or fault-domain distribution for scale-set instances' does not satisfy the mechanism that scale sets orchestrate instance pools and scaling; individual VM handcrafting is harder to manage. The necessary action is 'Use an Azure Virtual Machine Scale Set for managed fleets of uniform instances', which should be checked against this Azure resource's actual permissions and state.

'Apply the configured instance upgrade/rolling policy to existing instances' solves another task because updating the scale-set model doesn't force every instance to adopt changes immediately under all policies. For the situation where a service requires hundreds of interchangeable web-processing VMs with common image and lifecycle, this distractor misses the requirement that scale sets orchestrate instance pools and scaling; individual VM handcrafting is harder to manage. Unlike 'Apply the configured instance upgrade/rolling policy to existing instances', 'Use an Azure Virtual Machine Scale Set for managed fleets of uniform instances' directly targets that requirement; its success must be confirmed at the authorized resource scope.

When a scale set reduces instances aggressively and drops long-running jobs, the action 'Use health checks, workload draining and safe scale-in policies' can be relevant: removing busy replicas without coordination can interrupt sessions and lose in-flight work. For the different problem of a service requires hundreds of interchangeable web-processing VMs with common image and lifecycle, 'Use health checks, workload draining and safe scale-in policies' misses the mechanism that scale sets orchestrate instance pools and scaling; individual VM handcrafting is harder to manage. Choosing 'Use health checks, workload draining and safe scale-in policies' would address that other need, whereas 'Use an Azure Virtual Machine Scale Set for managed fleets of uniform instances' is intended to solve the stated condition.

A schedule-only scale setting can be useful when business demand follows known daily or seasonal patterns. It does not respond to this application's actual latency and queue depth when traffic unexpectedly shifts outside the scheduled window. It can spend money on idle capacity or leave workers overloaded during an unscheduled surge. The requirement explicitly states that scaling must occur after sustained metric thresholds, so the administrator needs metric-based autoscale rules, not a fixed morning increase. Scheduling may be combined with separate autoscale profiles only if tested and approved for the same service.

Larger disks can help when a workload is capacity- or disk-performance-limited, but they do not create additional VMSS worker instances to drain a growing queue. The scenario identifies sustained queue length and application latency as desired scale triggers, not a lack of available disk capacity. Increasing storage may also require guest filesystem steps and incur charges without changing processing concurrency. Configure horizontal autoscale for the VM scale set using supported emitted metrics and bounded instance counts. Assess storage throughput separately if telemetry later shows that disk performance is the actual bottleneck.

An Azure Monitor alert can notify operators that a custom latency or queue metric exceeds a threshold, but an email action does not automatically modify the scale set's instance capacity. Manual intervention might arrive too late for the ten-minute response requirement and would not guarantee repeatable scale-in behavior or safety bounds. Metric-based autoscale rules explicitly define the scaling action, thresholds, capacity and cooldowns. Alerts remain valuable for investigating unusual scaling failures, cost or health, but they are complementary to—and not a substitute for—the required automated instance adjustments.

The nearby action 'Extend the guest partition and filesystem into the new capacity' is associated with this separate need: an admin enlarged a managed disk in Azure, but the Windows guest still shows the old filesystem size. That is because cloud disk expansion does not always automatically grow the guest partition or filesystem. Here a VM disk is enlarged and the team calls that scale-out, so 'Extend the guest partition and filesystem into the new capacity' misses the fact that horizontal scaling adds compute replicas; disk expansion is storage capacity vertical change. 'Use additional VM instances for horizontal scale-out, not a larger single disk' is the more defensible action; confirm its behavior in the target service before calling the task complete.

'Use Azure VM Backup rather than relying only on an isolated managed-disk snapshot' solves another task because VM backup manages recovery points, schedule and restore workflow; disk snapshots are not equivalent coverage. For the situation where a VM disk is enlarged and the team calls that scale-out, this distractor misses the requirement that horizontal scaling adds compute replicas; disk expansion is storage capacity vertical change. Unlike 'Use Azure VM Backup rather than relying only on an isolated managed-disk snapshot', 'Use additional VM instances for horizontal scale-out, not a larger single disk' directly targets that requirement; its success must be confirmed at the authorized resource scope.

'Use health checks, workload draining and safe scale-in policies' applies to a different feature boundary because removing busy replicas without coordination can interrupt sessions and lose in-flight work. In the stated scenario where a VM disk is enlarged and the team calls that scale-out, 'Use health checks, workload draining and safe scale-in policies' does not satisfy the mechanism that horizontal scaling adds compute replicas; disk expansion is storage capacity vertical change. The necessary action is 'Use additional VM instances for horizontal scale-out, not a larger single disk', which should be checked against this Azure resource's actual permissions and state.

Placement across availability zones or fault domains protects against infrastructure failures and helps distribute scale-set instances. It does not determine whether a busy VM is safe to terminate during autoscale scale-in. Here the failures occur while long-running worker jobs are active, so changing placement alone leaves the application-level data-loss risk unchanged. Use workload-aware scale-in design, instance protection when required, and termination notifications with an application drain or checkpoint procedure. Then verify that a chosen scale-in target stops accepting jobs before the instance is actually removed.

Azure Virtual Machine Scale Sets already manage the pool of virtual machines and support autoscale rules. Choosing the same service again does not address the observed loss of in-progress jobs as instances are deleted. The missing controls are termination awareness and workload coordination: use scheduled-event termination notification where supported, a bounded delay to drain or checkpoint work, and scale-in policy or instance protection to avoid selecting critical workers. Application health probes can inform other orchestration features but do not independently guarantee that a busy job has finished before deletion.

Adding compute replicas is horizontal scale-out and can help a system process more jobs during peaks, whereas increasing a single VM disk is a storage-capacity change. Neither action fixes the current hazard: the scale set already scales down, and the jobs are interrupted before their state is safely completed. A correct response needs termination-notification handling and application-level draining or idempotent checkpoint/retry behavior, with suitable scale-in policy and protection. A scale-out decision might reduce queue depth temporarily but would not guarantee safe deletion when the subsequent scale-in occurs.