Common Script File Types for A+
Short answer
Technicians should be able to look at a filename or deployment artifact and identify likely script types and where they run. File extensions provide clues about the runtime required and the platform where the script is expected to operate. The goal is recognition and safe handling, not scripting skills.
Why it appears on the exam
- Given a filename and platform, identify the likely runtime (e.g., which extension runs on Linux vs Windows). - Match an operational scenario to an appropriate script file type (e.g., cross-platform automation -> .py). - Recognize when a file extension suggests the need for caution and a review before execution.
Key concepts
Concept 1
Required terms
.bat: .bat - Windows batch file for command interpreter (cmd.exe) automation tasks .ps1: .ps1 - PowerShell script used on modern Windows systems for more powerful automation .vbs: .vbs - VBScript file used historically on Windows for simple scripted tasks and automation .sh: .sh - Shell script for Unix-like systems (Linux, macOS) typically run by a shell like bash or sh
Example
A file named update_drivers.bat found on a Windows workstation likely contains cmd commands for legacy automation.
Concept 2
How Common Script File Types works
Technicians should be able to look at a filename or deployment artifact and identify likely script types and where they run. File extensions provide clues about the runtime required and the platform where the script is expected to operate. The goal is recognition and safe handling, not scripting skills.
Example
An admin receives a file deploy.ps1: it is a PowerShell script and may require elevated permissions to run.
Concept 3
Common confusion
- Treating the extension as a guarantee of safety; any script can be malicious regardless of extension. - Confusing .bat and .ps1 as interchangeable; they use different interpreters and capabilities. - Assuming scripts without extensions are harmless; Unix scripts often have no extension but are executable.
Example
A script called cleanup.sh found on a Linux server suggests shell commands and should be reviewed for unintended effects.
Concept 4
Core 2 (220-1202) question cues
Given a filename and platform, identify the likely runtime (e.g., which extension runs on Linux vs Windows); Match an operational scenario to an appropriate script file type (e.g., cross-platform automation -> .py); Recognize when a file extension suggests the need for caution and a review before execution.
Example
A tool delivered as collect_info.py indicates a Python-based utility that needs a Python runtime to operate.
Sample questions
Select an answer to reveal the explanation. For tracked practice and weak-area review, use the Cultiv8 app.
Q1.A technician is troubleshooting this situation: A file named update_drivers.bat found on a Windows workstation likely contains cmd commands for legacy automation. What should they identify?
Q2.A technician sees this situation: An admin receives a file deploy.ps1: it is a PowerShell script and may require elevated permissions to run. Which answer should they choose?
Q3.Read this A+ scenario: A script called cleanup.sh found on a Linux server suggests shell commands and should be reviewed for unintended effects. Which term or action matches it?
Practice this lesson in Cultiv8
The app adds tracked practice, targeted remediation, saved session history, and future readiness scoring.
Continue in Cultiv8