Question 14

A rollback had been executed on the instance.

The most likely cause for a previously remediated vulnerability reappearing on a database server is that a rollback had been executed on the instance. This action can restore the system to a prior state, potentially reintroducing vulnerabilities that were previously mitigated.

A) The finding is a false positive and should be ignored.

This option is unlikely to be correct because a false positive would not typically result in a previously remediated vulnerability reappearing. If the vulnerability was genuinely remediated, a false positive should not lead to its resurgence.

B) A rollback had been executed on the instance.

This option accurately identifies the cause of the issue. If a rollback occurred, it would revert the system to its earlier state, including vulnerabilities that had been previously addressed, thus explaining the reappearance of the vulnerability on the dashboard.

C) The vulnerability scanner was configured without credentials.

While misconfiguration of the scanner could lead to incomplete assessments, it would not logically result in the re-emergence of a previously remediated vulnerability. This option does not address the situation where a vulnerability is showing up again after being fixed.

D) The vulnerability management software needs to be updated.

Updating the vulnerability management software is essential for maintaining effectiveness, but it does not directly explain why a previously remediated vulnerability would reappear. An outdated system would affect detection but would not revert the state of vulnerabilities.

Conclusion

The reappearance of the vulnerability on the dashboard is best explained by the execution of a rollback, which can restore vulnerabilities that were previously remediated. Other options either misinterpret the scenario or do not directly relate to the re-emergence of the vulnerability, confirming that B is the definitive correct answer.