How to automate SQL Server cumulative updates using Azure Update Manager on SQLVM?
Short answer
D Set Automated patching to Disable.
Question
Key Takeaways
The exam tests your understanding that Automated Patching and Azure Update Manager are mutually exclusive patching mechanisms, and you must disable the former before enabling the latter to avoid conflicts.
When migrating from Automated Patching to Azure Update Manager for a SQL Server IaaS VM, you must first disable the built-in Automated Patching feature to prevent update conflicts. This ensures the SQL Server IaaS Agent extension remains functional for Azure portal management while Azure Update Manager handles cumulative updates.
Common mistake: Many candidates choose to uninstall the SQL Server IaaS Agent extension (Option B), mistakenly believing it is responsible for Automated Patching. However, removing the IaaS Agent would break Azure portal management of the SQL instance entirely.
Expert Analysis
Why the Answer Is Correct
The correct answer is D: Set Automated patching to Disable. According to Microsoft documentation, you cannot use both Automated Patching and Azure Update Manager simultaneously because they are overlapping tools that may lead to failed updates. Disabling Automated Patching within the SQL Server IaaS Agent extension is the prerequisite step before onboarding the VM to Azure Update Manager for cumulative update deployment.
Why the Other Options Are Wrong
Option A (Install Azure Monitor Agent) and Option C (Install Log Analytics agent) are related to monitoring and diagnostics, not patch management. Option B (Uninstall the SQL Server IaaS Agent extension) is incorrect because the IaaS Agent is required for Azure portal management of the SQL Server instance; removing it would break portal management capabilities, which the question explicitly states must be maintained.
Community Comment Notes
Community consensus strongly supports Option D with 100% of votes. Comment [1] correctly explains that using both Automated Patching and Azure Update Manager simultaneously causes conflicts. Comment [3] provides the official documentation link and emphasizes the "choose only one option" principle for VM update tools, reinforcing the mutual exclusivity concept.
Official Reference
This link opens the official vendor documentation in a new tab.
Exam Strategy
When a question asks you to switch between two Azure management tools that perform similar functions, always look for the option that disables or removes the legacy tool first. Remember that overlapping management tools in Azure often cause conflicts, and Microsoft documentation consistently warns against using them simultaneously.
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
voodoo_sh 👍 2D - Set Automated patching to disable To automate the deployment of cumulative updates to SQL Server using Azure Update Manager, while ensuring that SQLVM1 can still be managed via the Azure portal, you should first disable Automated Patching. This is necessary because using both Automated Patching and Azure Update Manager simultaneously can lead to conflicts and unexpected behavior
-
2f5c7cd 👍 1 Answered Dhttps://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/automated-patching?view=azuresql Choose only one option to automatically update your VM as overlapping tools may lead to failed updates.
-
voodoo_sh 👍 1 Answered DD - Disable automated patching in SQL Iaas Agent extension
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All DP-300 Questions
Access 105 questions with complete answers and detailed explanations.
View Full DP-300 Practice Test →