Network Watcher for diagnostics in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable Network Watcher in a specific Azure region.

Azure

az network watcher configure --locations [1] --enabled true

Drag options to blanks, or click blank then click option'

Aeastus

Bwestus2

Ccentralus

Dnorthcentralus

Attempts:

3 left

💡 Hint

Common Mistakes

Using an invalid or misspelled region name.

Omitting the --locations parameter.

The --locations parameter specifies the Azure region where Network Watcher is enabled. Here, westus2 is used as an example region.

2fill in blank

medium

Complete the code to start a packet capture session on a VM's network interface.

Azure

az network watcher packet-capture create --resource-group MyResourceGroup --vm [1] --name MyPacketCapture --time-limit 60

Drag options to blanks, or click blank then click option'

AMyVirtualMachine

BMyNetworkInterface

CMyResourceGroup

DMyStorageAccount

Attempts:

3 left

💡 Hint

Common Mistakes

Using the network interface name instead of the VM name.

Using the resource group or storage account name incorrectly.

The --vm parameter requires the name of the virtual machine where the packet capture will run.

3fill in blank

hard

Fix the error in the command to check IP flow verify between source and destination.

Azure

az network watcher [1] --resource-group MyResourceGroup --vm MyVM --direction Outbound --local-port 80 --remote-port 443 --protocol Tcp

Drag options to blanks, or click blank then click option'

Apacket-capture

Bshow-topology

Cip-flow-verify

Dflow-log

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'show-topology' which only displays network topology.

Using 'packet-capture' which starts packet capture sessions.

The ip-flow-verify command checks if traffic is allowed or denied between source and destination IP addresses and ports.

4fill in blank

hard

Fill both blanks to create a flow log for a Network Security Group (NSG) with logging enabled and retention set.

Azure

az network watcher flow-log create --resource-group MyResourceGroup --nsg [1] --enabled [2] --retention 7

Drag options to blanks, or click blank then click option'

AMyNSG

Btrue

Cfalse

DMyVM

Attempts:

3 left

💡 Hint

Common Mistakes

Using a VM name instead of NSG name.

Setting enabled to false which disables logging.

The --nsg parameter requires the NSG name, and --enabled should be set to true to activate flow logging.

5fill in blank

hard

Fill all three blanks to list all Network Watcher resources in a subscription filtered by location and status.

Azure

az network watcher list --query "[?location=='[1]' && provisioningState=='[2]'].[3]"

Drag options to blanks, or click blank then click option'

Aeastus

BSucceeded

Cname

Dwestus

Attempts:

3 left

💡 Hint

Common Mistakes

Using an incorrect location string.

Using a provisioning state other than 'Succeeded'.

Selecting a property that does not exist.

The query filters Network Watchers by location and provisioningState, then selects the name property to list their names.