Which scheduling behavior is correct for AT and SCHTASKS on Windows?

• A. AT runs all jobs as local SYSTEM.
• B. AT runs jobs as a designated user account.
• C. SCHTASKS cannot run as local SYSTEM.
• D. SCHTASKS is simpler but less flexible.

Answer: (A)

The key idea is the execution context of scheduled tasks. The legacy AT command schedules a one-time task, and the Task Scheduler service runs that job under the Local System account by default. It doesn’t provide an option to run the task under a specific user credential, so the command effectively executes with system-level privileges regardless of who created it.

That’s why the statement about AT is the best fit: AT runs all jobs as Local System. In contrast, SCHTASKS is designed to give you explicit control over which user account runs the task (via Run As options, including the possibility to run as SYSTEM if you specify that), so it isn’t limited to Local System like AT is. The claim that SCHTASKS cannot run as Local System is incorrect, and describing SCHTASKS as simpler but less flexible isn’t accurate given its broader credential options.