Which consequence of an outage tends to crash the core application?

The correct consequence of an outage that tends to crash the core application is not accurately represented in the chosen option. An outage typically leads to direct operational challenges, which can have a cascading effect on various aspects of application performance and reliability.

When an application faces an outage, it often results in immediate impacts on user experience, leading to frustration for both users and developers. These outages can erode the confidence developers have in their ability to ship code effectively. Continued instability within the application can deter teams from deploying updates and improvements out of fear that such changes will lead to further outages.

Moreover, an outage often wastes engineering time as teams scramble to identify the cause, fix the problem, and prevent similar issues in the future. This reactive maintenance diverts resources from strategic projects and improvements, ultimately stalling progress in the long term.

In addition, outages can increase risks for ongoing projects. If a company is dealing with frequent outages, it may cause stakeholders to hesitate in supporting new initiatives due to the perceived instability of core systems.

Therefore, recognizing the direct impact of outages on developer confidence, the time spent by engineering teams, and the risk to strategic projects is crucial in understanding how outages affect core applications.