SK0-005 · Question #616
A systems administrator is performing a routine update to a server. The administrator applies the update, restarts the server, and then conducts routine testing that reveals the critical…
The correct answer is D. The account used to run the service has expired. Since the service is set to start automatically and the issue persists even after rolling back the update, it indicates that the update itself was not the root cause. Instead, the underlying configuration is likely affected. One common scenario is that the account configured to…
Question
A systems administrator is performing a routine update to a server. The administrator applies the update, restarts the server, and then conducts routine testing that reveals the critical functionality provided by the server is unavailable. Event logs indicate a core service is failing to start. The service is configured to start automatically, and rolling back the update does not correct the issue. Which of the following is most likely causing the service failure?
Options
- AThe server requires another reboot to complete the rollback.
- BThe administrator is not authorized to run the service.
- CThe server requires further updates of other software components.
- DThe account used to run the service has expired.
How the community answered
(31 responses)- A13% (4)
- B3% (1)
- C6% (2)
- D77% (24)
Explanation
Since the service is set to start automatically and the issue persists even after rolling back the update, it indicates that the update itself was not the root cause. Instead, the underlying configuration is likely affected. One common scenario is that the account configured to run the service may have an expiration date (such as a temporary service account) that has now passed, preventing the service from starting. Rolling back the update wouldn't restore the credentials or account status; therefore, the expired account is the probable culprit.
Topics
Community Discussion
No community discussion yet for this question.