Home » Microsoft » AZ-400 » Which five actions should you perform in sequence?
DRAG DROP
You need to use Azure Automation State Configuration to manage the ongoing consistency of virtual machine configurations.
Which five actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
NOTE: More than one order of answer choices is correct. You will receive credit for any of the correct orders you select.
Select and Place:
Correct Answer:
Explanation/Reference:
Explanation:
Step 1: Assign the node configuration.
You create a simple DSC configuration that ensures either the presence or absence of the Web-Server Windows Feature (IIS), depending on how you assign nodes.
Step 2: Upload a configuration to Azure Automation State Configuration.
You import the configuration into the Automation account.
Step 3: Compiling a configuration into a node configuration
Compiling a configuration in Azure Automation
Before you can apply a desired state to a node, a DSC configuration defining that state must be compiled into one or more node configurations (MOF document), and placed on the Automation DSC Pull Server.
Step 4: Onboard the virtual machines to Azure State Configuration
Onboarding an Azure VM for management with Azure Automation State Configuration
Step 5: Check the compliance status of the node.
Viewing reports for managed nodes. Each time Azure Automation State Configuration performs a consistency check on a managed node, the node sends a status report back to the pull server. You can view these reports on the page for that node.
On the blade for an individual report, you can see the following status information for the corresponding consistency check:
The report status — whether the node is "Compliant", the configuration "Failed", or the node is "Not Compliant" (when the node is in ApplyandMonitor mode and the machine is not in the desired state).
References: https://docs.microsoft.com/en-us/azure/automation/automation-dsc-getting-started
Node configuration are inside the *.ps1 file so the answer and explanation are correct.
configuration TestConfig
{
Node IsWebServer
{
WindowsFeature IIS
{
Ensure = ‘Present’
Name = ‘Web-Server’
IncludeAllSubFeature = $true
}
…
The whole problem of this question is that during the onboard step you do “Assign the node configuration”, but it is done as part of the onboarding step. You do not need to do it after onboarding, anyway you can change it.
Maybe that is the reason, why more than 1 order is correct.
Correct steps are as follows:
Step 1: Upload a configuration to Azure Automation State Configuration.
Step 2: Compiling a configuration into a node configuration.
Step 3: Onboard the virtual machines to Azure State Configuration.
Step 4: Assign the node configuration.
Step 5: Check the compliance status of the node.
The answer is correct as per the link.
https://docs.microsoft.com/en-us/azure/automation/automation-dsc-getting-started
Step 1: Assign the node configuration.
Step 2: Upload a configuration to Azure Automation State Configuration.
Step 3: Compiling a configuration into a node configuration.
Step 4: Onboard the virtual machines to Azure State Configuration.
Step 5: Check the compliance status of the node.