220-1102 Practice Question: That a PowerShell script they wrote to rename…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  The script uses a cmdlet that is not available on the network drive.

  Why it's wrong here

  Cmdlets are compiled binaries or functions loaded into a PowerShell session from modules, which are typically installed locally on the system. Their availability is determined by the installed modules and the PowerShell environment configuration, not by the specific drive or network share where a script file is stored. Therefore, a cmdlet's functionality would not be dependent on the script's location on a network drive, making this option incorrect.

• ✓

  The execution policy is set to RemoteSigned, which blocks scripts from network locations.

  Why this is correct

  The RemoteSigned execution policy is a security measure that mandates all PowerShell scripts originating from the internet or network shares must be digitally signed by a trusted publisher to execute. While locally created scripts can run without a signature, PowerShell classifies scripts executed directly from a network location as 'remote.' This policy prevents the execution of unsigned network scripts, often resulting in an 'Access Denied' or similar error, directly addressing the reported issue.

• ✗

  The network folder has a space in its name.

  Why it's wrong here

  While spaces in file paths can sometimes cause issues if not properly handled in older command-line environments, PowerShell is robust and designed to manage such paths effectively. Enclosing the path in double quotes, such as & "C:\My Folder\script.ps1", or using tab completion automatically resolves this common scenario. A space in a folder name, if not properly quoted, would typically lead to a 'file not found' or a syntax parsing error, not a 'permission denied' or execution policy restriction.

• ✗

  The user is not running PowerShell as an administrator.

  Why it's wrong here

  Running PowerShell as an administrator grants elevated privileges necessary for system-wide changes, such as modifying protected system files, installing software, or altering system configurations. However, executing a PowerShell script that merely renames files within a user's accessible network folder does not typically require these elevated administrative rights. If the user possesses standard read, write, and modify permissions on the specific network folder, they can rename files without needing to run PowerShell with administrator privileges.

Go deeper

Related to this question