Powershell Active Directory - Traffic seucirty, LDAPS and port 636?

in powershell when run "get-aduser "username"" traffic encrypted? anyway make encrypted?   
is there means of using ldaps / port 636 powershell ad connectivity/queries? or protect username/password elements , not subsequent traffic?    
is there concern passwords being passed in clear text when using powershell , ad queries?
what saved/automated queries require passwords? can protected or local disk encryption issue?

by default, traffic not encrypted.  

yes, can make encrypted.

yes, can make powershell use ldaps, provided script right way.

there no concern passwords being sent in clear text ldap or ldaps, except if setting password

saved automated queries, providing username , password authenticate ad, these credentials can encrypted, powershell, within script, or file.

if super worried this, setting ipsec between whatever machines using run script, , dc's.  it's not difficult.  you have done in 10 or 20 minutes.  this encrypt traffic.

read this!

Windows Server  >  Windows PowerShell