PowerShell Scripting and Administration

PowerShell evaluates operators in the following precedence: parentheses and braces first, then subexpression operators (@ $), then logical not (!), then indexing and property access ([] .), then call operator (&), then increment/decrement (++ --), then unary operators, then multiplication/division/modulo, then addition/subtraction, then comparison operators, then logical -and -or, then pipelines (|), then redirection (> >>), then assignment (=). This matches standard operator precedence rules.

PowerShell supports multi-dimensional arrays using the 'object[,]' type notation. Option A correctly declares a 2D array using New-Object with dimensions 10,20. Options C and D correctly access and assign values using comma-separated indices [row,column]. Option B is incorrect because PowerShell 2D arrays use [x,y] syntax, not [x][y] nested indexing (which would be for jagged arrays).

PowerShell includes three core snap-ins by default: Core (fundamental PowerShell functionality), Management (system management cmdlets), and Utility (general-purpose utilities). Microsoft.PowerShell.Script is not a valid snap-in name in PowerShell's default snap-in list.

Windows PowerShell snap-ins must be registered with the system before they can be loaded and used. If a snap-in is not registered, PowerShell cannot load it or access its methods. Therefore, the statement is false.

PowerShell cannot load snap-ins that are not registered in the Windows Registry. The registration process is mandatory - it tells PowerShell where to find the snap-in's DLL and what cmdlets it provides. Attempting to load an unregistered snap-in will fail.

Global scope variables are accessible from anywhere in PowerShell. Script scope variables are visible throughout the script file. The statement C is incorrect because local scope variables ARE inherited by child scopes - they remain visible in nested scopes. Private scope is the only scope that doesn't inherit to children.

Option D correctly instantiates System.Diagnostics.EventLog with the log name MyLog and calls the Clear() method to remove all entries. Options A uses the wrong log name (Application), while B and C use incorrect methods (Remove() and Delete() don't exist or don't clear entries).

The string::join() method concatenates array elements using the specified separator (:). Joining This is, a sample, PowerShell, Script with colon separator produces This is:a sample:PowerShell:Script. The final $Array outputs this single string value.

The ArrayList starts with red, yellow, orange, green, blue, purple. RemoveRange(3,3) removes 3 elements starting at index 3 (0-based): green, blue, and purple. This leaves red, yellow, orange - the first three items that were added before the removal range.

To find processes running from a given date, we compare the starttime property using the greater-than-or-equal operator (-ge) against a cast datetime object. Option A uses -le (less than or equal), Option C uses -like, and Option D uses -neq, making option B the only correct choice.

The script connects to a remote computer using the WinNT ADSI provider, filters for objects with schemaClassName group (which retrieves all local group objects), then iterates through them and outputs each group's name. It does not list group members - it only lists the group names themselves.

Windows stores installed application information in the registry under HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall. Option B correctly navigates to this registry path and uses Get-ItemProperty to retrieve the application details from each subkey. Option A uses an incorrect key name, while Option C uses Get-ChildItem which lists subkeys rather than retrieving their properties.

The Win32_PhysicalMemory WMI class provides information about each physical memory module installed in the system. The DeviceLocator property identifies the memory slot location, and the Capacity property indicates the RAM size. Option B uses Win32_PhysicalMemoryArray which describes the memory array hardware rather than individual modules, while Option C references a non-existent WMI class.

Option A correctly uses Get-WmiObject -List to retrieve all WMI classes, then filters with -match ^Win32_ (regex for strings starting with Win32_), sorts by the Name property, and formats the output as a table. Option B uses the invalid -Table parameter, Option C uses -notlike which excludes Win32 classes, and Option D has an incorrect regex pattern with an extra asterisk.

The Kill cmdlet (alias for Stop-Process) terminates processes. The pipeline filters processes by name using -Eq for exact match, then passes matching processes to Kill. Option A and C incorrectly use Terminate which is not a valid PowerShell cmdlet. Option B uses -neq which would select all processes EXCEPT the one specified.

The win32_TimeZone WMI class contains timezone configuration information including bias, standard name, and daylight name. Option A queries desktop settings, option B has a typo (Enviornmanet) and queries environment variables, and option D uses a non-existent class name win32_TimeZoneSetting.

The break statement immediately exits the while loop before Write-Host executes. The condition ($a -eq 1) is never true because $a is a string 'something', not the integer 1, so continue is never reached. The break executes on the first iteration, terminating the loop without any output.

PowerShell parameter attributes include Mandatory, Positional, and Named (parameters you specify by name). Generic is not a valid PowerShell parameter type - there is no [Generic()] attribute in PowerShell. Parameter types can be string, int, bool, etc., but Generic is not a parameter classification.

Measure-Command is the PowerShell cmdlet that measures the time it takes to run a script block or command. It returns a TimeSpan object showing elapsed time. Option A Measure-CommandLet is not a valid cmdlet name, and Measure-Time does not exist in PowerShell.

The Out-Null cmdlet discards output generated by a command instead of sending it down the pipeline or to the console. This is commonly used to suppress unwanted output from functions or cmdlets.