What is the cause of extended recharge time?

A task is configured to run at 1:00AM. Historically it is a task that takes around 2 hours to complete. The system administrator realizes that the task is still running in the morning when it should have ended last night.

What is the cause of extended recharge time?
A . Database credentials have changed
B. There was a small increase in the amount of data
C. There are resource constraints in the database
D. Drivers for connection to the database have underwent automatic updates

View Answer

Answer: A

Explanation:

This type of question has a multitude of different interpretations, but I want you to follow a particular line of reasoning: through elimination it is possible to know the correct Answer , because when we set up a new task in QMC, if we keep the parameter "Max retries" in the pattern, which is zero, the task is no longer executed in the event of error. But now imagine that this parameter has changed. So if there was any changes to the database access credentials as well, the task will try to run that number of times parameterized.

A slight increase in the amount of data would result in a small increase in load. It wouldn’t make sense to grow little and take too long.

Drivers for connection to the database do not have, for the most part, automatic updating. That’s because it would be a very big security breach. Ideally, the environment will work with a stable, already tested version. These are situations performed manually.

If there was resource restriction in the database for some reason, surely the task would not have been performed from the past times and the symptom is that it stopped working overnight.