An Azure VM scale set (VMSS1) hosts a stateful web application (WebApp1) that is deployed via the Custom Script extension. The deployment script is stored in an Azure Storage account (sa1). You will make a minor UI change and run limited user testing of the new version on VMSS1. Which three actions should you perform?

To deploy a minor UI change and test it, you need to update the deployment script and trigger its execution on the VMSS. Uploading an updated custom script file to sa1 ensures the latest application version is available. Modifying the Custom Script extension settings on VMSS1 (e.g., by changing the fileUris or commandToExecute or updating the protectedSettings to include a new version number) forces the extension to re-run on existing instances, pulling the new script. Updating the configuration of a virtual machine instance in VMSS1 (e.g., by performing a manual reimage or upgrade) will also trigger the Custom Script extension to re-run on that specific instance, applying the changes. Redeploying VMSS1 is too drastic for a minor UI change and would cause unnecessary downtime. Modifying load balancer settings is irrelevant to deploying application updates.