Which statement best describes Testing in the SDLC?

Which statement best describes Testing in the SDLC?

• A. Verifying initial design aesthetics.
• B. Planning deployment schedule.
• C. Implementing feature flags in production.
• D. Verifying security, permissions, and functionality and fixing issues.

Answer: (D)

Testing in the SDLC focuses on validating that the software behaves correctly and securely, and on identifying and fixing defects. It involves running the software to verify that features work as intended, that security and access controls (permissions) enforce the right boundaries, and that issues uncovered during testing are resolved before release. This emphasis on functional validation, security checks, and defect repair is what makes it the best description of testing. Other activities mentioned aren’t testing: verifying design aesthetics belongs to design/UX evaluation, planning a deployment schedule is project management and release planning, and implementing feature flags in production is a deployment strategy for controlling features rather than testing the software’s correctness and security.

Testing in the SDLC focuses on validating that the software behaves correctly and securely, and on identifying and fixing defects. It involves running the software to verify that features work as intended, that security and access controls (permissions) enforce the right boundaries, and that issues uncovered during testing are resolved before release. This emphasis on functional validation, security checks, and defect repair is what makes it the best description of testing.

Other activities mentioned aren’t testing: verifying design aesthetics belongs to design/UX evaluation, planning a deployment schedule is project management and release planning, and implementing feature flags in production is a deployment strategy for controlling features rather than testing the software’s correctness and security.