SK0-004 · Question #357
A network administrator finds there are several users who cannot access a particular application. The application does not launch for the users. The network administrator finds the server has not…
The correct answer is A. Memory leak. A server that has run continuously for 192 days without a reboot and now fails to launch a specific application most likely has a memory leak in that application or its dependencies. Over time, a memory leak exhausts available RAM, eventually preventing new processes from…
Question
A network administrator finds there are several users who cannot access a particular application. The application does not launch for the users. The network administrator finds the server has not been rebooted in 192 days. Which of the following is the MOST likely cause of these issues?
Options
- AMemory leak
- BLow resources
- CSlow OS performance
- DService failure
How the community answered
(25 responses)- A84% (21)
- B4% (1)
- C4% (1)
- D8% (2)
Why each option
A server that has run continuously for 192 days without a reboot and now fails to launch a specific application most likely has a memory leak in that application or its dependencies. Over time, a memory leak exhausts available RAM, eventually preventing new processes from allocating the memory they need to start.
A memory leak occurs when an application or service continuously allocates memory but fails to release it back to the OS, causing cumulative consumption over time. After 192 days of uptime, leaked memory can exhaust the available pool, leaving insufficient RAM to launch additional application instances. This pattern - long uptime combined with failure to launch a specific application - is a classic indicator of a memory leak rather than a one-time resource shortage.
Low resources is a symptom or outcome, not a root cause - it does not explain why the condition progressively worsened with uptime rather than being a persistent problem from the start.
Slow OS performance might accompany high memory pressure but does not explain why the application fails to launch entirely, nor does it account for the long uptime context.
A service failure would typically affect the service itself (e.g., a daemon crashing) rather than causing a specific application to fail to launch after an extended uptime period.
Concept tested: Memory leak causing application launch failure over time
Source: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/debugging-a-user-mode-process
Topics
Community Discussion
No community discussion yet for this question.