Windows PowerShell and System Center Operations Manager Quiz

Win32_NetworkAdapterConfiguration WMI class contains MACAddress and IPAddress properties for network adapters. The filter IpEnabled=TRUE selects only adapters with active IP configurations. Option B and D incorrectly use Win32_NetworkAdapterDetails which is not a valid WMI class. Option C uses IpEnabled=FALSE which would return adapters without IP configuration.

PowerShell single quotes treat everything literally - $strA is not expanded but treated as the literal string '$strA'. Double quotes would expand variables. The output is exactly 'Tom drives a $strA car.' with the variable name displayed, not its value 'fast'.

Win32_ScheduledJob WMI class represents scheduled tasks created with the AT command (legacy Windows scheduler). Option A queries directories, option B queries shared folders, and option D queries disk partitions - none are related to scheduled tasks.

The script converts MB to bytes. First removes 'MB' string leaving '10.99'. Converts to double (10.99). Multiplies by 1024 to get KB, then by 1024 again to get bytes: 10.99 × 1024 × 1024 = 10.99 × 1048576 = 11523850.24 bytes exactly. This is the correct MB to byte conversion.

Get-History cmdlet retrieves the list of commands executed in the current PowerShell session. It returns command history with Id and CommandLine properties. Option A Invoke-History reruns a command from history but does not list them. Option B has a typo (Invake instead of Invoke). Option D Export-Console exports console configuration, not command history.

The correct code uses wscript.shell COM object and calls the popup method with the message text, timeout (0 seconds), title, and button type (4 = Yes/No). Options A uses wscript.Window (wrong object), B and D use .Window method instead of .popup. Option C has the correct COM object (wscript.shell) and correct method (popup).

The correct sequence for creating and using a new MMC Snap-In is: first create the snap-in code (I), then register it with the system so Windows recognizes it (II), next install it in the appropriate location (III), and finally add it to the MMC console for use (IV). Option A correctly presents this order.

PowerShell script signing requires: creating a code signing certificate using makecert or similar tools (A), enabling strong private key protection during certificate creation to prevent unauthorized use (B), and signing the script using Set-AuthenticodeSignature cmdlet (C). The public key is embedded in the certificate, not used separately for execution - the signature is verified automatically.

PowerShell scripts (.ps1 files) cannot be compiled into executable (.exe) files. PowerShell scripts are interpreted by the PowerShell host engine. While there are third-party tools that can package scripts with the PowerShell runtime into executables, PowerShell itself does not provide compilation to native executables. The statement is false.

PowerShell drives (PS Drives) are different from Windows filesystem drives. PowerShell drives are virtual drives that provide consistent access to various data stores like the registry, certificates, environment variables, and aliases, using the same navigation commands as filesystem drives. They are created by PowerShell providers and don't correspond to physical or logical disk drives.

Tee-Object cmdlet splits pipeline output, sending it to a file or variable while also passing it down the pipeline for further processing (A, B). It saves output to a destination without stopping the pipeline flow. By default, Tee-Object uses ASCII encoding when writing to files (C is true). It's specifically designed for capturing output to files/variables in addition to pipeline processing, not for bypassing variables.

The correct PowerShell Snap-In for SCOM 2007 client operations is Microsoft.EnterpriseManagement.OperationsManager.Client. This Snap-In enables administrative tasks from the PowerShell console. The other options with 'server', 'SQLserver', and 'ScomServer' are not valid Snap-In names.

The SDK (Software Development Kit) account is specifically used to read and write information in the Operations Manager database. This account enables programmatic access to SCOM data. Data Warehouse Write Account, Data Reader Account, and Action account serve different purposes.

Management packs in SCOM contain Rules, Monitors, and Tasks as core components. An Agent is NOT part of the management pack itself - agents are the software installed on monitored computers that execute management pack content. The agent is separate infrastructure.

When a discovered item has an unknown status and no available monitor, SCOM displays a green circle without a check mark. This indicates the object is discovered but not actively monitored. Gray agent, check marks (green or red) represent different agent states.

SCOM 2007 has three built-in user roles: Advanced Operator, Author, and Operator. MP Admin is NOT a standard user role in SCOM 2007 - it appears to be a distractor. User roles control permissions within the Operations Console.

The MP View Tool (MPViewer) is used to export and view management pack settings and XML. It allows administrators to extract management pack configurations for backup or transfer. SCOM 2007 and Authoring tool serve different purposes.

In SCOM 2007, automatic group membership is created using computer attributes like OS version, installed software, or domain configuration. When you define an auto-group, you specify attribute-based rules, and computers matching those attributes are automatically added to the group.

SCOM 2007 agent requires Microsoft Core XML Services (MSXML) 6.0 for XML parsing and data management tasks. SQL Agent and Active Directory are not prerequisites for agent installation itself.