Batch files (.bat) are classic Windows script files that execute a series of command-line instructions. They can be linked to user logon events via Group Policy or the Startup folder to automate tasks (like mapping drives or launching applications) when a user signs in.

In a structured change-management process, the very first step is to propose (or formally request) the change via a Request for Change (RFC). This ensures stakeholders review the need, assess risks, and determine the priority before any approvals, scheduling, or implementation occur.

An internal wiki is the most likely place to store deployment instructions because it provides centralized, documented, and easily accessible technical procedures for large-scale or complex tasks.

Clearing the browser's cached data and recent history removes malicious scripts or adware- related pop-ups stored in the cache, ensuring the issue is resolved before returning the computer.

Domain join failures with successful IP connectivity almost always point to name-resolution issues. The workstation is using public DNS servers (8.8.8.8 and 1.1.1.1), which have no records for the internal AD domain or its controllers. Pointing DNS at the internal DNS server (192.168.1.10) ensures the domain name and SRV records can be resolved, allowing the join to succeed.