Scheduled scripts with Task Scheduler in PowerShell - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this PowerShell command to list scheduled tasks?

You run this command in PowerShell to list all scheduled tasks on your system:

Get-ScheduledTask | Select-Object -First 1 | Format-List

What kind of output should you expect?

PowerShell

Get-ScheduledTask | Select-Object -First 1 | Format-List

A A detailed list of properties of the first scheduled task, including TaskName, State, and Actions.

B A simple list of task names only, without any other details.

C A table showing all scheduled tasks with their next run times.

D An error saying 'Get-ScheduledTask' is not recognized as a cmdlet.

💡 Hint

Think about what Format-List does and what Select-Object -First 1 returns.

Get-ScheduledTask returns all tasks. Select-Object -First 1 picks the first task object. Format-List shows all properties of that object in detail.

📝 Syntax

intermediate

Which PowerShell command correctly creates a scheduled task to run a script daily at 7 AM?

You want to create a scheduled task that runs 'C:\Scripts\backup.ps1' every day at 7 AM. Which command is correct?

A Register-ScheduledTask -TaskName "DailyBackup" -Trigger (New-ScheduledTaskTrigger -Daily -At 7am) -Action (New-ScheduledTaskAction -Execute "powershell.exe" -Argument "-File C:\Scripts\backup.ps1")

B New-ScheduledTask -TaskName "DailyBackup" -Trigger (New-ScheduledTaskTrigger -Daily -At 7am) -Action (New-ScheduledTaskAction -Execute "powershell.exe" -Argument "-File C:\Scripts\backup.ps1")

C Register-ScheduledTask -Name "DailyBackup" -Trigger (New-ScheduledTaskTrigger -Daily -At 7am) -Action (New-ScheduledTaskAction -Execute "powershell.exe" -File "C:\Scripts\backup.ps1")

D New-ScheduledTask -TaskName "DailyBackup" -Trigger (New-ScheduledTaskTrigger -Daily -At "7:00") -Action (New-ScheduledTaskAction -Execute "powershell.exe" -Argument "-File C:\Scripts\backup.ps1")

💡 Hint

Register-ScheduledTask is used to create the task in Task Scheduler. Check parameter names carefully.

Register-ScheduledTask creates the task. The -TaskName parameter names it. The trigger and action are created with New-ScheduledTaskTrigger and New-ScheduledTaskAction. The -Argument parameter passes the script file path correctly.

🔧 Debug

advanced

Why does this scheduled task fail to run the script?

You created a scheduled task with this action:

New-ScheduledTaskAction -Execute "powershell.exe" -Argument "C:\Scripts\cleanup.ps1"

But the script never runs. What is the problem?

A The scheduled task must run as administrator to execute scripts.

B The script path must be enclosed in single quotes inside -Argument.

C The -Execute parameter should be 'pwsh.exe' instead of 'powershell.exe'.

D The -Argument parameter is missing the '-File' flag before the script path.

💡 Hint

Check how PowerShell expects script files to be passed as arguments.

PowerShell requires the '-File' flag before the script path to run a script file. Without it, powershell.exe treats the argument as a command, causing failure.

🚀 Application

advanced

How to export and import a scheduled task using PowerShell?

You want to move a scheduled task named 'WeeklyReport' from one computer to another. Which sequence of commands correctly exports and imports the task?

A Export-ScheduledTask -TaskName "WeeklyReport" -Path "C:\Temp\WeeklyReport.xml"; Register-ScheduledTask -Xml (Get-Content "C:\Temp\WeeklyReport.xml" | Out-String) -TaskName "WeeklyReport"

B Export-ScheduledTask -TaskName "WeeklyReport" -File "C:\Temp\WeeklyReport.xml"; Register-ScheduledTask -Xml (Get-Content "C:\Temp\WeeklyReport.xml") -TaskName "WeeklyReport"

C Export-ScheduledTask -TaskName "WeeklyReport" -Path "C:\Temp\WeeklyReport.xml"; Register-ScheduledTask -Xml (Get-Content "C:\Temp\WeeklyReport.xml" -Raw) -TaskName "WeeklyReport"

D schtasks /Query /TN "WeeklyReport" /XML > "C:\Temp\WeeklyReport.xml"; schtasks /Create /TN "WeeklyReport" /XML "C:\Temp\WeeklyReport.xml"

💡 Hint

Get-Content with -Raw reads the entire XML as a single string needed for -Xml parameter.

Export-ScheduledTask uses -Path to save XML. Register-ScheduledTask needs the XML as a single string, so Get-Content with -Raw is required. Option C correctly uses these.

🧠 Conceptual

expert

What is the effect of setting the 'RunLevel' property to 'Highest' in a scheduled task?

In Task Scheduler, you set the 'RunLevel' property of a task to 'Highest'. What does this do?

A The task runs only when the user is logged in with highest privileges.

B The task runs with administrator privileges, prompting for elevation if needed.

C The task runs with the highest CPU priority to finish faster.

D The task runs with the highest memory allocation allowed by the system.

💡 Hint

Think about Windows User Account Control and task permissions.

Setting RunLevel to Highest means the task runs with administrator rights, triggering elevation if required by UAC.