What best describes the relationship between bug severity and priority in this context?

• A. Severity reflects impact on the product, while priority reflects urgency for fixing based on business needs.
• B. Severity is about speed; priority is about cost.
• C. They are the same.
• D. Priority is about aesthetics.

Answer: (C)

In this context, severity and priority are treated as the same measure of how urgently a defect should be addressed. The idea is that the impact on the product and the urgency for fixing are aligned so that a high-severity issue is also a high-priority fix, and a low-severity issue is a low-priority one. This simplified view focuses on how quickly to act rather than separating impact and urgency into two separate axes.

In real-world practice, severity and priority are often different—severity typically reflects the defect’s impact on functionality or users, while priority reflects business urgency or release timing. But this question assumes they coincide, which is why this option fits best here.