A root cause analysis reveals that a web application outage was caused by one of the company's developers uploading a newer version of the third-party libraries that were shared among several applications.
Which of the following implementations would be BEST to prevent the issue from reoccurring?
A.
CASB B.
SWG C.
Containerization D.
Automated failover.
C.
A root cause analysis reveals that a web application outage was caused by one of the company's developers uploading a newer version of the third-party libraries that were shared among several applications.
Which of the following implementations would be BEST to prevent the issue from reoccurring?
A.
CASB
B.
SWG
C.
Containerization
D.
Automated failover.
C.
The best implementation to prevent the issue from reoccurring, based on the information provided, would be containerization (option C).
Containerization is the process of encapsulating an application with all its dependencies and libraries into a single, self-contained package called a container. By doing so, the containerized application can run consistently across different computing environments, without worrying about conflicts or compatibility issues with other applications.
In this scenario, the web application outage was caused by a developer uploading a newer version of the third-party libraries that were shared among several applications. By containerizing the web application, the third-party libraries would be included within the container, separate from other applications that may be using different versions of the same libraries. This would help to avoid conflicts and compatibility issues that could cause similar outages in the future.
CASB (option A) stands for Cloud Access Security Broker, which is a security solution used to monitor and manage access to cloud applications and services. While CASB may be useful for securing cloud-based applications, it does not directly address the issue of conflicting libraries that caused the web application outage.
SWG (option B) stands for Secure Web Gateway, which is another security solution used to monitor and manage web traffic for security purposes. While SWG may be useful for securing web applications, it does not directly address the issue of conflicting libraries that caused the outage.
Automated failover (option D) is a process of automatically switching to a backup system or component in the event of a failure of the primary system or component. While automated failover may be useful for ensuring availability of critical systems, it does not directly address the root cause of the web application outage, which was caused by a conflict with shared libraries.
Therefore, the best option to prevent the issue from reoccurring would be containerization (option C), as it directly addresses the root cause of the web application outage by separating the application and its dependencies from other applications that may be using different versions of the same libraries.