Bulk user operations from CSV in PowerShell - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import users from a CSV file.

PowerShell

Import-Csv [1]

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

A-Input 'users.csv'

B-File 'users.csv'

C-Path 'users.csv'

D-Source 'users.csv'

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect parameter names like -File or -Input.

Not enclosing the file name in quotes.

The Import-Csv cmdlet uses the -Path parameter to specify the CSV file location.

2fill in blank

medium

Complete the code to loop through each user imported from CSV.

PowerShell

foreach ($user in [1]) { Write-Output $user.Name }

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

AImport-Csv 'users.csv'

B$users

CGet-Content 'users.csv'

DRead-Host 'users.csv'

Attempts:

3 left

💡 Hint

Common Mistakes

Using Get-Content which reads raw text lines, not objects.

Using a variable not defined before the loop.

You can directly loop through the output of Import-Csv to process each user.

3fill in blank

hard

Fix the error in the code to create a new user from CSV data.

PowerShell

New-ADUser -Name $user.Name -SamAccountName $user.[1] -AccountPassword (ConvertTo-SecureString $user.Password -AsPlainText -Force) -Enabled $true

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

AUserName

BUser

CSamAccountName

DUsername

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect property names that do not match CSV headers.

Ignoring case sensitivity in property names.

The property name is case-sensitive and should be 'UserName' to match the CSV header.

4fill in blank

hard

Fill both blanks to filter users with 'Admin' in their role and create them.

PowerShell

Import-Csv 'users.csv' | Where-Object { $_.Role [1] '*Admin*' } | ForEach-Object { New-ADUser -Name $_.Name -SamAccountName $_.UserName -UserPrincipalName $_.UserPrincipalName -AccountPassword (ConvertTo-SecureString $_.Password -AsPlainText -Force) -Enabled [2] }

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

A-like

B-eq

C$true

D$false

Attempts:

3 left

💡 Hint

Common Mistakes

Using '-eq' which requires exact match instead of pattern match.

Setting -Enabled to $false which disables the account.

Use '-like' to match roles containing 'Admin' and enable the account with $true.

5fill in blank

hard

Fill all three blanks to update user email and enable the account only if status is 'Active'.

PowerShell

Import-Csv 'users.csv' | ForEach-Object { if ($_.Status [1] 'Active') { Set-ADUser -Identity $_.UserName -EmailAddress $_.[2] -Enabled [3] } }

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

A-eq

BEmail

C$true

D$false

Attempts:

3 left

💡 Hint

Common Mistakes

Using '-ne' or other operators instead of '-eq'.

Using wrong property names like 'EmailAddress' if CSV uses 'Email'.

Setting -Enabled to $false which disables the user.

Use '-eq' to check status, update 'Email' property, and enable account with $true.

Practice

1. What is the primary purpose of using Import-Csv in bulk user operations in PowerShell?

easy

A. To create a new CSV file with user details

B. To read user data from a CSV file into PowerShell objects

C. To delete users from Active Directory

D. To export user data to a CSV file

Solution

1. Step 1: Understand Import-Csv function

   Import-Csv reads data from a CSV file and converts each row into a PowerShell object with properties matching the CSV headers.

2. Step 2: Identify its role in bulk user operations

   In bulk user operations, Import-Csv is used to load user data so scripts can process each user easily.

3. Final Answer:

   To read user data from a CSV file into PowerShell objects -> Option B

4. Quick Check:

   Import-Csv reads CSV data [OK]

Hint: Import-Csv always reads data into objects, not writes [OK]

Common Mistakes:

• Confusing Import-Csv with Export-Csv
• Thinking Import-Csv deletes or modifies users
• Assuming Import-Csv creates new CSV files

2. Which of the following is the correct syntax to process each user from a CSV file named users.csv in PowerShell?

easy

A. Import-Csv users.csv | ForEach-Object { Write-Host $_.Name }

B. ForEach-Object Import-Csv users.csv { Write-Host $_.Name }

C. Import-Csv users.csv ForEach { Write-Host $_.Name }

D. Get-Csv users.csv | ForEach-Object { Write-Host $_.Name }

Solution

1. Step 1: Recognize correct pipeline usage

   Import-Csv users.csv outputs objects piped into ForEach-Object to process each user.

2. Step 2: Validate syntax correctness

   Import-Csv users.csv | ForEach-Object { Write-Host $_.Name } correctly uses the pipeline and script block syntax to access each user's Name property.

3. Final Answer:

   Import-Csv users.csv | ForEach-Object { Write-Host $_.Name } -> Option A

4. Quick Check:

   Pipeline with Import-Csv and ForEach-Object is correct [OK]

Hint: Use pipeline: Import-Csv | ForEach-Object { } [OK]

Common Mistakes:

• Misplacing ForEach-Object before Import-Csv
• Using Get-Csv which doesn't exist
• Omitting the pipeline operator |

3. Given the CSV file users.csv with content:

Name,Email
Alice,[e-mail]
Bob,[e-mail]

What will the following script output?

Import-Csv users.csv | ForEach-Object { Write-Output $_.Email }

medium

A. [e-mail]
[e-mail]

B. Name
Email

C. Alice
Bob

D. Error: Property 'Email' not found

Solution

1. Step 1: Understand CSV data and properties

   The CSV has two rows with headers Name and Email. Import-Csv creates objects with these properties.

2. Step 2: Trace the script output

   The script outputs the Email property of each object, so it prints [e-mail] and [e-mail] on separate lines.

3. Final Answer:

   [e-mail] [e-mail] -> Option A

4. Quick Check:

   Output emails from CSV rows [OK]

Hint: Output property names exactly as CSV headers [OK]

Common Mistakes:

• Printing header names instead of values
• Confusing Name and Email properties
• Expecting error due to property access

4. You wrote this script to create users from a CSV but it fails with an error:

Import-Csv users.csv | ForEach-Object { New-ADUser -Name $_.Name -EmailAddress $_.Email }

What is the most likely cause?

medium

A. The pipeline operator | is missing

B. The CSV file is empty

C. You forgot to import the Active Directory module

D. The New-ADUser cmdlet does not have an -EmailAddress parameter

Solution

1. Step 1: Check New-ADUser parameters

   New-ADUser does not accept -EmailAddress directly; email is set via -UserPrincipalName or -OtherAttributes.

2. Step 2: Identify error cause

   Using an invalid parameter causes the script to fail with an error about unknown parameter.

3. Final Answer:

   The New-ADUser cmdlet does not have an -EmailAddress parameter -> Option D

4. Quick Check:

   Invalid parameter causes error [OK]

Hint: Check cmdlet parameters with Get-Help [OK]

Common Mistakes:

• Assuming all user properties are direct parameters
• Ignoring module import errors
• Missing pipeline operator in script

5. You want to bulk update users' department from a CSV file update.csv with columns Username and Department. Which script correctly updates the department attribute in Active Directory?

hard

A. Import-Csv update.csv | ForEach-Object { Set-ADUser -Name $_.Username -Email $_.Department }

B. Import-Csv update.csv | ForEach-Object { New-ADUser -Name $_.Username -Department $_.Department }

C. Import-Csv update.csv | ForEach-Object { Set-ADUser -Identity $_.Username -Department $_.Department }

D. Import-Csv update.csv | ForEach-Object { Set-ADUser -UserPrincipalName $_.Username -Department $_.Department }

Solution

1. Step 1: Identify correct cmdlet for updating users

   Set-ADUser updates existing users; New-ADUser creates new users, so Import-Csv update.csv | ForEach-Object { New-ADUser -Name $_.Username -Department $_.Department } is incorrect.

2. Step 2: Check parameters for updating department

   -Identity accepts username or other identifiers; -Department sets the department attribute correctly. Import-Csv update.csv | ForEach-Object { Set-ADUser -Identity $_.Username -Department $_.Department } uses these properly.

3. Step 3: Evaluate other options

   Import-Csv update.csv | ForEach-Object { Set-ADUser -Name $_.Username -Email $_.Department } uses invalid -Email parameter; Import-Csv update.csv | ForEach-Object { Set-ADUser -UserPrincipalName $_.Username -Department $_.Department } uses -UserPrincipalName which may not match Username column, risking errors.

4. Final Answer:

   Import-Csv update.csv | ForEach-Object { Set-ADUser -Identity $_.Username -Department $_.Department } -> Option C

5. Quick Check:

   Set-ADUser with -Identity and -Department updates users [OK]

Hint: Use Set-ADUser with -Identity to update existing users [OK]

Common Mistakes:

• Using New-ADUser instead of Set-ADUser for updates
• Confusing parameter names like -Email vs -Department
• Using wrong identity parameter causing errors