An administrator is designing a deployment strategy for an Azure Virtual Machine Scale Set… — Microsoft Azure Administrator (AZ-104)

An administrator is designing a deployment strategy for an Azure Virtual Machine Scale Set (VMSS) named `VMSS1`. The scale set must meet the following requirements:
- Maximize application availability by distributing VM instances across multiple fault domains in a single region without using Availability Zones.
- Automate scaling based on average CPU utilization using Azure Monitor autoscale rules.
- Support the deployment of custom VM sizes within the same scale set.

The administrator configures the scale set to use Flexible orchestration mode and defines a virtual machine profile.

During testing, the administrator needs to roll out an updated OS image to the scale set. The update must be applied to all existing instances while maintaining application availability.

Which of the following actions should the administrator perform to meet these requirements? (Select TWO.)

Configure the `platformFaultDomainCount` property to a value greater than $1$ during the creation of the scale set.Answer
Manually apply the updated scale set model to the virtual machine instances in a staggered manner.Answer
C
Change the scale set upgrade policy to `Rolling` to automatically roll out the OS image update to instances in batches.
D
Set the scale set upgrade policy to `Automatic` so that existing instances are updated concurrently.
E
Configure the scale-in policy of the scale set to `OldestVM` to prioritize updating older instances first.

Answer

Configure the `platformFaultDomainCount` property to a value greater than

1

during the creation of the scale set, and manually apply the updated scale set model to the virtual machine instances in a staggered manner.

In Flexible orchestration mode, virtual machine scale sets only support the Manual upgrade policy for VM model updates. Therefore, to apply a new OS image or configuration change to existing instances, the administrator must manually apply the scale set model to the virtual machines. Applying the update in a staggered manner manually ensures that some instances remain online, satisfying the availability requirement. Furthermore, to distribute virtual machine instances across multiple fault domains in a single region without using Availability Zones, the `platformFaultDomainCount` property must be explicitly set to a value greater than

1

(such as

2

3

) at the time the scale set is created.

Step-by-Step Solution

Determine the orchestration mode and upgrade policy constraints.

Identify that `VMSS1` is configured with Flexible orchestration mode. In this mode, the upgrade policy is restricted to Manual. Automatic and Rolling upgrade policies are not supported.

This determines how the OS image update must be applied to the existing VM instances.

Determine how to apply the model update.

Since only the Manual upgrade policy is supported, the update must be manually applied to each instance. To maintain application availability, the update should be applied in a staggered or batched manner.

This satisfies the requirement of updating existing instances while maintaining application availability.

Determine how to distribute VM instances across multiple fault domains without Availability Zones in Flexible mode.

Configure the `platformFaultDomainCount` property to a value greater than

1

(e.g.,

2

3

depending on the region) during scale set creation.

This property must be set at creation time and cannot be modified later. Setting it greater than

1

ensures VMs are spread across separate physical hardware racks.

Key Concept

Azure VMSS Flexible Orchestration Mode Upgrade Policies and Fault Domain Configurations

Estimated Time:3m 0s

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic