An organization manages a large cloud-deployed application that employs a microservices architecture across multiple data centers.
Reports have been received about application slowness.
The container orchestration logs show that faults have been raised in a variety of containers that caused them to fail and then spin up brand new instances.
Which two actions can improve the design of the application to identify the faults? (Choose two.)
Click on the arrows to vote for the correct answer
A. B. C. D. E.BC.
The given scenario describes an application that employs a microservices architecture across multiple data centers, and reports have been received about application slowness. The container orchestration logs show that faults have been raised in a variety of containers that caused them to fail and then spin up brand new instances. The question asks to identify two actions that can improve the design of the application to identify the faults.
Option A: Automatically pull out the container that fails the most over a time period.
This option suggests automatically identifying the container that fails the most over a time period. While this approach might help to identify a specific problematic container, it does not necessarily address the root cause of the faults. Moreover, the container that fails the most might not necessarily be the most critical container to the application's overall performance.
Option B: Implement a tagging methodology that follows the application execution from service to service.
This option suggests implementing a tagging methodology that follows the application execution from service to service. This approach can help to identify the specific service(s) causing the faults, which could provide insight into the root cause of the slowness issue. By following the execution flow of the application, the organization can identify which microservice is causing the slowness issue and take appropriate actions to fix it.
Option C: Add logging on exception and provide immediate notification.
This option suggests adding logging on exception and providing immediate notification. This approach can help to identify the root cause of the faults in real-time. By logging exceptions, the organization can identify the specific service(s) that are causing issues, and immediately notify the relevant team to investigate and fix the issue.
Option D: Do a write to the datastore every time there is an application failure.
This option suggests writing to the datastore every time there is an application failure. While this approach can help to track application failures, it does not necessarily address the root cause of the faults or provide real-time insight into the issue.
Option E: Implement an SNMP logging system with alerts in case a network link is slow.
This option suggests implementing an SNMP logging system with alerts in case a network link is slow. This approach can help to identify network-related issues that could be causing the slowness of the application. However, this option does not necessarily address the faults raised in the container orchestration logs.
Based on the above analysis, options B and C are the best choices. Implementing a tagging methodology that follows the application execution from service to service can help identify the specific service(s) causing the faults, while adding logging on exception and providing immediate notification can provide real-time insight into the root cause of the issue.