Why security posture matters in Azure - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable Azure Security Center's default policy.

Azure

az security [1] enable

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

Aconfiguration

Bsettings

Cpolicy

Dmanagement

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'configuration' instead of 'policy' will not enable security rules.

Using 'management' or 'settings' commands are invalid here.

The policy command enables Azure Security Center's default security policies, which help improve your security posture.

2fill in blank

medium

Complete the code to list all security recommendations in Azure Security Center.

Azure

az security [1] list

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

Arecommendations

Balerts

Cpolicies

Dconfigurations

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'alerts' lists current security alerts, not recommendations.

Using 'policies' shows policies, not improvement suggestions.

The recommendations command lists security improvement suggestions to enhance your security posture.

3fill in blank

hard

Fix the error in the command to show the security posture score.

Azure

az security [1] show --query 'securityScore'

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

Asecure-score

Bposture

Cconfiguration

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'posture' or 'configuration' commands will cause errors.

Repeating 'secure-score' with wrong spelling causes failure.

The correct command uses secure-score to show the security posture score in Azure Security Center.

4fill in blank

hard

Fill both blanks to create a policy assignment for security baseline.

Azure

az policy assignment create --name [1] --policy [2]

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

AsecureBaselineAssignment

BdefaultSecurityPolicy

C/providers/Microsoft.Authorization/policyDefinitions/SecurityBaseline

D/providers/Microsoft.Authorization/policyDefinitions/DefaultSecurityPolicy

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'defaultSecurityPolicy' as assignment name is confusing.

Using wrong policy definition path causes deployment failure.

The assignment name is secureBaselineAssignment and the policy definition ID is the SecurityBaseline path.

5fill in blank

hard

Fill all three blanks to create a resource group and enable security auto provisioning.

Azure

az group create --name [1] --location [2]
az security auto-provisioning-setting create --name [3] --auto-provision "On" --resource-group [1]

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

AMySecurityGroup

Beastus

Cdefault

Dwestus

Attempts:

3 left

💡 Hint

Common Mistakes

Using inconsistent resource group names between commands.

Choosing a region not supported or misspelled.

The resource group is named MySecurityGroup, located in eastus, and the auto-provisioning setting is named default.