What practice best ensures coordination with teams when responding to a vulnerability in GAS?

• A. Work in isolation without notifying others.
• B. Assign all tasks to a single individual without updates.
• C. Coordinate with maintainers, security and development teams; update advisories; track status in a shared dashboard.
• D. Only inform management and skip engineering teams.

Answer: (C)

Coordinated cross‑team action, with clear communication and shared visibility, is essential when responding to a vulnerability. Working with maintainers to understand the scope, engaging security teams to assess risk and define remediation, and involving development teams to implement fixes ensures the right people know what needs to be done and when. Keeping advisories up to date communicates the nature of the vulnerability, affected components, risks, and mitigation steps to users and stakeholders, while a shared dashboard provides a single source of truth for progress, status, timelines, and ownership. This approach prevents gaps, duplication, and delays that often happen when teams work in silos or rely on a single person.

Earlier options fail because isolation or unilateral ownership creates blind spots and bottlenecks, and informing only management excludes the engineers who must implement the fix. Coordinated, transparent effort is what enables a timely, effective, and auditable response.