Exam CV0-003 topic 1 question 194 discussion

D. Use a load balancer to redirect traffic to other systems serving the application is the best step to take. This will allow the engineer to gracefully stop new transactions from processing by redirecting traffic to other systems while the updates are applied. Option A is not always available, depending on the application. Option B is not the best option, as it could cause delays. Option C is not the best option, as it could cause data loss or corruption.

Maintenance mode is a built-in feature in many applications that prevents new transactions while allowing current ones to complete gracefully. This is the best approach to avoid data corruption or incomplete operations before applying updates.

I lean towards option D as the best option. I initially thought of going with option B, but waiting until after business hours to conduct the change when the system is not in use might cause significant delays and possible application vulnerabilities if the updates to be applied are urgent security patches, and updates to enhance application functionality.

This is poorly worded. And a bad scenario. The application is being stopped entirely. No "new" transactions will be allowed until the update is done. Load balancing will not solve this problem. Maintenance seems the best (worst) option.

It's not saying anything to redirect traffic or keep the application running. It's a direct gracefully stop and apply the updates.

A. Enable maintenance mode from the application dashboard: While this is a valid option, it depends on your application supporting a maintenance mode and may not be as fast or flexible as using a load balancer to divert traffic. B. Wait until after business hours: This approach might not always be feasible, especially in scenarios where 24/7 service is required. C. Run a kill command on the system: Killing processes abruptly with a kill command can lead to data corruption and isn't a graceful way to stop a service. It can result in the loss of in-flight transactions and may not allow you to control the process gracefully. Using a load balancer to manage traffic during updates allows for a controlled and seamless transition, minimizing the impact on end-users.

Is Not A When a server is undergoing maintenance, it may be in a state that it will not respond to health checks, API calls, Simple Network Management Protocol (SNMP), or any other means used to monitor its health by network management systems. This failure to respond to various monitoring methods may cause false alarms and trigger automated troubleshooting systems. When a server is in maintenance mode, the management systems will not respond to alarms from the server being down for maintenance.

By configuring the load balancer to direct traffic away from the servers that require updates, new transactions can be effectively stopped while the updates are applied.

load balancer will only redirect new tasks and not "gracefully stop" running activities. This can be provided by a maintenance mode - if the app has such.

D. Use a load balancer to redirect traffic to other systems serving the application. The best approach to gracefully stop new transactions before applying updates to an application is to use a load balancer. The load balancer can redirect traffic to other systems that are still serving the application while the updates are being applied. Once the updates are completed, the load balancer can direct traffic back to the updated systems. This approach avoids any downtime for the application and ensures a smooth transition.