What is a plausible reason for an automation tool account to become locked, requiring investigation?

• A. Low permission levels
• B. Expired password
• C. Network congestion
• D. Someone has tried to hack into the system using that account

Answer: (A)

When an automation tool account is locked, it usually points to authentication or authorization controls that require review. If the account’s permissions are too low for the tasks it’s trying to perform, automated actions can fail repeatedly. Those failures can trigger security policies or lockouts to prevent potential misuse, prompting an investigation to verify that the account has the proper scope of access without being over-privileged. In practice, you’d check the account’s roles and privileges, confirm it has exactly what it needs to run its jobs, and adjust as needed. Other possibilities like an expired password would also cause a lock because the system cannot authenticate the account, but the reason tied to insufficient permissions explains why investigators would focus on whether the account has the right level of access rather than just why it can’t log in. Network congestion wouldn’t cause a lock, and while a targeted hacking attempt could trigger protective measures, a permission-related lock is a common, actionable scenario that practitioners routinely investigate first.