CHALLENGE 4 - Release Recoverability Evidence Gate
Backups completed for the upgraded reporting system and the newly installed UAT database before testing began. Recovery validation for the UAT database is scheduled but not complete, and the upgraded system has only backup completion evidence. What should happen before final UAT sign-off supports release approval?

• A. Approve sign-off because completed backups are enough for release continuity.
• B. Perform recovery validation only if reporting becomes unavailable during UAT.
• C. Complete recovery validation and document startup behavior for the release systems.
• D. Replace recovery validation with dashboard availability because this is not production cutover.

CHALLENGE 2 - Release Control Timing for Urgent Replenishment Orders
A project reviewer notes that urgent replenishment orders can still be created and progressed under both of the following conditions: one path uses the common approval structure, and another path uses locally reduced approval handling. The business asks which path should guide go-live readiness. Which answer is best?

• A. Keep both routes active so plant buyers can decide based on workload at the time of order creation
• B. Choose the common approval structure unless it prevents urgent orders from meeting operational timing expectations
• C. Choose the faster path because any functioning route is acceptable during the cutover weekend
• D. Use the reduced approval route for direct materials and the common route for indirect materials only

A packaging manufacturer performs a controlled SAP HANA administration change before a weekend reporting cycle. After the activity, the database starts and SAP HANA cockpit shows normal availability. During validation, the administrator sees that a scheduled administrative check still uses the previous configuration value even though the new value appears in the saved configuration record. The operations supervisor wants to close the change because no current user sessions are failing.
The constraint is that the administrator must confirm that scheduled administration will execute with the approved configuration. The validation must focus on the configuration state used during execution, not only current database availability.
What should the administrator do before closing the change?

• A. Wait for the weekend reporting cycle to complete and review whether users report any effect from the configuration mismatch.
• B. Close the change because active users are not reporting failures after the database restart.
• C. Manually update the change record to show that the previous configuration remains the operational baseline.
• D. Validate why the scheduled check still reads the old value, activate the approved configuration where required, and rerun the administrative check.

A regional textile manufacturer is preparing an SAP HANA lifecycle update rehearsal for an on-premises database. The database is available, and the update package has been staged. During the final review, the administrator finds that the rollback checkpoint in the runbook still references the previous rehearsal's backup timestamp. The current backup completed successfully, but the rollback section was not updated before the approval meeting.
The constraint is that the rehearsal must begin only after rollback evidence matches the current lifecycle activity. The administrator must prevent execution from starting with a recovery reference that belongs to an earlier rehearsal.
What should the administrator do before approving the lifecycle update rehearsal?

• A. Restart SAP HANA so the runbook rollback section can be refreshed through the current runtime state.
• B. Keep the previous rollback timestamp because it was already proven during the earlier rehearsal.
• C. Start the rehearsal because the database is available and the current backup completed successfully.
• D. Update the rollback checkpoint to the current backup evidence, validate the reference, and proceed only after the runbook is current.