Which option describes the correct content of an RFC?

Prepare for the CSS Mastery SAD Maintenance and CSA Stand Ups Test. With flashcards and multiple choice questions, ready yourself for the exam with hints and explanations for every question. Ace your exam today!

An RFC should capture information that governs the change from planning through approval to a safe rollback. It needs to spell out why the change is needed (purpose) and what exactly will be affected (scope), so stakeholders understand the extent and rationale. It must also include a back-out or rollback plan and criteria, so there’s a clear path to revert if things don’t go as expected. Including risk and a testing plan helps assess potential impact and confirm the change behaves as intended before full deployment. Approvals are essential to show who is authorized to proceed, ensuring proper governance.

The other options don’t provide this full picture. Approvals alone omit what’s being changed and how to react if problems arise. Only purpose and scope miss the necessary risk assessment, testing, and rollback details. Documenting technical steps in detail is too focused on execution and doesn’t ensure the broader governance and revert mechanisms that an RFC should guarantee.