Previous

Next

Summary and cleanup

Completed

You've created a new Linux virtual machine, changed its size, stopped and started it, and updated the configuration with the Azure CLI.

Clean up

The sandbox automatically cleans up your resources when you're finished with this module.

When you're working in your own subscription, it's a good idea at the end of a project to identify whether you still need the resources you created. Resources that you leave running can cost you money. You can delete resources individually or delete the resource group to delete the entire set of resources.

Additional resources

• Azure CLI overview
• Azure CLI command reference

Check your knowledge

1.

Suppose you're an administrator of several Azure virtual machines. You get a text message indicating some problems with your VMs. You are at a friend’s house and only have your tablet with you. True or false: you'll still be able to access the Azure CLI using the tablet, even though you can't install the CLI on it.

True

False

2.

Suppose you have a script that creates several VMs with different images. When the script issues the command to create the first VM you don't want to block the script while the VM is created, instead you want the script to immediately move on to the next command. What is the best way to do this?

Add the '--async' argument to your create command.

Use the ampersand (&) to run the process in the background.

Add the '--no-wait' argument to your create command.

3.

Most Azure commands return JSON by default. Sometimes this dataset can be large, which makes it difficult to read and tricky to use the result of one command as input to another command. What can you use with Azure CLI to filter the results to get only the data that you need?

You can use the '--query' argument.

You can use the '--filter' argument.

You can pipe the results to a JSON parsing utility and use filtering capability there.

You must answer all questions before checking your work.

Continue