Scripting basics matching lab

Match PowerShell, batch, Python, and script-risk; leave run-blind and rename-ps1 unused.

Match each scripting ticket. Leave run-blind and rename-ps1 unused.

CompTIA 4.8 recognizes .bat/.ps1/.vbs/.sh/.js/.py use cases and the risk of malware, config drift, and resource exhaustion — never execute learner code server-side.

Automate Windows inventory with structured cmdlets

PowerShell script type.

Legacy logon map drives with a classic command script

Batch .bat/.cmd.

Cross-platform parse of CSV into a ticket API

Python use case.

User double-clicks an unknown .ps1 from email

Script malware / risk awareness.

Still on the bench

.ps1 PowerShell — Windows automation/cmdlets — Preferred modern Windows admin scripting when execution policy allows.
.bat/.cmd batch — simple legacy logon mappings — Still common for drive maps; limited compared to PowerShell.
.py Python — cross-platform parsing/API glue — Great for data/API tasks; runtime must be present and trusted.
Treat unsolicited scripts as malware — do not run — Email .ps1/.js/.vbs are classic payloads. Quarantine and report.
Run the emailed script elevated so it just works — Elevation plus unknown script is an incident, not troubleshooting.
Rename .ps1 to .bat and double-click for compatibility — Extension tricks do not make PowerShell into batch — and hide intent.