Why avoid aliases in shared PowerShell scripts?
Documentation: Microsoft Learn
Interview · Question 7 of 34
Answer before reveal
Your draft
Write the answer you would give in an interview. The model answer stays hidden until you have drafted at least a short response.
A strong answer
Aliases are convenient interactively, but shared scripts should favor full command and parameter names so intent survives code review, different profiles and hosts.
Show it concretely
1PS> Get-Command % | Select-Object Name, Definition
Expect this follow-up
Are aliases themselves portable across every host and module version?
