Exam AZ-500 topic 3 question 58 discussion

Right ans. Update Management allows you to target a dynamic group of Azure or non-Azure VMs for update deployments. A dynamic group is defined by a query that Azure Automation evaluates at deployment time.

C is the right answer, sure. I use in my work

To meet the requirements, you need to use a dynamic group query. This is because: Automatically applies updates to VM1 and VM2: When configuring Update Management in Azure Automation, you can target virtual machines for update deployments. The dynamic group query allows you to automatically include VMs, and as new Windows Server 2019 VMs are added, they will be automatically included in the update deployment without requiring manual intervention. Automatically adds any new Windows Server 2019 virtual machines to Update1: By using a dynamic group query, new virtual machines that meet the criteria of being Windows Server 2019 will automatically be added to the group, which will then be included in the update deployment. A dynamic group query can automatically group VMs based on specific criteria such as operating system or other properties.

Answer C. Update Management allows you to target a dynamic group of Azure or non-Azure VMs for update deployments. Using a dynamic group keeps you from having to edit your deployment to update machines. A dynamic group is defined by a query that Azure Automation evaluates at deployment time. https://learn.microsoft.com/en-us/azure/automation/update-management/configure-groups

C. a dynamic group query

The answer is C. While a dynamic security group would be applicable in many cases in this case Update Management has it own Dynamic Group capabilities. See the article: https://learn.microsoft.com/en-us/azure/automation/update-management/configure-groups

C Define dynamic groups for Azure machines When defining a dynamic group query for Azure machines, you can use the following items to populate the dynamic group: Subscription Resource groups Locations Tags

B. a security group that has a Membership type of Dynamic Device To ensure that Update1 automatically applies updates to VM1 and VM2 and also automatically includes any new Windows Server 2019 virtual machines, you should use a dynamic group with a Membership type of Dynamic Device. A dynamic group is a feature of Azure Automation Update Management that allows you to create groups of devices based on dynamic queries. By using a dynamic query, you can automatically include devices that match specific criteria. In this case, you would set up a dynamic query that selects Windows Server 2019 virtual machines, and any new virtual machines that meet this criterion would be automatically added to the group.

C is the answer. https://learn.microsoft.com/en-us/azure/automation/update-management/configure-groups Update Management allows you to target a dynamic group of Azure or non-Azure VMs for update deployments. Using a dynamic group keeps you from having to edit your deployment to update machines.

C. a dynamic group query

C seems the right answer according to the link posted; "When defining a dynamic group query for Azure machines, you can use the following items to populate the dynamic group: Subscription, Resource groups, Locations, Tags."

There has to be more to the question as we have to make sure all future Server 2019 vms are included. The only attributes we can query against include: Subscription Resource Groups Locations Tags

Correta Letra C - CONSulta. A letra B esta incorreta Porque se tiver um grupo de seguranca dinamico de dispositivo e usar a tag devicetypeOS ele retonar apenas se WINDOWS idependete se a maquina e windows server 2016, 2019 e no anunciado ele que WINDOWS SEVER 2019.

Clearly Dynamic group is the answer.

# IN EXAM - 3/6/2022 (online). Lot of new questions. Good luck !

I am really not sure whether the suggested C is correct. It appears to me you can't define computer groups based on OS. "When defining a dynamic group query for Azure machines, you can use the following items to populate the dynamic group: Subscription / Resource groups / Locations / Tags " Instead check the prereqs to enable Update management. You will need: 1. Automation account 2. Log Analytics Workspace And in your LAW there you should define the targeting to what VMs the updated shall be applied. See: https://docs.microsoft.com/en-us/azure/automation/update-management/scope-configuration Thus I am tempted to choose D (i.e. Kusto).

correct