While maintaining Windows Server startup scripts written in VBScript, you discover that a typo in a variable name let the script run with an unintended Variant variable instead of failing. Which single-line directive should you place at the very top of each .vbs file so the script engine forces explicit variable declarations and stops when an undeclared name is used?
VBScript honors the statement "Option Explicit" when it appears before any other code in the file. With this directive enabled, every variable must be declared with Dim, ReDim, or another declaration statement; an undeclared or misspelled identifier causes a compilation error, preventing the silent creation of a Variant. "Option Strict" is a .NET-only directive that VBScript does not recognize, and the phrases "Dim All" and "Use Strict Variable" are not valid VBScript syntax, so they have no effect on variable declaration checking.