A security architect is assigned to a major software development project. The software development team has a history of writing bug prone, inefficient code, with multiple security flaws in every…

Question

Options

• Aerror handling, input validation, memory use and reuse, race condition handling,
• Berror prevention, requirements validation, memory use and reuse, commenting typical
• Cerror elimination, trash collection, documenting race conditions, peer review, and typical
• Derror handling, input validation, commenting, preventing typical security problems,

• A
  89% (16)
• B
  6% (1)
• C
  6% (1)

Explanation

Established secure coding frameworks (such as CERT Secure Coding Standards, OWASP, and MISRA) focus on: error handling (preventing information leakage and crashes), input validation (preventing injection and overflow attacks), memory use and reuse (preventing buffer overflows, use-after-free, and memory leaks), and race condition handling (preventing time-of-check/time-of-use vulnerabilities). Option B incorrectly references 'error prevention' and 'requirements validation,' which are QA/PM concepts, not secure coding topics. Option C mentions 'error elimination' and 'trash collection,' which are not standard secure coding categories. Option D partially overlaps but omits memory management and race conditions, which are critical security concerns in secure coding practice.

No community discussion yet for this question.