Why identity management is foundational in Azure - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new Azure Active Directory user.

Azure

az ad user create --display-name "John Doe" --user-principal-name [e-mail] --password [1]

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

A123456

Badmin

Cjohn.doe

DPassword123!

Attempts:

3 left

💡 Hint

Common Mistakes

Using a username instead of a password.

Using a weak password that Azure rejects.

The password must be strong and meet Azure AD requirements. "Password123!" is a valid strong password.

2fill in blank

medium

Complete the code to assign the 'Reader' role to a user on a resource group.

Azure

az role assignment create --assignee [e-mail] --role [1] --resource-group MyResourceGroup

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

AOwner

BContributor

CReader

DUser Access Administrator

Attempts:

3 left

💡 Hint

Common Mistakes

Assigning 'Owner' or 'Contributor' roles when only read access is needed.

Using incorrect role names.

The 'Reader' role allows read-only access to resources, which is often assigned for monitoring or auditing.

3fill in blank

hard

Fix the error in the command to enable multi-factor authentication (MFA) for a user.

Azure

az ad user update --id [e-mail] --[1] true

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

Astrong-authentication-required

Bforce-mfa

Cmfa-enabled

Denable-mfa

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent parameters like 'enable-mfa'.

Confusing parameter names.

The correct parameter to require MFA is '--strong-authentication-required'.

4fill in blank

hard

Fill both blanks to create a service principal with contributor role and assign it to a subscription.

Azure

az ad sp create-for-rbac --name [1] --role [2] --scopes /subscriptions/00000000-0000-0000-0000-000000000000

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

AMyAppSP

BReader

CContributor

DAdmin

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Reader' role when write access is needed.

Using invalid role names like 'Admin'.

'MyAppSP' is a valid name for the service principal. 'Contributor' role grants permissions to manage resources.

5fill in blank

hard

Fill all three blanks to create a conditional access policy that requires MFA for users in group 'Admins'.

Azure

az ad conditional-access policy create --display-name [1] --state enabled --conditions "[2]" --grant-controls "[3]"

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

A"AdminsGroupCondition"

B"users/groups eq 'Admins'"

C"mfaRequired"

D"requireMfa"

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect condition syntax.

Using wrong grant control names.

Omitting quotes around strings.

The policy needs a name, a condition targeting the 'Admins' group, and a grant control requiring MFA.