What risk does changing the password of a traditional service account create?

What risk does changing the password of a traditional service account create?

• A. The application may require more user interaction
• B. The service may fail to run
• C. The server may not need the password
• D. The service account will become inactive

Answer: (B)

Changing the password of a traditional service account can cause the service associated with that account to fail to run. This is because many applications and services use service accounts to authenticate and run tasks or processes. When the password of a service account is changed, any service or application that relies on that account will no longer be able to authenticate successfully unless it is updated with the new password. If this step is not taken, the application will not have the necessary permissions to operate, resulting in a failure to execute the service, which can disrupt functionality and impact overall system reliability.

The other possible outcomes listed do not directly address the critical connection between the service account's authentication and application functionality. For instance, while more user interaction might be needed in certain scenarios, or while the server may not need the password for other tasks, these situations do not fundamentally describe the risk of service failure that stems from password changes on service accounts. Furthermore, while a service account could technically become inactive or unutilized, the immediate and pressing concern in the context of changing the password lies in the potential failure of the service that relies on the account for authentication.