CV0-002 · Question #242
A company upgraded a hosted vulnerability scanner to the latest version, and now tickets are not being created to assign critical vulnerabilities. After confirming the ticketing issue, all the…
The correct answer is D. There is an application compatibility issue. Roll back to the previous working backup. When a vulnerability scanner fails to create tickets after an upgrade, despite services running, the most probable cause is an application compatibility issue introduced by the new version; the best fix is to roll back to a previously working backup.
Question
A company upgraded a hosted vulnerability scanner to the latest version, and now tickets are not being created to assign critical vulnerabilities. After confirming the ticketing issue, all the scanning services are confirmed to be running on the VM. Which of the following is the MOST likely cause and best method to fix the issue?
Options
- AThere was an IP change to the VM. Make changes to the server properties.
- BThe upgrade has a bug Reboot the server and attempt the upgrade again.
- CThe vulnerability scanner is on a different subnet. Open the ports, and it will reconnect.
- DThere is an application compatibility issue. Roll back to the previous working backup.
How the community answered
(16 responses)- A6% (1)
- B13% (2)
- C6% (1)
- D75% (12)
Why each option
When a vulnerability scanner fails to create tickets after an upgrade, despite services running, the most probable cause is an application compatibility issue introduced by the new version; the best fix is to roll back to a previously working backup.
An IP change would likely cause the entire scanner service to fail or lose network connectivity, not just the ticketing component while services are confirmed running.
While upgrades can have bugs, a reboot or re-attempting the upgrade does not address the underlying bug or compatibility issue and might lead to the same problem.
If the scanner were on a different subnet, it would typically lose all network connectivity, which contradicts the information that scanning services are running.
An application compatibility issue is highly likely after an upgrade, especially if core functionalities like ticketing integration stop working while the main service runs. Rolling back to a previous working backup is the most reliable and quickest method to restore service functionality when an upgrade introduces unforeseen software conflicts or bugs.
Concept tested: Troubleshooting post-upgrade application issues
Topics
Community Discussion
No community discussion yet for this question.