Examkin

Question

Difficulty: HardBasic Scripting Languages and Constructs

A desktop support technician is troubleshooting an automated network drive mapping script intended to run during user logon on Windows client workstations. The script references environment variables using the `%USERNAME%` syntax, utilizes `IF NOT EXIST` conditional checks for folder paths, and executes command-line network utility commands. Double-clicking the file results in a Windows Script Host runtime error indicating invalid syntax. Which of the following actions will resolve the execution failure while preserving the current script code?

  1. Change the script file extension from `.vbs` to `.bat` so it runs natively within the Windows Command Prompt interpreter.Answer
  2. B
    Change the file extension to `.ps1` and modify the PowerShell execution policy to `RemoteSigned`.
  3. C
    Change the file extension to `.sh` and insert a `#!/bin/bash` shebang line at the beginning of the file.
  4. D
    Execute the file using the `cscript.exe` command-line host with the `/b` switch enabled.

Answer

Change the script file extension from `.vbs` to `.bat` so it runs natively within the Windows Command Prompt interpreter.
The script code provided uses standard Windows Batch syntax (`%USERNAME%` for environment variables, `IF NOT EXIST` for conditionals, and command-line utility calls). Saving a batch file with a `.vbs` extension forces Windows to run it through Windows Script Host, which generates a syntax error. Renaming the extension to `.bat` ensures `cmd.exe` interprets the script natively.

Step-by-Step Solution

1
Analyze the syntax constructs presented in the problem statement.
The script uses `%USERNAME%` for environment variable expansion, `IF NOT EXIST` for file/directory conditional branching, and command-line commands.
These constructs belong exclusively to Windows Batch (`.bat` / `.cmd`) scripting.
2
Identify the cause of the runtime error.
The file was saved with a `.vbs` extension, causing Windows to invoke Windows Script Host (WSH/`wscript.exe`), which expects VBScript syntax.
WSH fails to parse Batch control constructs and variable syntax, throwing a syntax error.
3
Determine the corrective action to maintain existing script code.
Renaming the file extension to `.bat` directs the operating system to use `cmd.exe` as the interpreter.
This allows all existing Batch constructs to execute without requiring syntax modifications.

Key Concept

Basic Scripting Languages and File Extensions
Rate this question

Topics

Basic Scripting Languages and Constructs

More questions from this topic