A - Yes. I don't see why not.

Seems like it would be A to me as well. Wrong answer?

Chat-GPT says Answer A is correct. Adding the folder containing the PowerShell scripts to the PATH environment variable will allow you to run the scripts from any location in the PowerShell console without specifying the full path to the scripts. This solution will persist between PowerShell sessions, meaning that you won't need to add the folder to the PATH variable every time you start a new PowerShell session. To add the D:\Scripts folder to the PATH environment variable, follow these steps: Right-click the Start menu and select System. Click Advanced system settings. Click Environment Variables. Under System Variables, scroll down and select Path, and then click Edit. Click New and enter the path to the D:\Scripts folder, then click OK. Click OK to close all the windows. After completing these steps, you should be able to run the PowerShell scripts in the D:\Scripts folder without specifying the full path to the scripts.

Yes. Period.

The correct answer is 'A'. Environment variables don't just disappear between PowerShell sessions and server as fixed points of reference for the windows environment (i.e. environment variables).

chatgpt: A. Yes, this meets the goal. Explanation: The PATH environment variable is a system variable that contains a list of directories where the operating system looks for executable files. By adding D:\Scripts to the PATH environment variable, you can run PowerShell scripts in that directory without specifying the full path to the scripts.

Tested with windows sysinternal tools and IT IS persistent.

This site has so many answers just straight up wrong, I'm wondering if anyone actually reviews them

im more confushed than before in most of these tasks. People dosent agree and often doent agree with the provided answer. Its terrible way of studying

Resposta: A To make a persistent change to an environment variable on Windows using the System Control Panel: Open the System Control Panel. Select System. Select Advanced System Settings. Go to the Advanced tab. Select Environment Variables.... Make your chang https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_environment_variables?view=powershell-7.2&viewFallbackFrom=powershell-6

answer is A. tested and even after reboot it works

This is the standard way to change the path under Windows manually. It permanently modifies the path, so it will persist between Powershell sessions as well.

Saving changes to environment variables To make a persistent change to an environment variable on Windows, use the System Control Panel. Select Advanced System Settings. On the Advanced tab, click Environment Variable.... You can add or edit existing environment variables in the User and System (Machine) scopes. Windows writes these values to the Registry so that they persist across sessions and system restarts. Alternately, you can add or change environment variables in your PowerShell profile. This method works for any version of PowerShell on any supported platform. https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_environment_variables?view=powershell-7.2&viewFallbackFrom=powershell-6

B is correct.

The answer is B as: When you change environment variables in PowerShell, the change affects only the current session...Read more here https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_environment_variables?view=powershell-7.1#saving-changes-to-environment-variables

This link seems to support 'A' as the correct answer: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_environment_variables?view=powershell-7.1#saving-changes-to-environment-variables

you still need to add path every time .better answer will be right-click and run poershell here