The correct option is It allows stakeholders to rank fixes by both technical impact and business value.

Collaborative vulnerability management combines the security teams technical assessment with application owners business context and leaderships priorities so teams can rank fixes by severity and by impact to critical services and revenue. This joint ranking lets the organization focus limited resources on fixes that reduce the most risk to the business while accepting lower priority issues when appropriate.

It eliminates the need for a formal risk matrix is incorrect because working together does not remove the need for a risk framework. A formal risk matrix or documented criteria still helps standardize how technical severity and business impact are measured and compared across findings.

GCP Security Command Center is incorrect because it names a specific tool rather than explaining why collaboration matters. Tools can surface findings and provide telemetry but they do not replace stakeholder discussions about business impact and remediation priority.

It places remediation solely on IT teams is incorrect because the opposite is true. Effective vulnerability management distributes accountability and ensures application owners and business leaders accept or reprioritize fixes based on operational and business considerations.

Full AWS Practitioner Certification Question