1Y0-A05 · Question #215
Scenario: An automated application hotfix is causing the application to crash and hang. The helpdesk team must terminate this business-critical application without affecting other applications…
The correct answer is D. Terminate Processes. See the full explanation below for the reasoning.
Question
Scenario: An automated application hotfix is causing the application to crash and hang. The helpdesk team must terminate this business-critical application without affecting other applications running in the users' session while the application writers prepare a fix. Which permissions should an administrator assign the helpdesk team to achieve this?
Options
- ALogOff Users
- BReset Sessions
- CDisconnect Users
- DTerminate Processes
How the community answered
(22 responses)- A5% (1)
- B9% (2)
- C5% (1)
- D82% (18)
Community Discussion
6D is your answer. Terminate Processes lets the helpdesk team kill just that one hung application process without touching the user session or anything else running in it, which is exactly what you need when a bad hotfix crashes a specific app and you want to leave the rest of the user's work intact.
"Terminate Processes" targets the specific crashed process, not the whole session, so D.
That is accurate for most scenarios, but worth drilling a separate card for what happens when the crashed process holds a shared resource like a named pipe or a COM port, because the answer in those edge cases can shift toward restarting the whole session.
D is right. Why would LogOff or Disconnect risk other apps but Terminate Processes doesn't?
Terminate Processes is scoped to that session only, but the real reason Logoff and Disconnect get flagged is that they yank shared resources mid-flight and can corrupt state for other users on the same box.
"Reset Sessions" tempts here but nukes the whole session, D is the surgical pick.