Why AD management is essential for sysadmins in PowerShell - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to list all users in Active Directory.

PowerShell

Get-ADUser -Filter [1]

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

A*

BName

CUser

DAll

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'All' or 'User' instead of '*' causes errors.

The -Filter * parameter retrieves all users from Active Directory.

2fill in blank

medium

Complete the code to create a new Active Directory user named 'JohnDoe'.

PowerShell

New-ADUser -Name 'JohnDoe' -AccountPassword (ConvertTo-SecureString [1] -AsPlainText -Force) -Enabled $true

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

A'password123'

B'Password!'

C'123456'

D'adminpass'

Attempts:

3 left

💡 Hint

Common Mistakes

Using weak passwords causes creation failure.

The password must be strong; 'Password!' meets complexity requirements.

3fill in blank

hard

Fix the error in the code to disable a user account named 'JaneSmith'.

PowerShell

Disable-ADAccount -Identity [1]

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

AJaneSmith

BUser.JaneSmith

Cjane.smith

D'JaneSmith'

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting quotes causes errors.

The -Identity parameter requires the username as a string, so quotes are needed.

4fill in blank

hard

Fill both blanks to get all enabled users whose name starts with 'A'.

PowerShell

Get-ADUser -Filter "[1] -and Enabled -eq [2]"

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

AName -like 'A*'

BName -eq 'A*'

CName -contains 'A'

DTrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using -eq with wildcard does not work as expected.

The filter uses Name -like 'A*' to match names starting with 'A' and checks if Enabled is True.

5fill in blank

hard

Fill all three blanks to create a new user with a given name, surname, and enable the account.

PowerShell

New-ADUser -Name 'Alice Smith' -GivenName [1] -Surname [2] -AccountPassword (ConvertTo-SecureString 'Password!' -AsPlainText -Force) -Enabled [3]

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

A'Alice'

B'Smith'

C$true

D$false

Attempts:

3 left

💡 Hint

Common Mistakes

Using $false disables the account.

Use 'Alice' for given name, 'Smith' for surname, and $true to enable the account.

Practice

1. Why is Active Directory (AD) management important for system administrators?

easy

A. It helps control user access to network resources.

B. It allows users to install any software they want.

C. It slows down network performance.

D. It removes all security settings automatically.

Solution

1. Step 1: Understand AD's role in access control

   Active Directory manages who can access files, printers, and other resources on a network.

2. Step 2: Recognize sysadmin responsibilities

   Sysadmins use AD to set permissions and keep the network secure and organized.

3. Final Answer:

   It helps control user access to network resources. -> Option A

4. Quick Check:

   AD controls access = A [OK]

Hint: AD controls access rights for users and devices [OK]

Common Mistakes:

• Thinking AD slows down the network
• Believing AD removes security settings
• Assuming AD lets users install any software

2. Which PowerShell cmdlet is used to create a new Active Directory user?

easy

A. New-ADUser

B. Get-ADUser

C. Remove-ADUser

D. Set-ADGroup

Solution

1. Step 1: Identify cmdlets for AD user management

   New-ADUser creates users, Get-ADUser retrieves users, Remove-ADUser deletes users, Set-ADGroup modifies groups.

2. Step 2: Match cmdlet to creation task

   Creating a new user requires New-ADUser.

3. Final Answer:

   New-ADUser -> Option A

4. Quick Check:

   Create user cmdlet = New-ADUser [OK]

Hint: New-ADUser creates users; Get-ADUser only reads [OK]

Common Mistakes:

• Using Get-ADUser to create users
• Confusing Remove-ADUser with creation
• Using Set-ADGroup for user creation

3. What will this PowerShell command output?

Get-ADUser -Filter 'Enabled -eq $true' | Select-Object -ExpandProperty Name

medium

A. List of all disabled user names

B. Error due to wrong filter syntax

C. List of all group names

D. List of all enabled user names

Solution

1. Step 1: Understand the filter condition

   The filter 'Enabled -eq $true' selects only users whose Enabled property is true (active users).

2. Step 2: Analyze the Select-Object usage

   Select-Object -ExpandProperty Name extracts just the user names from the results.

3. Final Answer:

   List of all enabled user names -> Option D

4. Quick Check:

   Filter enabled users = list names [OK]

Hint: Filter Enabled -eq $true lists active users only [OK]

Common Mistakes:

• Thinking it lists disabled users
• Assuming it returns groups instead of users
• Believing the filter syntax causes error

4. Identify the error in this PowerShell snippet for disabling an AD user:

Disable-ADUser -Identity $userName

medium

A. The variable $userName must be a user object, not a string.

B. The parameter should be -UserName, not -Identity.

C. Disable-ADUser cmdlet does not exist.

D. The cmdlet requires the -Confirm parameter.

Solution

1. Step 1: Check if Disable-ADUser exists

   There is no Disable-ADUser cmdlet in PowerShell AD module; disabling is done with Set-ADUser.

2. Step 2: Correct method to disable user

   Use Set-ADUser -Identity $userName -Enabled $false to disable a user.

3. Final Answer:

   Disable-ADUser cmdlet does not exist. -> Option C

4. Quick Check:

   No Disable-ADUser cmdlet = A [OK]

Hint: Use Set-ADUser -Enabled $false to disable users [OK]

Common Mistakes:

• Assuming Disable-ADUser cmdlet exists
• Using wrong parameter names
• Thinking -Confirm is mandatory

5. A sysadmin wants to automate disabling all inactive AD users who haven't logged in for 90 days. Which PowerShell approach is best?

hard

A. Use Get-ADGroupMember to find users and disable them.

B. Use Get-ADUser with -Filter on LastLogonDate, then pipe to Set-ADUser -Enabled $false.

C. Run Remove-ADUser on all users without checking last logon date.

D. Manually disable users one by one in Active Directory Users and Computers.

Solution

1. Step 1: Identify how to find inactive users

   Get-ADUser can filter users by LastLogonDate to find those inactive for 90 days.

2. Step 2: Automate disabling users

   Piping filtered users to Set-ADUser -Enabled $false disables them efficiently.

3. Final Answer:

   Use Get-ADUser with -Filter on LastLogonDate, then pipe to Set-ADUser -Enabled $false. -> Option B

4. Quick Check:

   Filter inactive users + disable = D [OK]

Hint: Filter inactive users by last logon, then disable in bulk [OK]

Common Mistakes:

• Disabling users manually one by one
• Removing users instead of disabling
• Using group membership instead of last logon date