The user acceptance testing phase usually occurs immediately before rollout.

The user acceptance testing phase usually occurs immediately before rollout.

• A. Project description
• B. System backup
• C. Rollout
• D. Project sign-off

Answer: (C)

User acceptance testing is a final validation by end users to confirm the system meets real business needs and supports actual workflows. It’s performed after development and internal testing, in a staging-like environment, and any issues found are addressed before go-live. Because it serves as the last checkpoint before production deployment, it happens immediately before rollout. The other options don’t fit this testing role: a project description is an early planning artifact, not a testing phase; a system backup is a precautionary operational step, not an acceptance test; and project sign-off is a formal closure milestone that typically follows testing and deployment, not the testing step itself.

User acceptance testing is a final validation by end users to confirm the system meets real business needs and supports actual workflows. It’s performed after development and internal testing, in a staging-like environment, and any issues found are addressed before go-live. Because it serves as the last checkpoint before production deployment, it happens immediately before rollout.

The other options don’t fit this testing role: a project description is an early planning artifact, not a testing phase; a system backup is a precautionary operational step, not an acceptance test; and project sign-off is a formal closure milestone that typically follows testing and deployment, not the testing step itself.